Bible Pay

Read 38214 times

  • Rob Andrews
  • Administrator

    • 2956


    • 49
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #465 on: September 06, 2020, 12:26:55 PM »
Ah, I see. That makes perfect sense, thanks for clearing it up.  :)
I think we will see in the upcoming days and weeks, whether or not all of this works out; I'm quite excited on that.

Yes, me too, I've seen an uptick in interest on SX for BBP over the last couple days also.  Despite massive sales to raise funds for Cameroon-one (from the sancs) all the coins were bought up (I think volume was about 30 mm and 20 mm over a couple days).  Also I see the total sell wall has decreased by 10MM - which is stellar news, as that is our biggest hole to climb out of.  It will be amazing when we have a free floating price again.

My guess is some of the people in the sell wall gave up and locked it in DWS (because Ive seen 10 MM in new DWS over the last 2 days).

To calculate the sell wall size, I look at the sum of BBP for sale up to 9 satoshi. (Its currently about 60MM).

I consider TOKOK neutral as it has a miniscule sell wall (and a miniscule amount of ether buyers unfortunately).







4300 BBP


  • Rob Andrews
  • Administrator

    • 2956


    • 49
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more


  • MIP
  • Developer

    • 302


    • 38
    • February 13, 2018, 11:55:52 AM
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #467 on: September 07, 2020, 02:50:46 AM »
** SANCTUARY CHAIN APPEAL **

...
Will you all please restart your sanctuaries with "-erasechain=1".  This will erase the LLMQ folder and resync.

Once you are done with this, 'quorum list' should return empty (in contrast to returning 3 quorums (50_60 and 2 * 5_60).

Please do this immediately, because we are trying to jumpstart the quorums before block 220,000.

Thanks!

My two working sancs are showing empty, but my controller wallet shows 3 entries in quorum list. Is this ok or do I have to do anything else?


  • Rob Andrews
  • Administrator

    • 2956


    • 49
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #468 on: September 07, 2020, 11:19:02 AM »
It looks like Bololex now requires you to link your account to Telegram to vote.
But on the bright side, we are in third place, please keep the impetus!

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




4300 BBP


  • Rob Andrews
  • Administrator

    • 2956


    • 49
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #469 on: September 07, 2020, 11:31:03 AM »
My two working sancs are showing empty, but my controller wallet shows 3 entries in quorum list. Is this ok or do I have to do anything else?

Great on the sancs!

The controller wallet with an empty quorum list should be good.

Once we get our first quorum I will post the hash and we can all run the command to see it in 'quorum list'.

Now I'm working on tracing the block on why the sancs are not signing the commitments.

I heard back from Song and miningpool.fun has resynced, so the pools are good and not causing a problem.



4300 BBP


  • Rob Andrews
  • Administrator

    • 2956


    • 49
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #470 on: September 07, 2020, 07:33:03 PM »
** Sanctuary LLMQ Appeal Part II **

We have found one more issue, strictly pertaining to sanctuaries.  Anyone who is running a sanc on a nonstandard port (IE a port other than 40,000), and using a self compiled node, will you please upgrade to 1.5.2.6?

I believe part of the problem with our LLMQs is they are not connecting to nonstandard ports (until v1.5.2.6).

I will announce more tomorrow to release 1.5.2.6 officially but I want to get a jumpstart on this for any sancs who can possibly upgrade early.

Thanks!



4300 BBP


  • Rob Andrews
  • Administrator

    • 2956


    • 49
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #471 on: September 08, 2020, 06:37:52 PM »
BiblePay - 1.5.2.7
Mandatory Upgrade for Sanctuaries
Leisure Upgrade for Network

- Allow sanctuary non-standard ports
- Ease up on checking POOS scores to once every 30 minutes after client is warmed up
- Ensure LLMQ quorums start

Sanctuaries:  Please upgrade immediately, as we need to form quorums before block 220,000.

EDIT:  Once you upgrade please ensure the version is 1.5.2.7.



4300 BBP
« Last Edit: September 09, 2020, 11:42:01 AM by Rob Andrews »


  • dave_bbp
  • Jr. Member

    • 21


    • 4
    • April 11, 2020, 12:25:14 PM
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #472 on: September 09, 2020, 03:12:24 PM »
Is there some fork situation going on? I updated my sanc to 1527 and it's currently  in sync with the chainz explorer.
Then I realized that my windows wallet was 2 blocks ahead, so I just restarted it with -erasechain=1 and let it resync completely. However, now it's almost 20 blocks ahead and the hash (e. g. for 219239) doesn't fit either.

Code: [Select]
getblockhash 219239:
Windows (freshly synced): 6643678c9716b26d11b47d733832736fbc387b873169f6ea0f1a43e3e3115648
Sanc/Explorer:
 265e8c70593ce83b9ee7f288e79cd65411f40ba1f144781c201ab0ef7717628b 


  • 001ar
  • Newbie

    • 1


    • 0
    • May 09, 2020, 02:07:00 PM
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #473 on: September 09, 2020, 03:30:51 PM »
Southexchange says that BBP wallet is disabled?


  • Rob Andrews
  • Administrator

    • 2956


    • 49
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #474 on: September 09, 2020, 08:36:42 PM »
Is there some fork situation going on? I updated my sanc to 1527 and it's currently  in sync with the chainz explorer.
Then I realized that my windows wallet was 2 blocks ahead, so I just restarted it with -erasechain=1 and let it resync completely. However, now it's almost 20 blocks ahead and the hash (e. g. for 219239) doesn't fit either.

Code: [Select]
getblockhash 219239:
Windows (freshly synced): 6643678c9716b26d11b47d733832736fbc387b873169f6ea0f1a43e3e3115648
Sanc/Explorer:
 265e8c70593ce83b9ee7f288e79cd65411f40ba1f144781c201ab0ef7717628b 


I see the issue-- the problem is our LLMQs are causing a consensus change. 

And, the root of the problem is I was under the impression that LLMQs did not cause a consensus change.
(After looking at these for a while, I now see the way it can happen is if we don't enforce LLMQ rules one of the two pools can break a rule, then the clients that look back can fork).

Anyway, what we are going to have to do is halt the exchanges and ask everyone to upgrade to 1.5.2.7 now.

(1.5.2.7 requires everyone to transition to LLMQs at the same time at block 220,000 and enforces them at the same time). 
Hopefully all that works properly after 220,000, but one step at a time.


In the mean time, please go ahead and upgrade to 1.5.2.7.

Let me notify the block explorers first, so we have a good block hash to refer to.

Sorry for the inconvenience everyone.




4300 BBP


  • Rob Andrews
  • Administrator

    • 2956


    • 49
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #475 on: September 09, 2020, 08:39:00 PM »
BiblePay - 1.5.2.7
Mandatory Upgrade

- Allow sanctuary non-standard ports
- Ease up on checking POOS scores to once every 30 minutes after client is warmed up
- Ensure LLMQ quorums start

Sanctuaries:  Please upgrade immediately, as we need to form quorums before block 220,000.


Our exchanges are in maintenance.



4300 BBP


  • Rob Andrews
  • Administrator

    • 2956


    • 49
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #476 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

    • 518


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

2600 BBP


  • Rob Andrews
  • Administrator

    • 2956


    • 49
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #478 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

    • 2956


    • 49
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« Reply #479 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 »