Bible Pay

Read 19343 times

  • Rob Andrews
  • Administrator

    • 2795


    • 43
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #480 on: September 09, 2020, 08:41:17 PM »
While we are waiting for the BXs to upgrade, please shoot for this blockhash:


getblockhash 219305

5f1147e0fa8d8ecf4b953674535da5710944cfb7044874cd58d394818cb042b1


EDIT:

Btw, most likely you can recover to block 219305 with 'exec reassesschains' if you dont automatically get there.
I don't think everyone needs to resync the whole chain in this case.






4300 BBP
« Last Edit: September 09, 2020, 08:46:04 PM by Rob Andrews »


  • togoshigekata
  • Hero Member

    • 522


    • 26
    • September 01, 2017, 10:21:10 AM
    • USA
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #481 on: September 09, 2020, 09:28:39 PM »
Explorer.BiblePay has been updated:
https://explorer.biblepay.org/

2600 BBP


  • Rob Andrews
  • Administrator

    • 2795


    • 43
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #482 on: September 11, 2020, 08:09:05 AM »
** LLMQ Update **

The block explorers have been updated.  You can now refer to either block explorer for the correct block hash.

** Bololex Voting **

https://bololex.com/voting?order=trending

Please continue to vote, as we have a real chance of being in second place!  If we win second place, we receive 4 stars (worth $1200 USD) and will be 40% of the way towards a free listing!



4200 BBP


  • Rob Andrews
  • Administrator

    • 2795


    • 43
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #483 on: September 11, 2020, 08:34:48 AM »
** Please stay with BIBLEPAY during the thick and thin **

I want to take the time to mention how much we at BiblePay appreciate the long term loyalty of the original users who stayed with us through thick and thin. 

Thank you for being here with us while we go through troubling times.

Let me explain the situation with LLMQs as compared to 'normal mandatory upgrades'.  A while back, I vowed that we would do everything possible to prevent forks (we would upgrade to randomx, we would pre-test any consensus changes and verify they will not add fork risk, and we will resist changes that cause danger to consensus).  Realize that we have been doing all of that, and now we have an environment where the chain itself is very resilient to forks:  RandomX is a proof-of-work algorithm that is merge mined, and not fork prone, and requires real energy to create blocks.  Our APM feature is deterministic.  Our daily GSC contracts (for PODC) are as strong as Dash masternode voting calls for budget blocks.

Now, realize with LLMQ, we are enabling this system to gain more features that we do not currently have.  LLMQs facilitate chainlocks (which provide even greater security), instantsend 10 second transactions, and POSE/POOS banning.  Realize that POSE banning is no longer based on an unstrusted call to a port, it now requires a node to participate in the quorum signing session to determine the node is alive. 

I've been following DASH's rollout of Spork 6 (new sigs), Spork 17 (Quorum DKG), Spork 19 (Chainlocks), DIP3 (Deterministic MNs),  and DIP8 (new LLMQ version+ChainLocks enforced), and hopefully everyone realizes that Dash's codebase was released in multiple steps (.14 to .15) with certain on-chain votes that took place between Spork enable and DIP-enable bitsets.  And we have been mostly successful in mirroring the rollout order, so as to simulate the requirements to jump from DM->LLMQ->Chainlocks.  We successfully enabled Deterministic Sanctuaries without forking, and LLMQs phase 1.  However in June when we rolled out ChainLocks, our environment contained everything except DIP0008 (because this required an on-chain vote for a bit in versionbitsstate for dip8 - that I was not aware existed).  At that point I shut off ChainLocks and LLMQ at the spork level and decided we need to wait for this September mandatory to perform the update.   (Some may ask, why was this LLMQ consensus breaker not caught in testnet?  We actually did test this LLMQ execution in full in testnet, but the difference in testnet is we had 6 sanctuaries solo mining, but in prod, we have two pools.  The exact difference in prod is the pools do not enforce LLMQ rules during the first 205 block transition phase, while in testnet those that solo mined *did* enforce LLMQ rules - hence a difference between test and prods rollout.)

Now we are in the midst of rolling out LLMQs again.  My view of LLMQs is just as strict as our POW consensus quality level.  Now that we know that LLMQ has its own set of consensus rules (Enforcing non-null commitments, enforcing complete quorums with lookback over the last day), we are committed to staying on LLMQs once they are enabled and preventing any future consensus breaking events, forever.  I go as far as saying we need to lock in our chain security after this event and not touch it for a couple years, but instead focus on value adds in the gospel area and in the area where we release other groundbreaking features (in contrast to adding any consensus changes in the future).

With this all said, let me lay out a roadmap over the next 1000 blocks so everyone, and exchanges know exactly what our plans are.  The current height is 219570.

Roadmap over the next 1000 Blocks:

Height             Event

220000            At this height, everyone will be running 1.5.2.7.  We will verify that LLMQ quorums started.  Exchanges are in maintenance.  We will let the quorums run for 205 blocks and provide an update. 
220400            At this height, we will ask some users to erase the chain and resync.  We need to confirm that the quorums are loaded and mirror the rest of the network.  We also need to confirm the chain syncs from zero and the quorums have not broken any business logic.
220500            At this height, we will ask the exchanges to upgrade and open again for trading.  At this point, LLMQs are a success. 
220700            At this height we can enable other features that rely on LLMQ, such as chainlocks and 10 second IX transactions.



Thank you for being patient with BiblePay during this transition to Long Living Masternode Quorums.






4200 BBP
« Last Edit: September 11, 2020, 08:36:38 AM by Rob Andrews »


  • Rob Andrews
  • Administrator

    • 2795


    • 43
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #484 on: September 13, 2020, 07:50:09 PM »
** Great News Today ! **

1)  Bololex awarded us 3 stars!  We came in 3rd place!  Congratulations and Thank you to all who voted!
https://bololex.com/voting?order=trending

At this rate, we can be listed in 90 days if we win 2 more times!

2)  We have transitioned past block 220,000 without any issues so far!
Now LLMQs are working in production, in phase 1.  In this phase, sanctuaries will start POSE banning each other, and theoretically in 200 more blocks we will see the sanctuary count drop.  Which will increase the ROI for POOS sponsorships (by sanctuaries).

However, we still need to do some testing in 400 blocks to ensure everything works and we can sync from zero.

So far, I am excited to see a few sanctuaries being POSE banned.

EDIT:

If you want to see the percentage of bad sanctuaries compared to the good, you can check and see who is signing the llmqs with this command:
quorum info 1 7efc37fd6be6f89733ff27bda7c85d3c3663539bbbc2a729bf9aa49d765634b2





4200 BBP
« Last Edit: September 13, 2020, 07:52:18 PM by Rob Andrews »


  • noxpost
  • Newbie

    • 19


    • 6
    • April 10, 2018, 07:24:15 AM
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #485 on: September 14, 2020, 07:35:53 AM »
That's awesome news! Personally, my fingers are crossed that we aren't all here for 2 more votes - I would so love to see us raptured this week (if it is really God's timing, which I can't say for sure, although there are many encouraging signs). But if we're here, the mission remains clear, doing what's possible to bring Christ to the world, and in return, lead the world to Christ.

Let's keep it up.


  • Rob Andrews
  • Administrator

    • 2795


    • 43
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #486 on: September 14, 2020, 09:54:03 AM »
That's awesome news! Personally, my fingers are crossed that we aren't all here for 2 more votes - I would so love to see us raptured this week (if it is really God's timing, which I can't say for sure, although there are many encouraging signs). But if we're here, the mission remains clear, doing what's possible to bring Christ to the world, and in return, lead the world to Christ.

Let's keep it up.

Hi Nox!

Yeah, I'm with you 100%, although I feel that there is a high liklihood that we will unfortunately have to see some tribulation first (Matthew 24:9, Then they will deliver you up...), however I pray every morning to be worthy of the rapture, or the wilderness event (Rev 12). 

But on the optimistic side, it really appears to be the most profound time to be alive, in all of human history (except the years when Jesus actually walked on the Earth).

We have an unbelievable week coming up:  President Trump is signing the UAE (and other middle East countries) peace deal with Kushner tomorrow on Sep 15th, and on a side note...  Ive done a little research on that deal... and it looks very, very bad for the US (prophetically speaking), because it does divide Israel (it stops expansion on the West bank, promises non-Jews a two state solution, and paves the way to split Jerusalem).  Remember in Zechariah, whoever splits my land, I will split their land.  It also tries to nullify the 1967 borders of Israel that they obviously fought and won by Gods hand.  It basically makes me see that Trump, was elected for the goodwill of the Christians and worked Pro-Israel policies during the first 3.5 years, but in reality at the end is becoming Judas.  He will be the betrayer that secretly lures Israel into something they really should not do (compromise the land lines that Abraham was promised by God), and the way this is secretly being done is disguising this as competely pro-peace and pro-Israel, but, in effect drawing Netanyahu to do something that is very grave.  When Netanyahu becomes a party of this he will be on the opposite side of God.

The other is Rosh Hashana itself - its the culmination of the resting period between the Revelation 12 sign of 2017; and "No man knows the day or the hour", and, after Teshuva - a time of repentance, the beginning of possible judgement (that we saints are supposed to pray that does not occur). 

Then we have the election, and all the civil unrest that goes along with it.

Its an unbelievable year.  Some prophets had said a year ago, that 2020 will be the year where people will say this was the US before 2020, and this is the US after 2020.  Another said Before Trump and after Trump.   



4200 BBP


  • dave_bbp
  • Newbie

    • 13


    • 4
    • April 11, 2020, 12:25:14 PM
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #487 on: September 14, 2020, 10:24:59 AM »
** Great News Today ! **

2)  We have transitioned past block 220,000 without any issues so far!
Now LLMQs are working in production, in phase 1.  In this phase, sanctuaries will start POSE banning each other, and theoretically in 200 more blocks we will see the sanctuary count drop.  Which will increase the ROI for POOS sponsorships (by sanctuaries).

However, we still need to do some testing in 400 blocks to ensure everything works and we can sync from zero.

So far, I am excited to see a few sanctuaries being POSE banned.

EDIT:

If you want to see the percentage of bad sanctuaries compared to the good, you can check and see who is signing the llmqs with this command:
quorum info 1 7efc37fd6be6f89733ff27bda7c85d3c3663539bbbc2a729bf9aa49d765634b2



Hi again. I think there is still some kind of forking going on. I tested your command on my sanc and it worked fine.
On my controller wallet it created an error and I checked back and saw, that this was on another chain. So I restarted it with "erasechain=1".
Now I came home from work at it is synced again, but again on a completely different chain. Also the 2 explorers seem to be different/stopped.

Could anyone please confirm, that my Sanc (at least) is on the right one?
Code: [Select]
getblockhash 220161
4f5e6f7278bf3e3e713e58c7bdf70cc0e035a37d7e0b7a22fdd9f9c53b195880


  • MIP
  • Developer

    • 272


    • 33
    • February 13, 2018, 11:55:52 AM
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #488 on: September 14, 2020, 11:02:02 AM »
Hi again. I think there is still some kind of forking going on. I tested your command on my sanc and it worked fine.
On my controller wallet it created an error and I checked back and saw, that this was on another chain. So I restarted it with "erasechain=1".
Now I came home from work at it is synced again, but again on a completely different chain. Also the 2 explorers seem to be different/stopped.

Could anyone please confirm, that my Sanc (at least) is on the right one?
Code: [Select]
getblockhash 220161
4f5e6f7278bf3e3e713e58c7bdf70cc0e035a37d7e0b7a22fdd9f9c53b195880

I have my sancs stalled at block 220054 (I guess that would explain why they start piling up ban score).
My controller wallet is at the same chain as your sanc.

I will run reassesschain and see what happens.


  • MIP
  • Developer

    • 272


    • 33
    • February 13, 2018, 11:55:52 AM
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #489 on: September 14, 2020, 12:08:21 PM »
I have my sancs stalled at block 220054 (I guess that would explain why they start piling up ban score).
My controller wallet is at the same chain as your sanc.

I will run reassesschain and see what happens.

Neither reassesschain nor -erasechain=1 worked for me, they are still in an apparently stalled chain:

Code: [Select]
{
  "version": 1050207,
  "protocolversion": 70760,
  "walletversion": 61000,
  "balance": 1896.98274919,
  "privatesend_balance": 0.00000000,
  "blocks": 220056,
  "timeoffset": 0,
  "connections": 14,
  "proxy": "",
  "difficulty": 0.001729468455635417,
  "testnet": false,
  "keypoololdest": 1572338947,
  "keypoolsize": 1000,
  "paytxfee": 0.00000000,
  "relayfee": 0.01000000,
  "errors": "Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade."

I am running 1.5.2.7b (Leisure Update), donīt know if this has anything to do with it.


  • Rob Andrews
  • Administrator

    • 2795


    • 43
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #490 on: September 14, 2020, 02:12:43 PM »
Neither reassesschain nor -erasechain=1 worked for me, they are still in an apparently stalled chain:

Code: [Select]
{
  "version": 1050207,
  "protocolversion": 70760,
  "walletversion": 61000,
  "balance": 1896.98274919,
  "privatesend_balance": 0.00000000,
  "blocks": 220056,
  "timeoffset": 0,
  "connections": 14,
  "proxy": "",
  "difficulty": 0.001729468455635417,
  "testnet": false,
  "keypoololdest": 1572338947,
  "keypoolsize": 1000,
  "paytxfee": 0.00000000,
  "relayfee": 0.01000000,
  "errors": "Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade."

I am running 1.5.2.7b (Leisure Update), donīt know if this has anything to do with it.


On 1.5.2.7, everyone should be running the latest version (1.5.2.7b).  The only difference between the two is  for sanctuaries:  If you are running the latest version, your sanctuary will start.  If you are running the one that we replaced and did not intend to release (that has been overwritten), it will not start.  So no, it has nothing to do with 1.5.2.7.


Let me investigate this thoroughly.  I have a feeling it has to do with the percentage of sancs who upgraded and bound themselves to the chain with more work.  Checking.





4200 BBP


Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #491 on: September 14, 2020, 06:17:01 PM »
Hi all!
So how do you add proposals on here ??


Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #492 on: September 14, 2020, 09:06:15 PM »
Sync issues between two explorers:
https://chainz.cryptoid.info/bbp/
https://explorer.biblepay.org/


1000 BBP


  • sunk818
  • Sr. Member

    • 447


    • 27
    • April 24, 2018, 02:02:20 PM
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #493 on: September 14, 2020, 09:29:42 PM »
I'm not able to download the latest binary for some reason.http://biblepay.org/biblepay-win64.exeForbiddenYou don't have permission to access this resource.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.

2700 BBP
BH6oxjLkyz3z8FYpvU3ZR7PTZ31Xt9DkXZ


  • Rob Andrews
  • Administrator

    • 2795


    • 43
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #494 on: September 14, 2020, 11:36:43 PM »
I'm not able to download the latest binary for some reason.http://biblepay.org/biblepay-win64.exeForbiddenYou don't have permission to access this resource.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.

Hmm, Rebuilding now.

Checking...


4200 BBP