|
I noticed nomp.biblepay.org was kind of sluggish so I bounced it.
Please anyone let me know if it gets sluggish again and Ill try to find the root cause.
|
|
|
|
Does anybody know the status of the Biblepay pool? I will need to do some CPU mining to get the stake funds necessary for PODC 2.0. Thanks!
It looks like its up, have you switched over to nomp? http://nomp.biblepay.orgNo I have not, my config file still points to pool.biblepay.org. Will that work or should I switch over? I have full instructions on how to pool mine. https://whitewalr.us/2019/biblepay-nomp-pool-mining.htmlI believe only the new external miner works with the NOMP pools, with the just wallet you can only solo mine, Please anyone correct me if Im mistaken https://wiki.biblepay.org/POBH_SetupYou can certainly use the wallet miner if you want to solo mine, but you get better performance using the external miner. Some have claimed the wallet is 90% efficient, but so far, have been unable to replicate this claim. On the CPUs, I've tried... it is closer to 75% to 80%. Still a vast improvement from the wallet miner before, but you'd still do better to use the external miner (for solo or pool). More details on the comparison here -- thanks to Marty on Discord for testing some different CPUs: https://whitewalr.us/2020/bbp-solo-hashrate.htmlBeen pool mining for a couple days now, seems to be working fine but I have not yet received any payouts from the pool. I know it's supposed to take at least 12 hours but it's been over 48 at this point. Do I just need to keep waiting? Thanks! Which pool are you mining against, and in your command line settings for bbpminer, do you have the address as part of the command line the payments should be flowing to in there? If you are mining against nomp.biblepay.org could you please paste your bbp address? Hi! Here is my command line: bbpminer-x86.exe -o stratum+tcp://nomp.biblepay.org:3032 -u BG4cah66HTF4pCYsVS4K7kGCxER7VRQFWK -p x -t 4 Thanks! I see you are in 5 solved blocks in "Historical Stats" (You can view this from the top menu by searching for bg4c*). The nomp pool pays out 102 blocks after the height you solved it; so basically in about 100 more blocks you should start seeing these 5 payments on your end. |
|
|
|
Yeah, I got my burnt DWS back 2 days after the maturity date ended; so I believe you will get it on the maturity height. |
|
|
|
hi Rob,
i have been podc mining for days and have not received a payment.
very strange.
I have added some money to my staking wallet. also my cpuid comes up on the website so im a bit confused.
f1205d2ce902f1f1990ae02c5469e499
Thanks in advance.
Your 99% working .. but a couple things. Your RAC of 2858 requires a daily stake of 32K coin age. You did successfully send one good stake out yesterday: 08:42:43  exec sentgsc BFYvhTNBmjt8ZXmkvVj5UJPFy77WQap3Xf "886e853323bf119320372cb9c53251fd0ab76bb3ab0f1aa08fb3c4efc191459a": "Points: 0, Campaign: WCG, CoinAge: 0, Donation: 0.00, Height: 167589, Date: 01-04-2020 05:29:41", "a579145a9140d1f36bed8347c91447f7e4d45aa69cf2c75650fd581a7b1788ab": "Points: 32014, Campaign: WCG, CoinAge: 32014, Donation: 0.00, Height: 167794, Date: 01-05-2020 06:01:39", "f964067d2ac2f8b2508c81eb96a180de037f6ab6a9bbc846f858e105c74c650f": "Points: 0, Campaign: WCG, CoinAge: 0, Donation: 0.00, Height: 167999, Date: 01-06-2020 05:53:52", "Total": 32013.80629469835 However #1, it takes 48 hours to receive the payments, so please wait until 1-7-2020 for the one you sent above at height 167794. Problem #2: You must ensure the wallet is open during the daily sendgsc wcg height (you can find the height in exec rac, that is height 168202 (see Next_podc_gsc_transmission). Another words, these escrow tx's must be sent once per day to stay in the leaderboard. I dont see you in the leaderboard right now, so it looks like what happened is you sent one at 167999, but it sent 0 (probably due to not having enough coinage in the *external purse*). You can send one manually by typing: sendgscc wcg Maybe the problem is you dont have enough funds in your cpk external purse. You may need to send some BBP to your cpk. Or you can type 'exec bankroll 50 5000' for example. This only needs done once. To find out, type 'exec rac' and paste it here and we can look at your available coinage. Or go to coin control and see how much is in your CPK address? Thanks i will wait till tomorrow. as far as i know i have 150k bbp in external purse. i will check in the morning as i am away from the machine. i will also send you the rac data too. Thank you I seem to have had a payment come in so it seems to be working, but i get this message when i excecute exec rac 07:53:18  exec rac 07:53:18  { "Command": "rac", "cpid": "f1205d2ce902f1f1990ae02c5469e499", "temporary_cpid": "f1205d2ce902f1f1990ae02c5469e499", "Error": "Your CPID is linked to your CPK, but we are unable to find your research records in WCG; most likely because you are not in team BiblePay yet.", "Step 1": "Log into your WCG account at 'worldcommunitygrid.org' with your WCG E-mail address and WCG password.", "Step 2": "Click Settings | My Profile. Record your 'Username' and 'Verification Code' and your 'CPID' (Cross-Project-ID).", "Step 3": "Click Settings | Data Sharing. Ensure the 'Display my Data' radio button is selected. Click Save. ", "Step 4": "Click My Contribution | My Team. If you are not part of Team 'BiblePay' click Join Team | Search | BiblePay | Select BiblePay | Click Join Team | Save.", "Step 5": "NOTE: After choosing your team, and starting your research, please give WCG 24 hours for the CPID to propagate into BBP. In the mean time you can start Boinc research - and ensure the computer is performing WCG tasks. ", "Step 6": "From our RPC console, type, exec associate your_username your_verification_code", "Step 7": "Wait for 5 blocks to pass. Then type 'exec rac' again, and see if you are linked! ", "Step 8": "Once you are linked you will receive daily rewards. Please read about our minimum stake requirements per RAC here: wiki.biblepay.org/PODC" } according to wcg i am definitely part of the team. Ok, so in this case it does not look like its the core client now that we fixed that pesky rac associate bug , but lets dig deeper. So I see your CPID here: https://boinc.netsoft-online.com/e107_plugins/boinc/get_user.php?cpid=f1205d2ce902f1f1990ae02c5469e499So I know you have 4K active rac and you are part of biblepay. Looking at todays WCG file directly in the source you are not in there. Could you please check your wcg web account and verify this: "Step 3": "Click Settings | Data Sharing. Ensure the 'Display my Data' radio button is selected. Click Save. ", Could you please let us know if that needed changed to Data Sharing also? Then we will know this is the root cause. It will probably take 24 hours once you change it to know if it worked. Thanks. Its strange that you worked for a couple days though. If this is not it, could you please email me at rob@biblepay.org and we will open a case with IBM together and trace this problem? |
|
|
|
Does anybody know the status of the Biblepay pool? I will need to do some CPU mining to get the stake funds necessary for PODC 2.0. Thanks!
It looks like its up, have you switched over to nomp? http://nomp.biblepay.orgNo I have not, my config file still points to pool.biblepay.org. Will that work or should I switch over? I have full instructions on how to pool mine. https://whitewalr.us/2019/biblepay-nomp-pool-mining.htmlI believe only the new external miner works with the NOMP pools, with the just wallet you can only solo mine, Please anyone correct me if Im mistaken https://wiki.biblepay.org/POBH_SetupYou can certainly use the wallet miner if you want to solo mine, but you get better performance using the external miner. Some have claimed the wallet is 90% efficient, but so far, have been unable to replicate this claim. On the CPUs, I've tried... it is closer to 75% to 80%. Still a vast improvement from the wallet miner before, but you'd still do better to use the external miner (for solo or pool). More details on the comparison here -- thanks to Marty on Discord for testing some different CPUs: https://whitewalr.us/2020/bbp-solo-hashrate.htmlBeen pool mining for a couple days now, seems to be working fine but I have not yet received any payouts from the pool. I know it's supposed to take at least 12 hours but it's been over 48 at this point. Do I just need to keep waiting? Thanks! Which pool are you mining against, and in your command line settings for bbpminer, do you have the address as part of the command line the payments should be flowing to in there? If you are mining against nomp.biblepay.org could you please paste your bbp address? |
|
|
|
for dws: I think you need to wait 48 hours after maturity (more likely two block days - 205 x 2). Rob said he wants charity donations via PayPal or credit card. To me, unless I'm wrong, that means he wants giving to be done off the BiblePay blockchain. Charity continues to be the biggest marketing identity of this coin since the beginning (see radio show from June 2018: https://www.canarycryradio.com/2018/06/01/flyby-what-is-biblepay/). Obviously, charity will continue it sounds like the hope is that anyone that receives BBP will 1) HODL, 2) Not sell to recoup their giving, 3) Not use directly for charity. If the BBP/BTC price is high, then you can give the fiat equivalent easily, but I wonder what would have happened if charities received max BBP per month because the BBP price is low. You can not support every child this way, but giving say 5M BBP to CameroonONE and 2.5M BBP to Kairos when prices are low seems more sustainable if you want to continue the "10% to charity" marketing. I just feel that with making donation via fiat (PayPal, CC, or check) you remove a lot of visibility, transparency, and gives BiblePay less of a use case. Why does BiblePay need to exist then? "Why does BiblePay need to exist then?" In my opinion is a deceptive conclusion (It alludes to the accusation that because I am recommending a fiat payment to cameroon-one or Kairos that we are not helping children, which is false). Whether a user pays a currently owed balance in fiat, or whether I paid COMPASSION in fiat for a given month has no bearing on who is actually footing the bill. You are forgetting that BiblePay is paying the POOM miner back for the sponsored child payment. So the true comparison is this: Scenario A: The user pays in fiat and gets a tax deduction and a BBP refund; BiblePay still sponsored the child because it came out of our GSC contracts charity budget for POOM. Scenario B: We pay for the child out of the governance budget, liquidate it first and pay compassion FIAT later and no user gets a tax deduction. Both are very similar but scenario A has very little market pressure (up front). Neither are perfect, but thats not the point. The point is we are still supporting hundreds of children therefore not only biblepay has a purpose but weve done a lot of good in the world. And technically right now Compassion has not ended yet, so we do still have over 120 current children. We can update the infographic when we lose compassion to a number closer to the total poom. Either way we still give more than 10% to orphan-charity and thats the primary reason we started. I do feel that if our market is sluggish for 7 more months in a row, we should open a thread and discuss dynamic orphan charity expenses (IE limiting the entire charity side , payroll and governance expenses to a sliding scale of emissions) based on our price. But I prayed about this, and God (through the Holy spirit) does not want to start on this yet, I think some dynamics are currently changing so I want to hold off on this and keep things stable for a while if possible. But in the mean time we can look at our environment and try to see if there are ways to decentralize the sponsorships in a smarter way that relies less on any central and single foundation or authority or person. |
|
|
|
hi Rob,
i have been podc mining for days and have not received a payment.
very strange.
I have added some money to my staking wallet. also my cpuid comes up on the website so im a bit confused.
f1205d2ce902f1f1990ae02c5469e499
Thanks in advance.
Your 99% working .. but a couple things. Your RAC of 2858 requires a daily stake of 32K coin age. You did successfully send one good stake out yesterday: 08:42:43  exec sentgsc BFYvhTNBmjt8ZXmkvVj5UJPFy77WQap3Xf "886e853323bf119320372cb9c53251fd0ab76bb3ab0f1aa08fb3c4efc191459a": "Points: 0, Campaign: WCG, CoinAge: 0, Donation: 0.00, Height: 167589, Date: 01-04-2020 05:29:41", "a579145a9140d1f36bed8347c91447f7e4d45aa69cf2c75650fd581a7b1788ab": "Points: 32014, Campaign: WCG, CoinAge: 32014, Donation: 0.00, Height: 167794, Date: 01-05-2020 06:01:39", "f964067d2ac2f8b2508c81eb96a180de037f6ab6a9bbc846f858e105c74c650f": "Points: 0, Campaign: WCG, CoinAge: 0, Donation: 0.00, Height: 167999, Date: 01-06-2020 05:53:52", "Total": 32013.80629469835 However #1, it takes 48 hours to receive the payments, so please wait until 1-7-2020 for the one you sent above at height 167794. Problem #2: You must ensure the wallet is open during the daily sendgsc wcg height (you can find the height in exec rac, that is height 168202 (see Next_podc_gsc_transmission). Another words, these escrow tx's must be sent once per day to stay in the leaderboard. I dont see you in the leaderboard right now, so it looks like what happened is you sent one at 167999, but it sent 0 (probably due to not having enough coinage in the *external purse*). You can send one manually by typing: sendgscc wcg Maybe the problem is you dont have enough funds in your cpk external purse. You may need to send some BBP to your cpk. Or you can type 'exec bankroll 50 5000' for example. This only needs done once. To find out, type 'exec rac' and paste it here and we can look at your available coinage. Or go to coin control and see how much is in your CPK address? |
|
|
|
Does anybody know the status of the Biblepay pool? I will need to do some CPU mining to get the stake funds necessary for PODC 2.0. Thanks!
It looks like its up, have you switched over to nomp? http://nomp.biblepay.org |
|
|
|
Rob, how do we determine what the maximum total daily emission for the block is supposed to be? https://chainz.cryptoid.info/bbp/block.dws?167710.htmBlock value is 839,516.3287386 BBP , but I think based on the calculation of the leaderboard, the daily superblock is closer to 852k BBP? (216,754.3 BBP / 0.2543 prominence = 852,356 BBP). Is the total daily superblock value something we can query? I know due to deflation is this value decreases after each "monthly" superblock. I'm trying to make a Google Sheets with approximate bbp mined (its usd value) and approximate electrical use (power cost) to see what the break even for PoDC miners will be. To query the daily superblock: exec getgovlimit gsc_height, see the "Limit" column. To calculate the superblock amount: subtract the "Subsidy" (POW) and the "Sanc" amount from the "Limit", then subtract 20000 bbp (the original max block value). This should equal the total contract amount that day - except it might be a tiny bit lower due to our cameroon-one and kairos caps (which use the reverse engineered price and limit the payments for those projects). Note the deflation is calculated in, but this only changes once per 31 days or so, so if you want to see a decrease in deflation use a future block number way in the future (IE 'exec getgovlimit 372710' shows a 465K limit). |
|
|
|
Sun, will you please test cancelsponsorship and let me know if it deletes a child from listchildren.
been trying to get camerooneone to at least give bbp for the ones I sponsored about 7 children. once I get that squared away I can test the feature. it's been 4 days now. I don't know what you mean. The sentence appears to have multiple meanings. No rush. Once we know one dissapears from listchildren, then I can move to the next step. |
|
|
|
|
Sun, will you please test cancelsponsorship and let me know if it deletes a child from listchildren.
|
|
|
|
BiblePay
1.4.8.5 - Leisure Upgrade
- Fix glitch where exec rac occasionaly comes unlinked - Allow researchers with insufficient collateral to receive commensurate RAC (NOTE: This does not go into effect until the next Mandatory Sanctuary Upgrade is announced on the forum!) - Added cancelsponsorship rpc command (cancelsponsorship charityname childid authorize) to allow cancellation of a POOM child - Removed ability to pay for POOM sponsorship via BBP. An updated wiki page will be announced on the forum with the updated payment info. https://wiki.biblepay.org/Paying_For_a_POOM_Sponsored_Child- Fixed error message in exec associate for non-bbp researchers. Allow cpid to be associated if RAC > 256 for non-bbp researcher. - Added unlock wallet verbiage to vote failure in Voting UI page.
|
|
|
|
auto sending tx didnt work again  It's been working consistently for everyone and your last post was due to a low send amount (in contrast to not sending); please scan your log for this and post the error message in between: ("\nSending out GSC Transmissions...%f\n") ("\nEGSCQP::SendOutGSCs::Unable to create client side GSC transaction. (See Log [%s]). ", sError); |
|
|
|
Is the Dynamic Whale Stake pool full? I guess too many people in the jacuzzi already?  https://chainz.cryptoid.info/bbp/address.dws?B4T5ciTCkWauSqVAcVKy88ofjcSasUkSYU.htm23:14:33 exec dws 100 7 I_AGREE
23:14:33

{
"Command": "dws",
"Staking Amount": 100,
"Duration": 7,
"Reclaim Date": "01-10-2020 07:14:33",
"Return Address": "xxx",
"DWU": "78.8647",
"Error (Not Sent)": "Sorry, our annual saturation level is too great to accept this burn until we free up more room."
}
Yeah, unfortunately its already full. I think what we will need to do is give it a break for a couple months, and then we will change the rules (for a mandatory release), to allow at least 20* more transactions in. We will need to lower the highest DWU cap, increase the sensitivity of change, etc. This will result in lower rewards but with the goal of generally having it online and available. |
|
|
|
Just as a non-related test I rebooted the wallet and measured the governance sync time - and it was only about 30 seconds total (to reach mnsync status 999), and it consumed about 75k of bandwidth!
This is great, and I feel we must give credit where credit is due - the deterministic sancs are behaving much better than the old hybrid branch.
Ill go as far as saying, I think we got very unlucky when we picked the hybrid version. We didn't have a horrible time with PODC 1.0 when we used the September 2017 branch of Dash. But we had a horrendous time throughout most of 2019 with the hybrid branch.
Lets look towards a bright future with DM, concerning reliability (and with chainlocks, and we are looking forward to a bright fork-free future also!).
There has been a big improvement in terms of memory, bandwidth and CPU footprint As usual thanks to your efforts and constance. Congratulations Rob, and happy new year to all the Biblepay community! Let's hope 2020 brings the fruits of all the innovation in this project. Thanks MIP, we couldn't have done it without you and also thanks to the entire community. |
|
|
|
Sunk, wasn't this the bug Rob said he was fixing in the next version? IIRC you just had to restart the wallet and it would show correct.
I think the restart of the wallet (or entire system) with exec rac not showing the link: https://bitcointalk.org/index.php?topic=2388064.msg53470948The specific issue is that a CPID can't associate when it is not part of team BiblePay. The ^1.6 requirement works for non-BBP team but the current workflow seems to require you join team BiblePay (in version 1.4.8.4) then change to another team. Well, mine was associated back in PoDC 1.0, so not sure if that was a reason why it worked in 2.0. Otherwise, I've never been a member of team BBP and I believe that is the version I used to associate. Restarting the client would show it correctly being associated. Please let me see if I can clarify this as it can get complicated without the veil being removed: You can definitely associate a non-biblepay team researcher using 'exec associate' without joining team BBP first, as long as that CPID has > 256 RAC. The only complexity here is : When the RAC is < 256, the wallet does not recognize the researcher until they build up more RAC (this is because there are 21,000 non-bbp researchers with rac > 256 we memorize, this is to save resources in the core wallet). The error message does stop the flow simply because the tx was not actually sent, but that can be forced in the current version by adding the 'true' flag. The next version changes the error message to be more friendly and lets the transaction flow immediately out if it found your CPID with > 256 rac on a non biblepay team. For the BiblePay team, we memorize *all* the CPIDs to allow more user friendly messages to be displayed, so the flow can be a tiny bit different for people with < 256 rac on team BBP. The next version is being prepared for release. |
|
|
|
|
Just as a non-related test I rebooted the wallet and measured the governance sync time - and it was only about 30 seconds total (to reach mnsync status 999), and it consumed about 75k of bandwidth!
This is great, and I feel we must give credit where credit is due - the deterministic sancs are behaving much better than the old hybrid branch.
Ill go as far as saying, I think we got very unlucky when we picked the hybrid version. We didn't have a horrible time with PODC 1.0 when we used the September 2017 branch of Dash. But we had a horrendous time throughout most of 2019 with the hybrid branch.
Lets look towards a bright future with DM, concerning reliability (and with chainlocks, and we are looking forward to a bright fork-free future also!).
|
|
|
|
Thanks a lot Togo, this is extremely helpful! Updated. |
|
|
|
Happy New Year All.
I have just come back from the holidays and trying to associate my work community grid account.
Ok i managed to get a bit further now.
It says im not part of biblepay team. will wait a little while and try again.
Happy New Years! Yeah, if you have any trouble with 'exec rac' after waiting 12 hours (since the researchers are loaded twice per day) let me know the cpid and Ill search. But it does take a while to sync changes to the team, or to the data sharing settings, etc. |
|
|
|
I've upgraded my sanctuaries to the latest wallet version (1.4.8.4.) and cleaned them as per Togo's guide. Everything seems to be working fine, but I can't seem to vote. Voting failed! Failed to vote 0 time(s). (Check that sanctuaries are DIP3? Also you must wait 3 minutes in-between re-votes due to network rules.) They are in the DIP3 list and I've been getting rewards consistently. Both controller wallet and sanctuary wallets are on the same chain, and they are not on a fork as far as I can tell... Can you please post the voting command including the id you are using, as I voted manually for Togos proposal and it worked but I did it from the rpc. I tried to vote using the GUI. I can't remember the command to pull all the Proposal ID's, and I don't know if I can copy them from the GUI proposal tab  So I can't try it from the rpc for now. How can I find a list of all the current Proposal ID's that I can copy/paste so I can try it from the rpc? There used to be an overview of all the proposals on pool.biblepay.org right? Ok yes cause I would like to try to reproduce with one that actually throws the gov exception error, so one way, is to type: gobject list all proposals Could you try voting on the woocommerce one? 98e09d657fb771f1559ab046af76d295ebde16f563d35ff9bc95ff738ae725f7 gobject vote-many objid funding yes And let me know if successful and also, then try voting on the one you tried earlier and paste the vote string so I can reproduce? Note that we have not passed the mandatory height yet, but thats another topic (partially related though). Yes, it's working fine manually from the rpc  17:46:33

gobject vote-many 98e09d657fb771f1559ab046af76d295ebde16f563d35ff9bc95ff738ae725f7 funding yes
17:46:33

{
"overall": "Voted successfully X time(s) and failed 0 time(s).",
From the GUI I tried voting for all the proposals that are currently in the 'Proposals' list, and they all got the same error I mentioned before. I think we are OK then, the reason you cant vote now is we are past the 'end epoch period' for the monthly gov proposal block (166050). (I confirm it is actually too late to vote to change the outcome of this monthly trigger). Also there are a couple changes coming - at height 166075, we switch over to pure dip3 DM mode. So lets do this, please wait til next months proposals start kicking in then lets vote for one as early as possible and the error should go away. (We tested that in testnet). I do confirm I receive the same error as you in my GUI so yes we are on the same page. I tried voting again from the GUI on some new proposals and initially got the same error as last time: Voting failed! Failed to vote 0 time(s). (Check that sanctuaries are DIP3? Also you must wait 3 minutes in-between re-votes due to network rules.) Then, I tried voting from the command line and I understand the 'error' now. I believe that in the past, when voting via the GUI, you got a popup asking you to type your password to unlock your wallet before voting. Now, it seems' that pop-up no longer appears. So I've been trying to vote with a locked wallet :p When I unlock the wallet from the debug console first, and then vote from the GUI, I don't have problems voting. But I guess that I was so used to doing everything from the GUI that I didn't notice that the popup didn't show, and the 'error' didn't say anything about perhaps having to unlock your wallet before voting, so I didn't think about that. Was the popup removed for a reason? I don't know about the popup; realize that we have gone through so many hundreds of K of changes running the hybrid mode and now dip3 mode, its hard to say; note that there is even a different case that your wallet is going to go through when we enable chainlocks in a few days (two more DIPS actually get set in mainnet soon), so what Im saying is we will be running the pure voting DM mode in a few days, and now the error can be streamlined. In any case, I just modified the error message to ask the user to unlock the wallet if its locked. |
|
|
|
|
Show Posts
