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

[sunk818]

So far, we raised $130 USD so far:  240k BBP ($30 USD) and a generous credit card donation of $100. I will close collecting this week and forward the funds to the charities. There is still time to  donate and/or write a note to the kids:

2019 Donate Holiday Gifts for CameroonONE and Kairos children
https://whitewalr.us/2019/cameroonone-kairos-children-gifts.html


Other articles about BiblePay written recently:

Interview with long-time BiblePay supporter Togo
https://whitewalr.us/2019/biblepay-togo-interview.html

Should BiblePay Proof of Distributed Computing (PoDC) 2.0 whitelist teams (GRC, OByte)?
https://whitewalr.us/2019/biblepay-whitelist-grc-podc.html

Christianity, the original blockchain.
https://whitewalr.us/2019/christianity-the-original-blockchain.html

What is BiblePay’s Healing campaign?
https://whitewalr.us/2019/biblepay-gsc-healing.html

BiblePay Nov 2019 Monthly Proposals
https://whitewalr.us/2019/biblepay-nov-2019-proposals.html

[bible_pay]

Hi guys,

I was having some masternode trouble and upgraded all my wallets to the latest releases. My controller wallet is now on version 1.4.5.3 and the masternode wallet is on 1.4.5.4.
The problem is that I don't seem to be able to start my masternode, since the protocol version is different:

Controller wallet:

Code:

  "version": 1040503,
  "protocolversion": 70737,
  "walletversion": 61000,

Masternode wallet:

Code:

  "version": 1040504,
  "protocolversion": 70749,
  "walletversion": 61000,

I built the masternode wallet from source and downloaded the exe from the website for my controller wallet (windows 10 x64).

Any ideas on how to fix this? Can I 'downgrade' the masternode wallet to 1.4.5.3.? Of is that not possible in an easy way and is it easier to just install the controller wallet on a Linux box and build from source for the time being? Or (Rob) will the Windows wallet download on the website also be updated to 1.4.5.4. shortly?

Thanks!

I had that 70749 checked in (in mainnet) for about 12 hours; you probably upgraded during that time  - but now its been rolled back to 70737.

Please just grab latest again and re-compile.

We seem to be OK now.

Affirmative; you can't start the sanc if the proto version is 70749, it must be 70737.  (That was the main problem).

I'm moving to plan B in testnet today; we will need to modify the testnet branch to peer with prod for the rollout later this month.

[bible_pay]

So far, we raised $130 USD so far:  240k BBP ($30 USD) and a generous credit card donation of $100. I will close collecting this week and forward the funds to the charities. There is still time to  donate and/or write a note to the kids:

2019 Donate Holiday Gifts for CameroonONE and Kairos children
https://whitewalr.us/2019/cameroonone-kairos-children-gifts.html


Other articles about BiblePay written recently:

Interview with long-time BiblePay supporter Togo
https://whitewalr.us/2019/biblepay-togo-interview.html

Should BiblePay Proof of Distributed Computing (PoDC) 2.0 whitelist teams (GRC, OByte)?
https://whitewalr.us/2019/biblepay-whitelist-grc-podc.html

Christianity, the original blockchain.
https://whitewalr.us/2019/christianity-the-original-blockchain.html

What is BiblePay’s Healing campaign?
https://whitewalr.us/2019/biblepay-gsc-healing.html

BiblePay Nov 2019 Monthly Proposals
https://whitewalr.us/2019/biblepay-nov-2019-proposals.html

Sorry for the delay ; I donated also.

[sunk818]

Sorry for the delay ; I donated also.

No problem Rob! Thanks for your donation. We may have differences of opinion, but I never doubt your generosity and heart for the children!

[bible_pay]

It looks like the superblock did not emit for block 161560, most likely because of the switch to and back from DM mode.

I will investigate this.  In the mean time, I enabled deterministic mode for all sancs, so please upgrade your sanctuary to deterministic if you have not yet.
(As I dont want to take any chances with the next superblock).

Most likely the problem was that all the votes were erased for the GSC contract for this height, but they were displaying on the screen as if everything was fine, but behind the scenes they might have been invalid.

We will need to watch this next daily superblock closely and see how the sigs are formed and that they are honored in DM mode.

[bible_pay]

Info on the truth about flavor enhancers in food tested at one point on aborted fetal cells:
https://familycouncil.org/?p=4666

I checked this out because the Christian gossip was Pepsi, Gatorade and Mountain dew use flavor enhancers from Senomyx that 'contain' aborted fetal cells from a cloned baby from 1979 (using the cloned kidney cells for the flavor enhancer).  This leads people to believe the Illuminati is trying to get us used to 'eating aborted baby parts' leading to cannibalism.

Anyway the truth is Senomyx does have an R&D dept using the cloned cells to *test* new flavors against, but the 'artificial flavors' they end up selling are not made with aborted fetal cells.  Another words, they created an artificial tongue out of the aborted baby to run electrochemical tests on the flavors against.

Obviously this does not make it right, but at least we know we are not actually drinking fetus tissue.

[bible_pay]

Could someone please give us an update on Tokok, if they are working yet?

I find it very unsettling to not receive a reply from them in 24 hours.

Let me know and tomorrow if we have not heard back, lets talk about forming a grievance.

[coinsinspect]

The two Biblepay explorers do not match.

[bible_pay]

Anchor Point post:
USS Harry Truman deployed to Persian Gulf on Dec 4th:

https://www.youtube.com/watch?v=RKfEJF1CGrU


Keep an eye on this aircraft carrier.  The prophecy is one of our aircraft carriers gets blown up by Iran.

[jsheets1970]

Could someone please give us an update on Tokok, if they are working yet?

I find it very unsettling to not receive a reply from them in 24 hours.

Let me know and tomorrow if we have not heard back, lets talk about forming a grievance.

Have not heard from them either and no deposits have gone through at this point in time

[MIP]

Could someone please give us an update on Tokok, if they are working yet?

I find it very unsettling to not receive a reply from them in 24 hours.

Let me know and tomorrow if we have not heard back, lets talk about forming a grievance.

Have not heard from them either and no deposits have gone through at this point in time

Same here. Support chat says that "all agents are busy" when they were available in few minutes some weeks ago

[capulo]

i just break 1mhash/s with single machine

[2019-12-05 08:39:44] Total: 1188 khash/s

4x e5-4657l v2, 48/96 core, 640gb ram

[inblue]

It looks like the superblock did not emit for block 161560, most likely because of the switch to and back from DM mode.

I will investigate this.  In the mean time, I enabled deterministic mode for all sancs, so please upgrade your sanctuary to deterministic if you have not yet.
(As I dont want to take any chances with the next superblock).

Most likely the problem was that all the votes were erased for the GSC contract for this height, but they were displaying on the screen as if everything was fine, but behind the scenes they might have been invalid.

We will need to watch this next daily superblock closely and see how the sigs are formed and that they are honored in DM mode.

I am reporting three things I've found regarding the recent DM change.

1. I still have classic sanctuaries and the tabs for them disappeared in my wallet and I didn't upgrade the wallet or anything, I am on 1.4.5.3. Now only the DIP3 tab is there.

2. My sanctuaries crashed and after I restarted them, they are now stuck on this error: Waiting for ProTx to appear on-chain

3. The wallet now finishes the governance objects sync 10x faster than it used to and then when I type "exec health", I get "Our internal PAM hash disagrees with the network."

[MIP]

It looks like the superblock did not emit for block 161560, most likely because of the switch to and back from DM mode.

I will investigate this.  In the mean time, I enabled deterministic mode for all sancs, so please upgrade your sanctuary to deterministic if you have not yet.
(As I dont want to take any chances with the next superblock).

Most likely the problem was that all the votes were erased for the GSC contract for this height, but they were displaying on the screen as if everything was fine, but behind the scenes they might have been invalid.

We will need to watch this next daily superblock closely and see how the sigs are formed and that they are honored in DM mode.

I am reporting three things I've found regarding the recent DM change.

1. I still have classic sanctuaries and the tabs for them disappeared in my wallet and I didn't upgrade the wallet or anything, I am on 1.4.5.3. Now only the DIP3 tab is there.

2. My sanctuaries crashed and after I restarted them, they are now stuck on this error: Waiting for ProTx to appear on-chain

3. The wallet now finishes the governance objects sync 10x faster and then when I type "exec health", I get "Our internal PAM hash disagrees with the network."

Rob said this:
" In the mean time, I enabled deterministic mode for all sancs, so please upgrade your sanctuary to deterministic if you have not yet.
(As I dont want to take any chances with the next superblock)."

Please follow this guide:

https://www.reddit.com/r/BiblePay/comments/clyxyc/upgrading_masternodes_sanctuaries_to/

[inblue]

Rob said this:
" In the mean time, I enabled deterministic mode for all sancs, so please upgrade your sanctuary to deterministic if you have not yet.
(As I dont want to take any chances with the next superblock)."

Please follow this guide:

https://www.reddit.com/r/BiblePay/comments/clyxyc/upgrading_masternodes_sanctuaries_to/

I am aware of the DIP3 upgrade procedure. I read every post carefully, I think it's not time for classic sanctuaries to stop working yet, take a look at this:

The most probable outcome is we will focus on a Christmas mandatory upgrade and release all of this at once.

The biggest disruption this will require is everyone will need to be on deterministic sanctuaries by Christmas.  I am working with Apollon now to find out if they will support us during the cutover (or not).  If we do not have support from Apollon and Satoshi, we will recommend users who are about to be left behind use the new non-standard port feature to start a sanc.  But in the mean time I will do my best to set us up with a seamless path.

So I expected a mandatory release for classic sanctuaries to be deprecated.

But the most important point of my post is that something is wrong with governance right now, which doesn't have anything to do with my sanctuaries being classic or DIP3.

[sunk818]

Looks like my pool wallet (french pool) forked about 10 hours ago. I restarted mine and workers are submitting shares again.

web site: http://sunpool.whitewalr.us

http://5.135.183.202

stratum+tcp://sunpool.whitewalr.us:3032

stratum+tcp://5.135.183.202:3032

Hopefully, it'll run on the right chain. Looks like nomp and leopool aren't doing so well.

BiblePay network stability has been poor since we moved to 1.4.5.x

[jaapgvk]

Hi guys,

I was having some masternode trouble and upgraded all my wallets to the latest releases. My controller wallet is now on version 1.4.5.3 and the masternode wallet is on 1.4.5.4.
The problem is that I don't seem to be able to start my masternode, since the protocol version is different:

Controller wallet:

Code:

  "version": 1040503,
  "protocolversion": 70737,
  "walletversion": 61000,

Masternode wallet:

Code:

  "version": 1040504,
  "protocolversion": 70749,
  "walletversion": 61000,

I built the masternode wallet from source and downloaded the exe from the website for my controller wallet (windows 10 x64).

Any ideas on how to fix this? Can I 'downgrade' the masternode wallet to 1.4.5.3.? Of is that not possible in an easy way and is it easier to just install the controller wallet on a Linux box and build from source for the time being? Or (Rob) will the Windows wallet download on the website also be updated to 1.4.5.4. shortly?

Thanks!

I had that 70749 checked in (in mainnet) for about 12 hours; you probably upgraded during that time  - but now its been rolled back to 70737.

Please just grab latest again and re-compile.

We seem to be OK now.

Affirmative; you can't start the sanc if the proto version is 70749, it must be 70737.  (That was the main problem).

I'm moving to plan B in testnet today; we will need to modify the testnet branch to peer with prod for the rollout later this month.

Check! I re-compiled and now they are on the same protocol version Thanks!

Also: thank you for the suggestion MIP, that was my plan-B.

[togoshigekata]

The two Biblepay explorers do not match.

https://chainz.cryptoid.info/bbp/
http://explorer.biblepay.org/

Block 161668
https://chainz.cryptoid.info/bbp/block.dws?161668.htm
http://explorer.biblepay.org/block/f4283bb95a946f514271e1ce3aaa121facbb408afd5e4d26f187b2ed7e72a474

Looks like theyre both on same block now

Block 161668 Hash:
f4283bb95a946f514271e1ce3aaa121facbb408afd5e4d26f187b2ed7e72a474

Is this the correct chain?

[MIP]

The two Biblepay explorers do not match.

https://chainz.cryptoid.info/bbp/
http://explorer.biblepay.org/

Block 161668
https://chainz.cryptoid.info/bbp/block.dws?161668.htm
http://explorer.biblepay.org/block/f4283bb95a946f514271e1ce3aaa121facbb408afd5e4d26f187b2ed7e72a474

Looks like theyre both on same block now

Block 161668 Hash:
f4283bb95a946f514271e1ce3aaa121facbb408afd5e4d26f187b2ed7e72a474

Is this the correct chain?

Seems so... I have the same in all my nodes.

[bible_pay]

Rob said this:
" In the mean time, I enabled deterministic mode for all sancs, so please upgrade your sanctuary to deterministic if you have not yet.
(As I dont want to take any chances with the next superblock)."

Please follow this guide:

https://www.reddit.com/r/BiblePay/comments/clyxyc/upgrading_masternodes_sanctuaries_to/

I am aware of the DIP3 upgrade procedure. I read every post carefully, I think it's not time for classic sanctuaries to stop working yet, take a look at this:

The most probable outcome is we will focus on a Christmas mandatory upgrade and release all of this at once.

The biggest disruption this will require is everyone will need to be on deterministic sanctuaries by Christmas.  I am working with Apollon now to find out if they will support us during the cutover (or not).  If we do not have support from Apollon and Satoshi, we will recommend users who are about to be left behind use the new non-standard port feature to start a sanc.  But in the mean time I will do my best to set us up with a seamless path.

So I expected a mandatory release for classic sanctuaries to be deprecated.

But the most important point of my post is that something is wrong with governance right now, which doesn't have anything to do with my sanctuaries being classic or DIP3.

I wanted to wait til Christmas to force the cutover to DM also, as the last thing I wanted to do was add more instability.

However, I had no choice but to flip the spork for DM early after finding out the votes being cast by the classic sanctuaries are not being counted in DM mode once that switch was thrown (even though it was reverted).

So now we are running in pure deterministic mode in the mainnet branch.

Please upgrade to DM, Im sorry for the inconvenience.

EDIT: As far as the PAM hash not matching, this would not be a good time to check that, but to try to explain part of that now:  The PAM hash does not necessarily have to match for the network to be healthy, but Yes it should match in certain circumstances.  First, the supermajority does need to have a matching PAM hash.  For yours to match you must be on the same version, with the node synced, and with 'mnsync status' showing 999.  Then lets check it about 50% through the day (into the GSC contract).  At this point, most of the vote levels should be counted.  Then your PAM hash should match the supermajority of the sancs.  The one with the highest vote levels has an affinity programmed in to be voted in.  You would have to learn more about 'gobject listwild' to see if your sanc is #2 or #3 in the voting levels and those have different PAM hashes.