BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[MIP]

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.

[sunk818]

Is the Dynamic Whale Stake pool full? I guess too many people in the jacuzzi already?

https://chainz.cryptoid.info/bbp/address.dws?B4T5ciTCkWauSqVAcVKy88ofjcSasUkSYU.htm

Code:

23: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."
}

[Budinga]

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 think its now working.

Thank you

[jaapgvk]

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.

Thanks for your insight I think that adjusting is error message is a good way to remind people like me.

And great to hear about the efficiency improvements with deterministic sanctuaries.

[slovakia]

auto sending tx  didnt work again 

[orbis]

auto sending tx  didnt work again 

same.

same here. i found it 5 blocks prior payment block

[sunk818]

Healing Campaign https://wiki.biblepay.org/BiblePay_Healing_Campaign

I noticed in Suns guide there are config settings: https://whitewalr.us/2019/biblepay-gsc-healing.html

Are there rewards to tithing more than 1 BBP? Are there rewards for coin-age? Is this sort of a smaller version of POG?

Yes, it works just like the retired PoG except there's no cubed root for tithing more. 1 BBP is the same as 100 BBP for healing.

It is just what inputs you use and how much coin age you used in the tx.

The prominence will add up to 5% from the "Points" used (aka coin age).

24.8M BBP coin age was contributed.

Sakic is 16.7M out of 24.8M BBP.

16750 / 24805 = 67.52%

Multiply that by 5% and you have 3.376% prominence, or rounded up 3.38% for Sakic.

Code:

  "HEALING: B4hsUDPZUfrku9Aa9PHzDNf4KBh33zCwhA [Sakic], Pts: 16750.00": "3.38%",
  "HEALING: BFDwrSv2Yd1jBrAyieDGBYuTivNxoNXism [akkin4], Pts: 3428.00": "0.69%",
  "HEALING: BLDtfba6uPzcfw5YpS9VTUNat3JBckLjD4 [oncoapop3], Pts: 4329.00": "0.87%",
  "HEALING: BQXj5kV9LVUZGF4ipFCRmkzBbZu366grJt [randrews], Pts: 298.00": "0.06%",

[sunk818]

Welcome new PoDC miners:

Sm1th
E2teban
julius003
sf7kkn99
kraken76
w2m_xx
Anfecare16
Budinga  
GRom81  
gabaldiit  
mikeyanjelo

[cuarc001]

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.

[sunk818]

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.msg53470948

The 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.

[bolobala]

Hi, at step6 in RPC to link cpid, i got a message "Campaign wcg does not exist. (code - 1)" when type exec associate mynickname verification code. Please tell me how to solve it, thank you.

[sunk818]

Hi, at step6 in RPC to link cpid, i got a message "Campaign wcg does not exist. (code - 1)" when type exec associate mynickname verification code. Please tell me how to solve it, thank you.

did you do the follow the directions here?

https://wiki.biblepay.org/PODC_Setup

exec cpk bolobala

Do this command above and wait 6 confirmations.

[cuarc001]

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.msg53470948

The 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.

[bible_pay]

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.msg53470948

The 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.

[bible_pay]

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.

[bible_pay]

Is the Dynamic Whale Stake pool full? I guess too many people in the jacuzzi already?

https://chainz.cryptoid.info/bbp/address.dws?B4T5ciTCkWauSqVAcVKy88ofjcSasUkSYU.htm

Code:

23: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. 

[bible_pay]

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);

[bible_pay]

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.

[bible_pay]

Sun, will you please test cancelsponsorship and let me know if it deletes a child from listchildren.

[sunk818]

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.htm

Block 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.