TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

EVOLUTION



Currently testing Dash 0.14 features in BiblePay v1.4.6.3+



Testnet Download Links:

Windows v.1.4.6.3+:
https://biblepay.org/biblepayevo32develop.exe


Linux PC 32bits
Daemon: https://biblepay.org/biblepayd-evo-testnet-i686-pc-linux-gnu.tar.gz
QT: https://biblepay.org/biblepay-qt-evo-testnet-i686-pc-linux-gnu.tar.gz

Linux PC 64bits
Daemon: https://biblepay.org/biblepayd-evo--testnet-x86_64-pc-linux-gnu.tar.gz
QT: https://biblepay.org/biblepay-qt-evo-testnet-i686-pc-linux-gnu.tar.gz

Linux ARM64 daemon: https://biblepay.org/biblepayd-evo-testnet-aarch64-linux-gnu.tar.gz
Linux ARM32 daemon: https://biblepay.org/biblepayd-evo-testnet-arm-linux-gnueabihf.tar.gz

MacOS QT: https://biblepay.org/biblepaycore-evo-testnet.dmg






Mac-OS QT version here:
https://www.biblepay.org/biblepaycore-testnet.dmg



The purpose of this thread is to test BiblePay-Evolution and our new GSCs.

BiblePay-Evolution is our next release (scheduled for June 2019).

It includes all of the features that Bitcoin and Dash added to Dash over the course of 2018.
Including Segwit, Security updates, Lightning network support, BIPS and DIPS, ChainLocks (51% attack prevention), Deterministic Masternodes, Non-financial transactions, the Depends Development Build environment, C++14 compatibility for devs, more reliable chain syncing, better chain reorganization code, more reliable Governance messages, more efficient messages, HD wallets, High definition display support, InstantSend improvements, and more.

In BIblePay, we have added ABN (Anti-BotNet) mining.  This is a feature that requires miners to include an ABN transaction in each of their blocks that spends coin-age according to the network coin-age requirement (see getmininginfo).

We have also added GSCs (Generic Smart Contracts) client and server side.  The GSC allows BiblePay to abstract payments away from a hard consensus to allow the business logic rules to be malleable and configured so that they do not break consensus rules.  This results in a more reliable prod environment.

Before testing, please read about our GSC's here:
https://wiki.biblepay.org/Generic_Smart_Contracts


To Download BiblePay-Evolution, look for v1.4.0.1+ for windows on this link (at first, we will stay with 32 bit builds until we get close to Prod):
https://biblepay.org/biblepaycore-1.4.0-win32-setup.exe

MIP is working on building linux and MAC builds.  If necessary I will be able to release a link for Ubuntu64 builds/linux also.

To self compile Evo:
https://github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt

Let us start by testing standard core functionality in testnet.

Launching the client:

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

Place the file in ~/.biblepayevolution

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

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

NOTE:  We are keeping BiblePay's blocks, wallet, and chainstate in its own dedicated folder until the end of the test cycle at which time we determine if it is safe to change our pointer back to legacy biblepay files (as Evolutions blocks support a new file format, compressed, and Evo's wallet format has also been upgraded), so it is safer for us to keep these separate for now. 

NOTE: This version will also work side-by-side our production nodes, it will sync blocks, send and receive coins, however it will not peer with legacy Sanctuaries (as their protocol is too old).  We will need to test creation and usage of Sancs in Prod in Evo, and upgrade all legacy Sancs with a mandatory.




Getting started with Evolution:
https://wiki.biblepay.org/Getting_Started_with_Evolution
GSC's:
https://wiki.biblepay.org/Generic_Smart_Contracts
Healing Campaign:
https://wiki.biblepay.org/BiblePay_Healing_Campaign
Street Healing:
https://wiki.biblepay.org/Street_Healing
Spiritual Warfare:
https://wiki.biblepay.org/Spiritual-Warfare-I

How to upgrade a legacy Sanc:
https://forum.biblepay.org/index.php?topic=391.msg5968#msg5968

How to create a deterministic sanc from scratch:
https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html






** Low hassle Syncing from Zero **


EDIT:  NOTE:  Please do not use low hassle syncing in testnet after September 22nd 2019 - as we have reset the chain to block 0, please disregard the following lines.
(Keeping this here so we can port this to prod during the next release).

As our blockchain gets bigger it will be useful for us to release utilities to allow one click syncing from zero.
This first version is only for testnet and linux.  Later, I will extend this to windows and prod.

I will check this into github later, but for now, let me give manual instructions to use the script:

From your linux box:

cd ~/biblepay-evolution
(This is where your source starts, ie /src is one folder down)
wget biblepay.org/syncblocks_testnet.sh
chmod 777 syncblocks_testnet.sh

Now to get in sync for TestNet only, the script automatically deletes just the data files (dont worry, it wont delete anything else), then it pulls down the snapshot of the blocks gzipped and unzips them into the correct places (including the llmq and all necessary governance files), then its up to you re-launch the wallet.  The script does close biblepay as long as your machine supports pkill.

To sync from 0 type:
./syncblocks_testnet.sh

EDIT:

I just created a windows version and tested it on windows 7 and it works.  Will check-in during the next Develop release.

Looks like testnet is working, I have one local node and one VM node synced in testnet, here is the hash:

getblockhash 1960
aa5e6bda46848227f6746cd87242881534c662c763614eb80896c91a1da5f83d

BTW!, We restarted the chain in testnet so please just sync from 0.

Looks like testnet is working, I have one local node and one VM node synced in testnet, here is the hash:

getblockhash 1960
aa5e6bda46848227f6746cd87242881534c662c763614eb80896c91a1da5f83d

BTW!, We restarted the chain in testnet so please just sync from 0.

I'll get a few nodes up today.

Is the chain restart just for testing, or is this being looked at for prod as well?

I'll get a few nodes up today.

Is the chain restart just for testing, or is this being looked at for prod as well?

Only for testnet.

You can sync in prod in evolution with this version.

EDIT:  One of the reasons for this is in Testnet, we changed the Sanc requirement to 1,550,001 (to mirror prod).

Btw, we will need to set up some testnet sancs.

Does anyone need any tBBP?

Only for testnet.

You can sync in prod in evolution with this version.

EDIT:  One of the reasons for this is in Testnet, we changed the Sanc requirement to 1,550,001 (to mirror prod).

Btw, we will need to set up some testnet sancs.

Does anyone need any tBBP?

Sounds good, i'll do some mining on there see how quick it ramps up.

Interesting, the default "Prod' theme is the old pink bars,  testnet default is the belazeel theme, is this intentional?

Sounds good, i'll do some mining on there see how quick it ramps up.

Interesting, the default "Prod' theme is the old pink bars,  testnet default is the belazeel theme, is this intentional?

No - I ported the line that supposed to set the default, not sure why it changed.

I was using Bezaleel the whole time til last night I noticed a new node had the non bez.  Will look at this.

No - I ported the line that supposed to set the default, not sure why it changed.

I was using Bezaleel the whole time til last night I noticed a new node had the non bez.  Will look at this.

I fixed the PNGs for the next version; I verified the default is already set to Bezaleel; I think the 'pick' problem has to do with the name of the key its using (will still check that).


I just started two legacy-type sancs (IE non deterministic) in testnet.


We are now waiting for 80 blocks to pass to see if we can test a GSC.


In the mean time, you guys can do a 'exec cpk nickname' to create a CPK.

Then do a "exec join pog" .


Then wait 40 blocks and see if your system sends a "GSC-Transmission".

I fixed the PNGs for the next version; I verified the default is already set to Bezaleel; I think the 'pick' problem has to do with the name of the key its using (will still check that).


I just started two legacy-type sancs (IE non deterministic) in testnet.


We are now waiting for 80 blocks to pass to see if we can test a GSC.


In the mean time, you guys can do a 'exec cpk nickname' to create a CPK.

Then do a "exec join pog" .


Then wait 40 blocks and see if your system sends a "GSC-Transmission".

I see a notice "every sanctuary (of 1 known ones) is on a newer version than you".

So far i've "earned" 350k bbp, but none has matured yet.   I'll take some tbbp for a mn i supposeyjGK2wqh2M5SMiieyayiqtD2i7EqnwHVLZ

I'll do the register/join as soon as i'm able.

I see a notice "every sanctuary (of 1 known ones) is on a newer version than you".

So far i've "earned" 350k bbp, but none has matured yet.   I'll take some tbbp for a mn i supposeyjGK2wqh2M5SMiieyayiqtD2i7EqnwHVLZ

I'll do the register/join as soon as i'm able.

One interesting thing I just learned (no wonder the Bezaleel setting was already set), QT actually dumps the settings to a place the user doesn't pick (IE the checkbox settings), I think to ~/user/.config/username/settings.conf - so that would explain how we are picking up non-default values, lol, there is a reason for everything.  Ill add a logprintf with the exact location this afternoon.

Sent 2.5 mm.

Please dont mine Toooo fast, as it will slow us all down ha ha.

Ill be back I have to run a couple errands.

Uhhh, I think the notice of the sanc alert is because I set the sancs proto version higher than the wallet version (I was trying to prevent all the errors in the log we are seeing in Prod, because our sancs in prod are too old to peer with the Evo sancs - even the legacy evo compatibility will not work in our case because the BiblePay classic messages are too short, so I believe that fixed that), so Ill increment the core version in the next build to see if that removes the status bar error.

One interesting thing I just learned (no wonder the Bezaleel setting was already set), QT actually dumps the settings to a place the user doesn't pick (IE the checkbox settings), I think to ~/user/.config/username/settings.conf - so that would explain how we are picking up non-default values, lol, there is a reason for everything.  Ill add a logprintf with the exact location this afternoon.

Sent 2.5 mm.

Please dont mine Toooo fast, as it will slow us all down ha ha.

Ill be back I have to run a couple errands.

Uhhh, I think the notice of the sanc alert is because I set the sancs proto version higher than the wallet version (I was trying to prevent all the errors in the log we are seeing in Prod, because our sancs in prod are too old to peer with the Evo sancs - even the legacy evo compatibility will not work in our case because the BiblePay classic messages are too short, so I believe that fixed that), so Ill increment the core version in the next build to see if that removes the status bar error.

Lol it's an old machine running 3 cores mining shouldn't be too crazy but I can scale back if it becomes an issue..

will try to setup sanc tonight

I have set testnet up but it seems that I need tBBP to start with

Lol it's an old machine running 3 cores mining shouldn't be too crazy but I can scale back if it becomes an issue..

will try to setup sanc tonight

Maybe its not you then, I had a few machines running and got the diff up to 1.  Someone came on and got it up to 70, now it dropped to 52.

No problem, it is working its way out.

I have set testnet up but it seems that I need tBBP to start with

Thanks man, we can use the help!

Whats your address?

One interesting thing I just learned (no wonder the Bezaleel setting was already set), QT actually dumps the settings to a place the user doesn't pick (IE the checkbox settings), I think to ~/user/.config/username/settings.conf - so that would explain how we are picking up non-default values, lol, there is a reason for everything.  Ill add a logprintf with the exact location this afternoon.

Sent 2.5 mm.

Please dont mine Toooo fast, as it will slow us all down ha ha.

Ill be back I have to run a couple errands.

Uhhh, I think the notice of the sanc alert is because I set the sancs proto version higher than the wallet version (I was trying to prevent all the errors in the log we are seeing in Prod, because our sancs in prod are too old to peer with the Evo sancs - even the legacy evo compatibility will not work in our case because the BiblePay classic messages are too short, so I believe that fixed that), so Ill increment the core version in the next build to see if that removes the status bar error.

The "mystery" of where Evo is getting its theme-name and checkbox settings is solved. 
The first very good thing I confirmed, is if you delete the Machine settings file, our default really is Bezaleel (for a brand new machine install), so that is very good as new users wont see the pink theme.

(Also in the next version I fixed the PNGs for the other themes that had the invalid icons).

So the checkbox settings are stored here:  /username/.config/Biblepay/ProgramName-Qt-TestOrProd.conf

This explains How the old "./biblepay-qt" settings were auto-migrated to Evo (for test or prod).

So in the end, this is good as regardless of our working dir, settings are migrated, and that means the existing theme is honored.

yd3Nnd7W2Wmy546wBZGPKV1kN2LDmYq1mQ

thanks