Hey Rob, I believe the command getdifficulty causes wallet to crash, it was last message on explorer daemon debug.log with debug=1, and I tested it on a masternode wallet and it crashed that wallet too
Did you type 'getdifficulty' with no params and how many blocks on the sanc that crashed? |
|
|
|
TheRouge on discord is having issue with pool2 . Can you check if block hash is the same. He thinks there might be a fork?
Yes pool2 was on a fork; its been upgraded; both have been rebooted; have him check his hash also before restarting the mining. |
|
|
|
Has the Miner-ocalypse begun? Purepool is handing out very few shares atm. About 20% of what it has before.  I think they are on a fork. |
|
|
|
We integrated the pool with the Walmart API.
46k BBP for $15 Subway Gift card delivered by fedex very quickly.  Thank you for confirming! Thanks for ordering. I ordered one myself and saw on the back of the card that it's reloadable. Its something cool for us to keep in mind if we ever want to reload our users Subway cards. Also, I did take a look at e-mailing gift certificates and made some progress on that, but I need to update everyone later as there are higher priority things going on right now. But I will persistently get back to that project asap as I found one solid and concrete way for BiblePay to e-mail a gift card from the pool with WalMart gift cards. |
|
|
|
Rob, regarding PoG, some questions that will surely be of interest for our community and investors:
- how will the reward distribution be in terms of %?
- Will tithes replace the monthly 10% superblock for orphans or will it add up?
- Will masternode owners keep on having the same share as miners/tithers?
Thank you for the great job.
I'm gathering the answers for this now. |
|
|
|
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. |
|
|
|
./biblepay-cli getblockhash 98978
4d73e1f859c731f61545cb98affe3759f1bf8b5ec7d53ebbd03637faf71cfea5
./biblepay-cli getblockhash 98978
0a63726a48a743a922f6a3a34294854e5d56b4bc8a940603b09de9f7dcb17fda I reindexed the explorer and its on a different chain, how do I know which chain is correct? Ill reindex again and report back I noticed this issue this morning - the pool was on the lighter chain and my win wallet on the heavier chain. I reindexed the pool. To try to resolve this, everyone please upgrade to 1185. I received a couple complaints about the pool throwing "BLOCK_SOLUTION_STALE or INCOMPLETE". This is because the pool didn't agree with the miners chain. Here is what I have now for the current hash on my nodes: getblockhash 99135 e623c6ab3962772518999d1877cc748e916eef6b2c9db287119e5a4e651629c3 Please rm blocks and chainstate and reindex if your hashes differ (after upgrading to 1185). |
|
|
|
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. *
Hi is qiex still in the picture? Sorry, forgot to mention, they upgraded. |
|
|
|
On a side note, I plan on keeping the testnet thread alive while we go live with POG: https://forum.biblepay.org/index.php?action=post;quote=5394;topic=335.405And if we don't have any errors (or just small bugs) I'm going to edit the thread for general purpose testing of the Orphan Letter writing feature in testnet (so we can test editing new letters and sending the outbound letter to compassion and cameroon etc). |
|
|
|
|
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. *
|
|
|
|
Rob Tragedio - comedy part 2... I take popcorn and read what's in the new episode  ) In the third part. I suggest choosing who can mining and who does not. Whats a comedy to me is how you are jumping to conclusion. You realize the code only does what its programmed to do. There is no evidence that POG mining does not work yet. There is only evidence that User A didnt have any coins in the stake balance, and user B did..... We tested all this in testnet. I havent even tried it yet in Prod on windows; working on it... Til then don't assume there is a bug or flaw unless you confirm it through research. I'm open to hearing about any flaws with POG mining in Prod. |
|
|
|
Hi everyone, I received the newsletter today, and I just wanted to come by and say that I'm happy to see that BiblePay is still going strong! Although I'm still struggling to find balance in my life, I am definitely in better shape than a few months ago, and I'm going to see if I can dip my toe in the water again (no promises though). I'll be in the background for now, and maybe helping people out a bit on Telegram if needed It's great to potentially have you back Jaap, welcome back! We missed you. |
|
|
|
yes, so this is why i'm staking 20bpp/rac per every podc update, so where is problem? i'm not staking lower and getting higher payouts stakebalnce said that i have 10m bbp to stake, so i can use it in podc update, no? sunk, why i should not be in bbp team? because i'm using bpp wallet? it is only thing that i'm doing , i'm not hacking/cracking anything if you dont like current rules, change them (already did somehow), of course then announce new rules... rules are programmed in wallet/blockchain... and not somewhere spoken by someone, if wallet allows something then it is allowed and people will be using it no matter what you think Capulo, POG has so many holes. He could not correct one system, he would not do the next one. I'm sorry because I believed in this coin, now it's bottom.
Regarding "could not correct" the current, Sorry but let me inform you (who is obviously not listening to logical reason) what really happened since launch through 2018: - We released POBH vanilla with no CPU restrictions, and the rich kid with a lot of CPUs copied the code out to 300 machines to make more money for himself, but never wanted to upgrade - which caused problems for us because we couldnt issue releases in a timely manner (unless we changed the algo with a hard fork each time) - We reacted by releasing POBH f14000, which rewarded more BBP to mining on distinct nodes (in contrast to distinct cpus) and then that was abused by people who cloned copies of bbp to run multiple full nodes (which caused problems for us, because this vector was over-rewarding a niche greedy group more than the average lone miner) - We released PODC which turned out to be hard to set up for the average user and ended up stagnating our growth level - we need 1 new user per day - not stagnation - Now we move to POG, which is Easy to set up for the average user, uses commodity PCs still, and cannot be overrun by botnets (because there is no reward for multiple CPUs or multiple distinct full nodes) - the reward is based on giving. Again this is not insanity, these are incremental improvements over time. Lets see how our baseline looks in 90 days! If we go from 200 distinct miners to 2000, its obviously an improvement. We want mass participation. I think POG can potentially give us this! Lets be excited. But lets not fantasize and say POG has loopholes. |
|
|
|
Someone added to ticket suggesting we block HTTP, please use HTTPS. Tx - that works Maybe put a simple http redirect for people who try to connect in http Yes, I hear you, we added the http->https redirect and it broke the CORS policy, so I'm working on another alternative now. For now users can again use http or https. |
|
|
|
ok so how it works now? if coin age .5 means half a day then i have more than one day coins in wallet, stakebalance shows them but getboininfo shows no cpid and so
how can i check if coin age is met? or also other new things?
on other side, if coin age si below .5 then cpid is lost? or when it is lost?
I don't think you should be on BiblePay Team any more. The rules are hidden now, sometimes rabbit, sometimes rain. Capulo asked only about rules... Why doesn't he explain it to all the other people that staked 100% BBP for 100% reward, why it is fair for capulo to staked only 10% BBP to get 100% reward? If the rules allow it, it's ok. He did not create rules. He asked about current, because they are changed without the knowledge of others. It's like you have to pay taxes and do not know how much. The "stated rules" are 20 bbp stake per rac. This is what people were expected to obey, just because you found a way around it, doesn't change the stated rules. I'm watching this. Rob covers up, opensource, and then swims like a fish. This is not what investors expect. I'm not covering anything or swimming, we have 5 days left before POG, I'm working as fast as I can to ensure a smooth cutover. On PODC, I just asked yesterday if you possibility violated the .50 age rule and now I am looking into the info we have. We said the sancs would eventually start enforcing the rule, its public - nothing is hidden. You are probably experiencing the pain of that rule, but you haven't explained to us your entire operation - you are clearly not telling us if you are sharing your UTXO, so how can we help you. |
|
|
|
I noticed GRCPool has a banner at the top of their pages: Biblepay has decided to blacklist Gridcoin team from earning rewards. Bums me out. It should really read: Biblepay has decided to reinstate the Team Requirement (like Gridcoin currently does). It hopefully should be a stop gap measure to enable time for a real solution to be coded, but some users were sharing stake back and forth. This meant they were able to get higher rewards than they were designed to (by using a glitch in the system). I'm hopeful there will be a technical solution that would allow for the Team Requirement to be lifted if that is still what the community desires. If the community desired lifting of the team requirement then I think they would want to vote that way. We just had a vote on this very recently (within 10 days) and the supermajority voted to require the team again. (I dont think it is prudent to flood the community with flip-flop polls every other week). |
|
|
|
Ill look at this today, but on a side note everyone: All you really need to do is go to: https://pool.biblepay.org(The only issue is the redirect from HTTP to HTTPS is throwing a CORS violation). |
|
|
|
** CRITICAL NOTE **
For now, if you decide to upgrade early, please do not add tithe=nn to your production config file (otherwise you will auto-tithe to the foundation address and lose the BBP).
I would have thought auto tithing would be in effect in production when the block height is reached. That's good to know. Thanks for the warning. I did install 1185 and put tithe=60 (every hour) already, but I'm not seeing the behavior you mentioned. Maybe it is just with tithe=1 or I'm just lucky. I haven't tried it myself yet, but if you put in "tithe=1" it uses a 4 hour default frequency. It looks like 60 should have been working. Please check the log for this: BiblePayMiner::SendTithe::Error Ill test this asap also. Sun, please enlighten us on this when you get a chance, if we are ready to go live and things are working properly. |
|
|
|
This was only happening on the http:// landing page in IE. Fixed. Please consider using https://. |
|
|
|
yeah its mine, but does not matter look at team total rac, it is dropped by 8 milions so somewhere must be problem and i'm not alone with my rac=0 as i found already was wcg stats picked up correctly by sancs? Have you been sharing your daily UTXO with anyone else? If UTXO coin age < .50, and shared coin-age with another biblepay user, you will receive zero PODC rewards and risk being booted from Team BiblePay. |
|
|
|
|
Show Posts
