June 2024 (Q2) - Babylon Falling Release

June 2024 Release - Babylon Falling



Welcome to TestNet - Babylon Falling!




Testing Starts: May 4th, 2024
Testing Ends: June 4th, 2024



In this thread we will be testing:

- Ability to create a sanctuary of each size (Altar, Sanctuary, Temple) with collateral amounts (455,001, 4,500,001, and 45,000,001) and corresponding payments of (10%, 100%, 1000%)
  a. Verify each size of sanc can register properly and appear in the deterministic masternode list
  b. Verify the payment amount on each sanc
  c. Verify the chain can sync from 0 after we solve some temple blocks
- Verify the monthly superblock still works and emits and is the correct amount
- Verify Quorums form
- Verify Temple and Altar coins in wallet lock in coin control and require an unlock (like regular sancs) so they dont get spent by accident
- Verify inactive sanctuaries (IE investor nodes) receive 50%
- Verify masternodelist shows the Tribe for a Temple
- Cutover height     ________195350_________________________
- Block hash :
getblockhash 195350
00001a40008c45546bbc725caf32e5238bfdd70eca982c0d220c0f92542dfb9c








Explain Changes to Entire BiblePay Network:   

- Explanation :

___________________________



Wiki Articles:



Older - Create a Sanc:
https://wiki.biblepay.org/Create_Sanctuary


Starting Version:    0.20.3:


(Please ensure your version is greater than this, in order to sync.  See post #2 for current hash.


Testnet Download Links:


Ready:

     Windows 64-bit:      https://biblepay.org/biblepay64develop.exe
     Linux :  Self compiled version ready (please post if you want Ubuntu binary)



NOT READY (ask before trying):
     (Inquire first before downloading)
     MacOS QT: https://biblepay.org/biblepay-harvest-develop.dmg

     Linux 64 bits (QT/biblepayd/biblepay-cli) zip:  https://biblepay.org/bbp-lin-develop-64.zip


To self compile:
git pull origin develop

https://github.com/biblepay/biblepay/blob/develop/BuildBiblePayDevelop.txt






CONFIGURING FOR TESTNET:

Create a biblepaytest.conf file with the following contents:
testnet=1

Place the file in ~/.biblepaycore


Start testnet by typing:
./biblepay-qt -conf=biblepaytest.conf

(Note the blocks and chainstate will sync into the ./biblepaycore/testnet3 folder.

NOTE: If you only have one machine, you can run in testnet side by side a prod node.

To create a TestNet Sanctuary:

https://wiki.biblepay.org/Create_Sanctuary

__________________________________________________________________________________________________________________________________________________________________________________________



                                                                   OUR BIBLEPAY CORE TESTERS



#1 -

#2 -  Mr. A

#3 - Rob Andrews

#4 -

Alright the time has come for Babylon Falling.

The Windows wallet is ready for download.


I created 3 public testnet sancs:  2 regular and 1 temple.  I also created an investor Altar.

So now we can test LLMQs, and payment amounts, governance proposal and watchman on the wall.

Just downloaded the wallet.

Just downloaded the wallet.

Ok, verify that you are synced to the ref blockhash in Testnet and the version of the wallet is => new wallet.

I will check block reward amount for sancs asap.

I already entered a gov proposal and voted on it - waiting for watchman on the wall to create a trigger.

Ok, verify that you are synced to the ref blockhash in Testnet and the version of the wallet is => new wallet.

I will check block reward amount for sancs asap.

I already entered a gov proposal and voted on it - waiting for watchman on the wall to create a trigger.

Downloaded and synced seems to be working as intended.

Mine is 3 weeks behind to sync,
It was stuck yesterday. I started it again today.

Mine is 3 weeks behind to sync,
It was stuck yesterday. I started it again today.

Probably just an addnode as I verified the chain was clean up to best block with a reindex.

Try 'addnode sanc22.biblepay.org add' from the rpc.  Then wait a half hour to make sure you have peers.
Then verify the block hash I posted in the OP post.

So there were about 99 issues to fix while refactoring (maybe 1000, lost count) and Im very happy with the outcome as this ended up being a solid wallet.
Almost every test passed, including moving to sha256, and mining, and the reward schedule and the governance add and view and watchman voting.
One issue that is present, is quorums are not forming on the sancs and chainlocks is not working.  This is pretty normal however if quorums arent even forming.
So Ill be looking into that next.

If anyone was asking earlier how to mine, you just set up a sanctuary on testnet and when the sanc boots, it will launch one miner thread.
You can see it with getmininginfo.
Right now in testnet you can manually mine if you want with:
setgenerate true 1
But we will probably turn that off for prod as we dont want pump n dumpers mining (even though they dont get paid for it).

Downloaded and synced seems to be working as intended.

Do you want me to send you some tBBP?
If so what is address and how much do you need?

Do you want me to send you some tBBP?
If so what is address and how much do you need?

Anything really so i can just test the Sanc functions
yZ4LmikQgzq5q1sc9SRsyQ4JeKDw4YCSme

Thanks

Anything really so i can just test the Sanc functions
yZ4LmikQgzq5q1sc9SRsyQ4JeKDw4YCSme

Thanks

Hi rob i just realised my wallet is stuck 2 days behind i cant seem to get it to sync again any ideas?

Hi rob i just realised my wallet is stuck 2 days behind i cant seem to get it to sync again any ideas?

Hi, yeah, I see the problem; although I tested a full resync a few times before the latest release I apparently added some consensus breaking logic later in the development cycle that caused this.

So, Im adding some fixes for this and will need to release a mandatory testnet upgrade to get around this.
Let me do a round of testing with my 3 testnet sancs to ensure we are staying in sync and resyncing first to avoid issues.

Ill post when I have the mandatory upgrade ready.  Thanks for testing.

Hi, yeah, I see the problem; although I tested a full resync a few times before the latest release I apparently added some consensus breaking logic later in the development cycle that caused this.

So, Im adding some fixes for this and will need to release a mandatory testnet upgrade to get around this.
Let me do a round of testing with my 3 testnet sancs to ensure we are staying in sync and resyncing first to avoid issues.

Ill post when I have the mandatory upgrade ready.  Thanks for testing.

Thank you

Chainlocks is working, along with LLMQs in TestNet now.

Will be posting very soon with updated wallet.

See attachment.

Mandatory upgrade for TestNet
Biblepay v0.20.18

Code has been released to github.
Windows is ready for download (see link in op post).
Verify your wallet upgrades to newest version and then start with "-reindex=1".
Sync to block 215583 hash 000015d648efc77ed5f25743c388780fae99307a38aab6efe1f6641e5b7e9a3c.

Let me know if you are synced.