Unbanked test, always something is wrong, enough, You live in a world of fantasy
"true","2019-01-08T10:55:56","PODC Payment","","BMdmVJtfYU9TtgF7TRSXzsK9Wh2teweijB","442.19000000","e3aca59824320db1f679f32f211adc8d3ae349c423c788aaad0e7c6a0764365a-000"
"true","2019-01-06T10:34:30","PODC Payment","","BMdmVJtfYU9TtgF7TRSXzsK9Wh2teweijB","434.75000000","763fecf4d7f6a5eab47345e6ab428c9cb7ec69ff738bea875e92c1855ebce9b4-000"
Could you elaborate? Showing a list of data doesn't tell us what is wrong  You really don`t see what is wrong? Is it that the payments have been going down since November? If its the variance in payments, a lot of factors go into this... And I dont have a record of your historic RAC to compare. (my own unbanked devices vary regularly) Plus the increase of the overall RAC means even if your RAC is the same your payments will go down unless you increase your RAC. If not, then please ask an actual question, so we can respond. |
|
|
|
Unbanked test, always something is wrong, enough, You live in a world of fantasy
"true","2019-01-08T10:55:56","PODC Payment","","BMdmVJtfYU9TtgF7TRSXzsK9Wh2teweijB","442.19000000","e3aca59824320db1f679f32f211adc8d3ae349c423c788aaad0e7c6a0764365a-000"
"true","2019-01-06T10:34:30","PODC Payment","","BMdmVJtfYU9TtgF7TRSXzsK9Wh2teweijB","434.75000000","763fecf4d7f6a5eab47345e6ab428c9cb7ec69ff738bea875e92c1855ebce9b4-000"
Could you elaborate? Showing a list of data doesn't tell us what is wrong |
|
|
|
Totalrac pulls from a bbp pool API, and is only a "rough guess" try the podcstatus script, if it matches then we have an issue
No, totalrac pulls from the API, but it is the from the last WCG rac export (not a rough guess). Thats the same info that is used to create each superblock. I should have been more clear; The "totalrac" command pulls from the latest copy of the WCG export that was loaded to the pool. Yes, this is the same source as the superblock but due to timing can have slightly different values. I was trying to express, if the podcstatus page agrees with the totalrac command, then there is an issue at the source (the WCG export file), otherwise its localized to the pool. (which seems to have been the case this time around). |
|
|
|
|
Totalrac pulls from a bbp pool API, and is only a "rough guess" try the podcstatus script, if it matches then we have an issue
|
|
|
|
Are there any Modifications on PODC or ist POG Activated?
My Boinc Maschines are Up and Running
But since today my WCGRac is 0
"wallet_fullversion": "1.1.5.9"
Where are you checking RAC? Try: http://forum.biblepay.org/tools/podcstatus.php |
|
|
|
Sorry guys and gals... I had enabled notifications for new posts, apparently they stopped sending and I had not noticed.. I'm still around Will keep this tab open going forward.. |
|
|
|
I think discussions of other coins should be kept in either their threads, or in PM's Please keep this topic for things BBP related. |
|
|
|
|
im curious why the source is not up on github?
|
|
|
|
|
I don't see this being ready that quickly, i'm not sure if there is a specific timeline.
|
|
|
|
I thought the team limit removed, I changed team and I am getting this:
Warning": "CPID xxxxxx not in team Biblepay. This CPID is not receiving rewards for cancer research.
This is a client display bug, (error is hardcoded into the client). Check PODC Status page for more current info Edit: What is the command you're running and getting this error from? getboincinfo on Linux wallet version: 1.1.5.9 EDIT: same for 1.1.6.1 on Linux, I don't have GUI. Fixed in the next version; we now respect the non-biblepay-team-percentage spork, and will not show the warning. my masternode connected to same wallet is in this mode since team change: WATCHDOG_EXPIRED masternode debug.log shows this for every watchman call (once per minute) : 2018-12-15 14:40:27 ERROR: ContextualCheckBlock: CPID Signature empty. Strange what version of the client is your MN running? |
|
|
|
I thought the team limit removed, I changed team and I am getting this:
Warning": "CPID xxxxxx not in team Biblepay. This CPID is not receiving rewards for cancer research.
This is a client display bug, (error is hardcoded into the client). Check PODC Status page for more current info Edit: What is the command you're running and getting this error from? |
|
|
|
I tried restarting my pc and wallet, the PODC updates are working the past couple of days, waiting on payments to resume.
Sorry for the trouble, but glad it got resolved. Incidentally, I did a minor update to the PODC Status script, it will now capture your RAC at the time it sees new PODC updates, should give a nice history of activity over time. |
|
|
|
Thanks. Here are some of the results from the link:
Error: Missed a 24 hour PODC Update Window
Total Rac:8,257
Min Required Stake:6,610
Min Stake last 24hr:0 Warning: Not enough stake
Most Recent Stake:0 Warning: Not enough stake
---
If 20 BBP is needed for each Rac, then the required stake is 20 x 8257 Rac = 165140
There is more than 165140 BBP in the wallet.
Also, isn't the UTXO/stake automatically calculated to provide a lower percentage of reward if the entire 20 BBP per Rac isn't available?
fyi there is no 'utxoamount=' in the biblepay.conf file.
Try running 'exec podcupdate true' from the debug console.. I suspect something is preventing your client from sending updates. If that doesn't work PM me your CPID, and I'll see what else I can tell As for the other questions, yes if you are sending updates it should adjust, but from what you put there, you're not sending them. Here are the results from running exec podcupdate true: "Command": "podcupdate", "PODCUpdate": "Processed (4) over 1 CPID(s) successfully." Also does 'utxoamount=' need to be in the biblepay.conf file for the auto stake feature to work? 4 updates? strange.. do you see it on the site now? And no, utxoamount is not required. You do need gen=1, and at least genproclimit=1 do you mind pasting your .conf here (you can remove any sensitive info) |
|
|
|
 DOVE is for mining: but why so high reward? doesnt POW 20% and POG 80%? You're on testnet... there is no payments to masternodes there currently. |
|
|
|
Thanks. Here are some of the results from the link:
Error: Missed a 24 hour PODC Update Window
Total Rac:8,257
Min Required Stake:6,610
Min Stake last 24hr:0 Warning: Not enough stake
Most Recent Stake:0 Warning: Not enough stake
---
If 20 BBP is needed for each Rac, then the required stake is 20 x 8257 Rac = 165140
There is more than 165140 BBP in the wallet.
Also, isn't the UTXO/stake automatically calculated to provide a lower percentage of reward if the entire 20 BBP per Rac isn't available?
fyi there is no 'utxoamount=' in the biblepay.conf file.
Try running 'exec podcupdate true' from the debug console.. I suspect something is preventing your client from sending updates. If that doesn't work PM me your CPID, and I'll see what else I can tell As for the other questions, yes if you are sending updates it should adjust, but from what you put there, you're not sending them. |
|
|
|
how you get 8%?
20% POW
80% POG = variableX
that 8% i suppose is 10% from 80%, right? (X:(WEIGHT*10))
TIER 1 is block or block has 16 TIERS?
8 % is as you proposed Each block rewards one tier. My windows 64 wallet crashed too. Could you post debug.log or email me? |
|
|
|
after pog will be what?  Can't imagine? Change isn't always a bad thing.. Gotta keep life exciting! haha... Don't forget the idea is we test POG along with PODC for a while. So we're still a ways out from cutting PODC |
|
|
|
Slovakia, that for sure is the Biblepay paper wallet? The source code makes mention of Litecoin?
yes it is..... its from Webster daemonko yes, ill make 1000 wallets  pool mining= dead podc=dead pog= dead future bbp= dead Robertko: you said few months ago that PODC is perfect and now is bad for you? investors must be very happy from all this changes  Please calm down, nothing is dead right now. |
|
|
|
|
Show Posts
