Since updating to 1195 or 1196 (not sure which, I'm currently on 1196) my wallet does not tithe as often as it can. I have set "tithe=10" and my POG Engine Room is full of tithable coins, but the wallet only tithes 3 times (every 10 minutes), then waits for approx. 3-4 hours, then again tithes 2 or 3 times and so on ...
Any ideas?
Go into PoG Engine Room. On top checkboxes, check Tithable, Age not Amount, and Amount Not age Sort by Age (Days) descending Status will tell you whether your coins are tithable or not. If not, it'll explain why in the status. If your BBP is not eligible to tithe, auto tithe won't sent donation to BB2. If you're having different issue, please explain further. Well, as I already said, I have loads of "tithable coins" in that list (about 3 dozen lines or something like that), so I honestly have no other idea what the problem could be ... I'll test running the wallet with tithe=45, let's see how this works out. Can you tithe manually? Tithe 9 from debug console Or pog tithe from gui Under tools info how many mempool tx are there? # mempool tx: 1 => manual tithe works perfect => # mempool tx: 4 => tried manual tithe again: works after approx. 2 minutes => further manual tithes also seem to work, # mempool tx is rising (currently 11) |
|
|
|
Since updating to 1195 or 1196 (not sure which, I'm currently on 1196) my wallet does not tithe as often as it can. I have set "tithe=10" and my POG Engine Room is full of tithable coins, but the wallet only tithes 3 times (every 10 minutes), then waits for approx. 3-4 hours, then again tithes 2 or 3 times and so on ...
Any ideas?
Go into PoG Engine Room. On top checkboxes, check Tithable, Age not Amount, and Amount Not age Sort by Age (Days) descending Status will tell you whether your coins are tithable or not. If not, it'll explain why in the status. If your BBP is not eligible to tithe, auto tithe won't sent donation to BB2. If you're having different issue, please explain further. Well, as I already said, I have loads of "tithable coins" in that list (about 3 dozen lines or something like that), so I honestly have no other idea what the problem could be ... I'll test running the wallet with tithe=45, let's see how this works out. |
|
|
|
After update to 1.1.9.6 all my titheable coin disappear   . i mean my coin still in wallet but no able to tithe. coinage ..etc..gone...WTH i can't understand.. It seems I have kind of the opposite problem.  Since updating to 1195 or 1196 (not sure which, I'm currently on 1196) my wallet does not tithe as often as it can. I have set "tithe=10" and my POG Engine Room is full of tithable coins, but the wallet only tithes 3 times (every 10 minutes), then waits for approx. 3-4 hours, then again tithes 2 or 3 times and so on ... Any ideas? |
|
|
|
What's going on with the pool? oO Seems like our beloved "botnet" is back at it, leeching almost every network block and getting more than 90% of all coin rewards. btw: for the "Reports -> Block history" the Anonymization does not work. P.S.: I tested POG with tithe=5 today and it worked quite well as I received quite a large POG payment. However my wallet went "dry" quite quickly (naturally) and this raised the question in me how a new user would ever be able to tithe anything, when the "minAmount" is constantly in the thousands of BBP. That must be quite disappointing. |
|
|
|
Could anyone please explain again (from scratch) what the heck the "bankroll" feature is all about?
Why should I create a certain amount of fixed BBP "changes" when my wallet can just use random amounts of coins I have?
Can you re-read https://discontinuo.us/biblepay-unofficial-wiki/proof-of-giving/exec-bankroll-example ? I added a screenshot and more explanation. Let me know if anything is unclear. Anyone (that means you) can revise the wiki like I just did. P.P.S.: Also thanks for the quick compiling of 1191 on the PPA. Just updated my ARMs. I'm also glad you got them installed on the ARMs. Can you tell me what kind of hardware setup you have? Someone mentioned running Rasp Pi. Wouldn't that be cool? Be eco friendly (being good stewards of the Earth as God called us to be) and being able to help secure the BiblePay PoW network and also submit donations for PoG rewards. All using maybe 2-5 watts! Ah thank you, that makes it much clearer. I think I understood the concept now. So basically you can only tithe a maximum of "MaxTitheAmount" from addresses with amount>"MinCoinValue" AND (boolean) age>"MinCoinAge". Additionally, am I right to assume that once an address has been used for tithing it looses its coin age, meaning that if I have a single address with 50k BBP I can NOT tithe several times per day from this? Then the bankroll feature is actually quite helpful.  On the ARMs: Yes, I have some Raspberries (RPi 3b and 3b+), some Orange Pis (O-Pi PC 2) and an Odroid C2. They all run quite stable; the biggest issue with the BBP wallet right now is the I/O of the SD cards (especially when running multiple wallets) and the traffic if you use wifi. However you need some cooling of course; I use those cheap mini-racks and some passive cooling on the chips with a 120mm FAN on the side of the rack. Power-wise it's safe to say that none of those uses north of 5 watts. |
|
|
|
Could anyone please explain again (from scratch) what the heck the "bankroll" feature is all about? Why should I create a certain amount of fixed BBP "changes" when my wallet can just use random amounts of coins I have? I read " https://discontinuo.us/biblepay-unofficial-wiki/proof-of-giving/exec-bankroll-example" but still have no idea what the purpose of all of this is. Why is it benefitial to have a large amount of equal-coin bankrolls?? Additionally when Rob says The primary change that will occur this weekend is all the tithes over 10 bbp will dissapear and the POG payment per user should increase does that mean that from now on it only makes sense to create bankrolls of 10 (or less)? Just for the fun of it I created 100x10BBP denominations. What will the effect of this be in relation to my current tithing? (My wallet randomly spits out denoms of 7 or 8 bbp). Finally, I find it really confusing to use the term "coin" for a certain amount of BBP used as tithe. For me (and I think most crypto guys) 1 coin == 1 BBP! P. S.: Thank you MIP for the POG Engine Room in the wallet. This is really interesting, although I don't think it will make things easier to understand for new users. P.P.S.: Also thanks for the quick compiling of 1191 on the PPA. Just updated my ARMs. |
|
|
|
To be honest I still don't understand how exactly the tithing works. I have tithe=1 in my config and my wallet occasionally sends out some BBP. By now I also appear in the leaderboard and I even received tithes already. However my "titheinfo" still shows 0 for all numbers: "24_hour_tithes": 79488.39999999999,
"pog_difficulty": 102758.9892453088,
"min_coin_age": 60,
"min_coin_amt": 25000,
"max_tithe_amount": 1,
"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": 50694,
"Daily_Miner_Emissions": 94628,
"Pool_Emissions": 75702.40000000001,
"Lowest_ROI%": 16.5,
"Highest_ROI%": -2.5 Also, why is "highest ROI" a negative number? (win x64 wallet 1187) |
|
|
|
Ah I see, thanks guys, now the "bankroll" went through. I thought the unlock for this was already covered by the PODC unlock you make at wallet startup. Thank you rob for clearing up the diff. I checked back with my utxoreport and it seems like my wallet did NOT use all my coins over the last couple of weeks, but nevertheless I seem to have no "aged" coins, that seems strange.  |
|
|
|
Hello all, so I've been away the last 2 days and just came home to see that POG officially started. I read all 10 pages of new posts in this thread, then read the POG beginner guide, updated my wallet to 1186 and added "tithe=1" and a nickname to the config. The wallet starts fine and I see the POG stats etc., but please help me understand these problems: 1. current titheinfo: {
"24_hour_tithes": 128902.4,
"pog_difficulty": 166639.1616298037,
"min_coin_age": 60,
"min_coin_amt": 25000,
"max_tithe_amount": 1,
"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": 50694,
"Daily_Miner_Emissions": 94628,
"Pool_Emissions": 75702.40000000001,
"Lowest_ROI%": 16.5,
"Highest_ROI%": -35
}The guide says "maximum difficulty = 65535" and "maximum tithe per day approx. 100k". So how come both these values are way out of specification (and why does the wallet report "tithe_cap 50694"? 2. Up to today I did not cap my utxoamount. Does that mean that probably my current coin age is 0 for all my balance and I cannot receive POG payments (as of now) for 2 months?? 3. Why does "exec bankroll x y" always return "Signing transaction failed", no matter which values for x and y I try (even tried 1 1)? |
|
|
|
Nope, I mean "-resync". It's two levels "above" rescan (which only scans the blockchain without changing it) and one level above reindex (which uses already existing block files). It automatically deletes all blockchain-related files and re-downloads it completely.
First I've heard of the -resync option. Is it part of Bitcoin? Its not part of DASH as far as I can find. Do you know what coin offers this option? I don't know if it's part of Dash or Bitcoin, but some of my other QT wallets like CARE and XAX definitely have this feature and it's quite handy. |
|
|
|
1.1.8.5b is already in Ubuntu Launchpad. (PPA repository)
Remember that it just adresses a crash in a RPC (console) command , so it doesn't make any difference to 1.1.8.5 in terms of chain consensus .
after upgrade,still crashed I just checked the windows version ( www.biblepay.org) works and does not crash, maybe its the PPA version? It would be nice to know the OS+version used, and how it was installed. Also what kind of "crash" is the user experiencing (if there is a message to be seen on console, a segfault line, or nothing). Unfortunately, "still crashed" is not enough information to narrow down the problem. If anyone is running the new PPA version, please do a 'getdifficulty' and tell us it does not crash . Working just fine. It seems like I missed a PODC payment today, although my wallet was definitely on the correct chain the whole time and is constantly sending out PODC updates. Could this be related to the chaos in the blockchain? My getboincinfo looks like this: "Command": "getboincinfo",
"CPID": "7c9264559fef3c1c689ee9fc3ff42494",
"Address": "BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh",
"CPIDS": "7c9264559fef3c1c689ee9fc3ff42494;",
"CPID-Age (hours)": 430362,
"NextSuperblockHeight": 99640,
"NextSuperblockBudget": 1013881,
"7c9264559fef3c1c689ee9fc3ff42494_ADDRESS": "BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh",
"7c9264559fef3c1c689ee9fc3ff42494_RAC": 1884.74,
"7c9264559fef3c1c689ee9fc3ff42494_TEAM": 15044,
"7c9264559fef3c1c689ee9fc3ff42494_WCGRAC": 67264.5,
"7c9264559fef3c1c689ee9fc3ff42494_TaskWeight": 100,
"7c9264559fef3c1c689ee9fc3ff42494_UTXOWeight": 1521418,
"Total_RAC": 69149.24000000001,
"Total Payments (One Day)": 0,
"Total Payments (One Week)": 32228,
"Total Budget (One Day)": 1013881,
"Total Budget (One Week)": 7112607,
"Superblock Count (One Week)": 8,
"Superblock Hit Count (One Week)": 8,
"Superblock List": "99435,99230,99025,98820,98615,98410,98205,98000",
"Last Superblock Height": 99435,
"Last Superblock Budget": 1013881,
"Last Superblock Payment": 0,
"Magnitude (One-Day)": 0,
"Magnitude (One-Week)": 4.53110933867146 And yes, I think Discord or something like this would be very helpful (although I don't have a login for Discord yet^^). |
|
|
|
@Rob: other similar coins' wallets have the handy "-resync" flag for this process; would it be possible to implement this into the BBP wallet?
What is resync? Do you mean -rescan or -reindex ? options are available as tools under wallet repair. I'd try a reindex before you blow everything away except wallet.dat in your biblepaycore folder. Nope, I mean "-resync". It's two levels "above" rescan (which only scans the blockchain without changing it) and one level above reindex (which uses already existing block files). It automatically deletes all blockchain-related files and re-downloads it completely. Yes, addnodes are also a good idea. I usually don't have them in my configs but if necessary I add them manually to running ones (like today for the 1185b wallets). |
|
|
|
19:06:15
getblockhash 99323
19:06:15
5be68e877f004b4cf8ddcdc12dd3af8c536a0044f3aa67ac81903323063e92b5
OK, so it seems you are on a fork chain. Have you updated your wallet to 1.1.8.5 yet? If not, please do. If you have the newest wallet, then please close/stop your wallet, delete all files and folders in your core folder EXCEPT wallet.dat, biblepay.conf, masternode.conf, /backup/ and restart the wallet/daemon. @Rob: other similar coins' wallets have the handy "-resync" flag for this process; would it be possible to implement this into the BBP wallet? |
|
|
|
What should i write after getblockhash ?
txid= 07ec7d9354272c6163b5d11911bfcfa7e459f1ab988ff1bcd0aa395b49ca1c1e-000
I also want to note that the wallet behaves very unstable when trying to heat-mine. Even if I use 30% it closes (without messages) after 30-60 minutes, not to mention 60-80-100% load.
Either pick one of the blocks we posted earlier and compare, or try which should give 50fee6b0d63a163b8c7d40fc8d5d3f13d6fba908243bcb64f9dc6ce037a4fc2a (fingers crossed I'm on the correct chain right now lol). |
|
|
|
I shut down PODC few days ago. And leave wallet online with 1% CPU mining on pool.biblepay.org... And after few days i got it..
Please check your wallet with the "getblockhash" commands we posted earlier to see if you are on a fork. As already said, this symbol means that you found a block on your own, which is theoretically possible, but with 1% CPU highly unlikely. Btw: the main pool also seems to be on the wrong chain, it constantly changes the given information like "coins mined", "offline workers" etc. and also seems to be quite unresponsive. |
|
|
|
It seems like there are several problems right now. Most of my ARMs are on the apparently correct chain, but I just updated two of them to 1185b and this version does not seem to find peers at all. Also the PODC update system seems corrupt. The pool superblock view shows 0 for a lot of CPIDs and if I look up my CPID here: https://forum.biblepay.org/tools/podcstatus.php?cpid=7c9264559fef3c1c689ee9fc3ff42494it says my last PODC update was on 01/31, whereas my controller wallet constantly keeps sending them (mininmum 6 times yesterday alone). Strangely enough I received a PODC payment just a couple of hours ago. Also, my Sanc says "expired", but I received a payment for it just 3 hours ago ... [Edit]: nevermind, this one also was on a wrong chain ... @MIP: where do you see this "chainwork" information? |
|
|
|
I think I have one sanc in a chain and another in a different one. Could you please help me check the right one? biblepay-cli getblockhash 99171
772497d92be669e62e39cc0308204828e0bad28af948a6cc6695175b8dd52f71
biblepay-cli getblockhash 99171
9d6b806dad1e0091f6b2abcd865f97ef4623ac29036ebf255a863093c2ab3be0 My MacOS wallet is also on the first chain and my windows one is in the second one. All versions (wallets and sancs) are 1.1.8.5 Thanks! Yes, just discovered the same with my sanc that I updated via PPA to 1185. After deleting and resyncin it's now on the correct chain, which is: block 99171 772 ... f71 block 99181 2f9fe432810349468e4506b57efc761ecd59f3da3becbd7470b872edc5f0a2ea |
|
|
|
1.1.8.5 - BiblePay
Mandatory Upgrade
- Proof-of-Giving Goes Live (for heat mining rewards
only, PODC is still live) at block 100,001
- After block 100,000 minimum transaction relay fees increase (to
correct the absurdly low fees)
- At block 106,000 we vote to retire or not retire PODC (making the POG
budget bigger)
** Please upgrade before block 100,001 **
** This upgrade is for the entire network: Sanctuaries and Users **
* SouthXChange, CoinExchange, and GIN have upgraded. Waiting for C-CEX and CryptoBridge. *
Sorry, I still had no time to thoroughly read into POG. One question though: does that mean that from block 100k on all pool mining ("heat mining") will be done with and useless? That would be a shame for all my ARMs. How will this affect the block time? Will the PODC and MN payouts still be paid at roughly the same time frame? In addition to what TheSnat said, I don't plan on taking the pool down unless an unforeseen circumstance arises. The pool will most likely pay about 20% of its normal reward for 30 days after block 100,000. Then if PODC is voted to be retired, after block 107,000 or so, POG payments will then rise very high (for internal wallet POG reward payments) and at the same time, the pool payment will rise to about what it is now. So if you hang in an extra 30 days after the upgrade, and if we retire PODC, then your ARM payments would increase back to where they are now. I think its good to have these extra nodes for more security. Thank you theSnat and Rob, that is interesting and good to know. Let's see how the vote goes at 106k, but I think I will just keep them running on 1185 for now and the upcoming weeks. It's not that they use a lot of power or make unbearable noises, so every little BBP they make is welcome. Looking forward to the upcoming weeks, it's gonna be exciting to see how the transition goes, especially for people like me who haven't tested POG yet. |
|
|
|
1.1.8.5 - BiblePay
Mandatory Upgrade
- Proof-of-Giving Goes Live (for heat mining rewards
only, PODC is still live) at block 100,001
- After block 100,000 minimum transaction relay fees increase (to
correct the absurdly low fees)
- At block 106,000 we vote to retire or not retire PODC (making the POG
budget bigger)
** Please upgrade before block 100,001 **
** This upgrade is for the entire network: Sanctuaries and Users **
* SouthXChange, CoinExchange, and GIN have upgraded. Waiting for C-CEX and CryptoBridge. *
Sorry, I still had no time to thoroughly read into POG. One question though: does that mean that from block 100k on all pool mining ("heat mining") will be done with and useless? That would be a shame for all my ARMs. How will this affect the block time? Will the PODC and MN payouts still be paid at roughly the same time frame? |
|
|
|
I tried to cast my vote in the Emergency Election but all I get is:
"Voting Failed! Check that sanctuaries are registered in masternore.conf?"
Anyone know what I need to do to vote???
You need at least 1 sanctuary. If you have one, just put gobject vote-many 2a5c0805b0a026dd79898d50a27c49c4c2923b767c3735180e43e1dde9914bd2 funding yes into the debug console of your controller wallet. This should do the trick. (Don't make the mistake of checking with "gobject list" though; for BBP this is an endless list taking several minutes to load). |
|
|
|
|
Show Posts
