Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
On the DIP002, I agree on doing this on a longer term scale - for "best practices".
I think you can (given your availability) port the GetTitheParams function(s) (just the math function(s) like quantize, not the UpdatePogPool stuff) into the mobile wallet, and call the Pool API for the pindexBestHeader->chainTip() POG difficulty level (IE 0-65535) (only because the pindex during sync wont have your current diff since the blocks arent stored but instead computed in the large client), once you have that int you can then call for the GetTitheParams, and that gives you the 3 things we can quote the user (age, max, min).
The POG transaction does not require, but we should, transmit the <nickname> XML and the <tither> address in the ".sTxOutMessage" field - I dont know if you have implemented that field in the mobile client yet, would that be hard to add that field to the broadcasted transaction? Then you would need to ask them for their nickname somehow during setup (not sure if there is a config in there). It actually is OK to skip those two as users will receive POG payment rewards back to the sending address but I still recommend us going the extra mile to add the ability to send the message, because it is frowned upon to send rewards back to the change address (in addition a lot of clients try to anonymize the change address, and also it creates more spam, IE mobile user jumping around in the pog pool with many addresses etc).
At this point, the tithe should be accepted in the pogpool, so I think it should be doable.... Of course we should talk more about our apple situation as what is the use in doing all this if we cant even get listed in the Apple store.
MIP-
I wanted to make a small record of this so we dont forget - POG should theoretically allow us to help the unbanked - I believe all we need is the current POG difficulty level, a 'pog tithe' button, and the ability for the mobile wallet to send a tithe. At that point, the user should enter the pog pool.
Did you get your nickname working btw?
Oh, ok I remember something now - when your nickname is not set up (IE its empty) Chat does Not work - it needs a name to work.
On your nickname, I think I know the problem - Im not sure if you saw my prior message, but please create a biblepaytest.conf here:
~/.biblepaycore/biblepaytest.conf
If you place: nickname=yyyy
testnet=1
tithe=N
In there, you should then be able to reboot and see the nickname in 'pogpool'?
testnet=1
shrinkdebuglog=1
debug=true
debugmaster=true
tithe=3
nickname=mobiledev
genproclimit=1
gen=1pogpool
{
"ySwRWw1EEEMyGSz4iiWVAwryXbxBTumiPG": "Amount: 879.00, Weight: 1.0000, Payment_Tier: 0, Height: 101722, NickName: randrews",
"High Tithe": 879.3,
"Total Tithes": 879.3,
"Total Participants": 1,
"POG Difficulty": 14084.597503552,
"My Tithes": 0,
"My Nickname": ""
}
pogpool
{
"ySwRWw1EEEMyGSz4iiWVAwryXbxBTumiPG": "Amount: 637.00, Weight: 1.0000, Payment_Tier: 0, Height: 101505, NickName: randrews",
"High Tithe": 637.2,
"Total Tithes": 637.2,
"Total Participants": 1,
"POG Difficulty": 10206.64793502028,
"My Tithes": 0,
"My Nickname": ""
}
Correct, 13.87 days if the diff was static - but it fluctuates.
When you say chat doesnt work, what did you try - pm or public and what username did you page if it was PM? (I havent been at the computer).
(Ive tested them both across nodes and it appears to work though).
exec titheinfo
{
"Command": "titheinfo",
"POG Difficulty": 15151.39403913321,
"24 Hour Tithes": 11350.8,
"pog_diff_chain_tip": 15151.39403913321,
"min_coin_age": 13.87,
"min_coin_amt": 5780.66,
"max_tithe_amount": 230.87,
"Tithable_Coin_Quantity": 0,
"Tithable_Largest_Coin": 0,
"Tithable_Coin_Avg_Age": 0,
"Tithable_Total_Coin_Balance": 0,
"Tithability_Amount": 0,
"Tithability_Summary": "NO",
"Tithe_Cap": 49096,
"Daily_Miner_Emissions": 96188,
"Pool_Emissions": 76950.40000000001,
"Lowest_ROI%": 78.5,
"Highest_ROI%": 339
}getmininginfo
{
"blocks": 99878,
"blocks_tip": 99878,
"currentblocksize": 1000,
"currentblocktx": 0,
"difficulty_podc": 6.964404506368992,
"difficulty_pow": 0.1056952030005922,
"difficulty": 6.964404506368992,
...
"pool_url": "",
"poolmining_use_ssl": false,
"pool_high_tithe": 5048.1,
"pool_my_total_tithes": 0,
"pool_total_tithes": 10929.6,
"pog_difficulty": 14589.16343254311,
"pog_min_coin_age": 13.36,
"pog_min_coin_amount": 5566.19,
"pog_max_tithe_amount": 233.44
}
19:42:13

exec tithe 1000
{
"Command": "tithe",
"Error": "Sorry, your tithe exceeds the maximum allowed tithe for this difficulty level. (See getmininginfo)."
}
exec tithe 200
{
"Command": "tithe",
"TXID": "0000000000000000000000000000000000000000000000000000000000000000"
}
If you set your nickname (nickname=yourname) in the config we can test:
1) Private chat call and answer
2) You can help us test the ROI on a brand new POG node; IE be sure to write down exactly what you started with before POG started, then tally your total expenditures (IE donations to the foundation over the duration) and tally the "POG rewards", and paste the ROI level here. You should receive about a 50% profit on what you spend over a certain period.
testnet=1
shrinkdebuglog=1
debug=true
debugmaster=true
tithe=3
nickname=MIP
genproclimit=1
gen=1
I think at this stage we just wait for someone who has been crashing on windows to set 'boincmetrics=-1' and confirm it doesnt crash.
Then once we know it was that API call, you can make the decision if we want to fix the Win API call or wait until Evolution rebase is released.
I remember reading that the BOOST (later version boost that is with the MAC include you found for us) does support the WIN "hide" switch, so imo that would be the easiest (just let everyone live with the flashing screens for a while) and then we leverage that arg.
// If an error occurs, exit the application.
if ( ! bSuccess ) {
exit(1);
}