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

My windows testnet node is still giving me trouble,  refuses to find any peers.

Side-note:  I got a bit frustrated and deleted the wallet.dat along with all other info .. so no more coins lol

Also,  I noticed the "testnet" client creates/uses the SAN directory in the main client's folder, not the testnet3 folder.

The error message for all peers is: using obsolete version 209 after DIP3 activation; disconnecting


Erm... nevermined

Didn't realize the download link had changed, so i was stuck on .0.6

fixing now

Was this a test? lol

Great to have you back in the gang! 
So on the failure to find peers, I truly believe it was the old peer version disconnect - (as last week I added my 3 public nodes to our compiled in testned seed list) so technically I think people should be able to find a peer if they run the latest.

Yes, on the SAN, we do have only one (as there is also another intentional quirk in Dash, that causes it to use the root anyway, so for this SAN dir, we actually store prayers_test in a separate file - so thats OK.

So yeah I didnt enter that prayer, thats quite a long prayer.  Will take a look at these prayers asap.

Great to have you back in the gang! 
So on the failure to find peers, I truly believe it was the old peer version disconnect - (as last week I added my 3 public nodes to our compiled in testned seed list) so technically I think people should be able to find a peer if they run the latest.

Yes, on the SAN, we do have only one (as there is also another intentional quirk in Dash, that causes it to use the root anyway, so for this SAN dir, we actually store prayers_test in a separate file - so thats OK.

So yeah I didnt enter that prayer, thats quite a long prayer.  Will take a look at these prayers asap.

Working on getting the tools setup for testnet, will see about adding a campaigns tab as well

We have a monthly budget coming at 30135.  I just entered 3 proposals.  Feel free to enter some more and vote up-down so we can test watchman.

Working on getting the tools setup for testnet, will see about adding a campaigns tab as well

Great, I will look into adding features for Grandma starting tomorrow. 
I think I will add "Leaderboard" as an rpc command (without exec) asap to show the 'exec prominence' defaults also.

We have a monthly budget coming at 30135.  I just entered 3 proposals.  Feel free to enter some more and vote up-down so we can test watchman.

I entered 3 proposals (no one entered any others I see) and the two totaling 3.8 MM were paid (getblock 30135 to see them), that is correct as the other one was over budget.

So watchman succeeded, but I do see a bug in the proposal UI.  It still shows the 3 old proposals that are paid.  Ill work on analyzing this. 

I entered 3 proposals (no one entered any others I see) and the two totaling 3.8 MM were paid (getblock 30135 to see them), that is correct as the other one was over budget.

So watchman succeeded, but I do see a bug in the proposal UI.  It still shows the 3 old proposals that are paid.  Ill work on analyzing this.

I found the bug, this will be fixed in the next release.

So far, it appears QT is working correctly.

I will be enabling ABN soon and we can test that next. 

So far, it appears QT is working correctly.

I will be enabling ABN soon and we can test that next.

ALL:

I just enabled the enforcement of ABN weight.  We currently require 1000 abn weight.

Lets keep an eye on the difficulty and ensure everything rolls forward properly.

My windows testnet node is still giving me trouble,  refuses to find any peers.

Side-note:  I got a bit frustrated and deleted the wallet.dat along with all other info .. so no more coins lol

Also,  I noticed the "testnet" client creates/uses the SAN directory in the main client's folder, not the testnet3 folder.

The error message for all peers is: using obsolete version 209 after DIP3 activation; disconnecting


Erm... nevermined

Didn't realize the download link had changed, so i was stuck on .0.6

fixing now

Was this a test? lol

I forgot to ask, do you need any tBBP?

Rob,
I think, that would be nice to have these stats (from production) in tx details:

Code: [Select]

Height: XXX
Difficulty: XXX
Time: XXX
Subsidy: XXXNow its really hard to count block height when the tx has been done.
Maybe block height would be enough.

Rob,
I think, that would be nice to have these stats (from production) in tx details:

Code: [Select]

Height: XXX
Difficulty: XXX
Time: XXX
Subsidy: XXXNow its really hard to count block height when the tx has been done.
Maybe block height would be enough.

Good idea, I will add them (added to list).


Also I was just reading about the procedure to upgrade a Sanc to a deterministic sanc, and although on the positive side, its just a single page of commands that can be done from the home wallet itself, if someone owns a lot of sancs, they might miss out  on a major family event like birth of new child, etc.  In light of that I was thinking it might be useful for us to add an upgrade command.  I believe we can potentially access what we need by scanning down to the existing entry in the masternode.conf, then generating the new info, signing it and sending it.  One last step we can not do is move the 'masternodeblsprivkey=' to the hosted sanc, but we can emit that in the output of the upgradesanc command.  I think Ill work on this command before we move to dip3.      https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html

Something like 'upgradesanc existing_sanc_name' would be nice.  Then it outputs: masternodeblsprivkey=nnnnnn.

So, I did add the legacy double click info to our txlist, and over the last day, I added a new command to allow us to upgrade a sanc to deterministic.

Let me iterate through the punchlist, and verify some other small things we might need for our next round of testing, and then ill create a new release for testnet.

BTW, our ABN feature worked about 95%, but I did discover a bug in it so only 1 of its 2 features are enabled, will fix this as part of this next release also.

Progress is now speeding up, and everything looks very solid.  I feel bullish about the next version of BiblePay.

The new version is almost ready, but I see the 4.5MM lockup poll is most likely winning.

I believe this is a good time for us to include the higher collateral in the next release (since we need a mandatory change anyway for the ABN rule).

We will need to re-create our sancs @ 4.5 MM.

Stay tuned...

I'm starting to add some documentation to explain to new users how to get started:

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



I realize we need a specific section for Grandma also - I'll continue to refine the getting started guide.

Please let me know if anyone would like to see more expanded info on any of these, and/or if this is sufficient to call us "easy to use" with the release of Evo.

1.4.1.7 - Mandatory Upgrade for TestNet

- Fix bug showing old proposals in Proposals List page
- Change sanctuary lockup collateral to 4,500,001
- Upgrade persisted data storage system from v1.0 to v1.1
- Add txlist double click drill in: display of biblepay-classic fields:
height, time, difficulty
- Add RPC leaderboard command (leaderboard me=true/false [height ||
last || future]
- Add exec upgradesanc sancname.  This is a BiblePay utility that allows
you to upgrade a non-deterministic sanc to a deterministic sanc.  We
also add the deterministic.conf file, so the user can write scripts to
read their own deterministic sanc keys and automate the deployment of
the keys to the remote server(s).
- Fix low-abn-weight bug
- Make exec join healing display the wiki URL so the user can learn
about the healing campaign first


Note:  We just changed our sanctuary lockup collateral to 4,500,001.  Please re-create your sancs.

We will talk about Deterministic a little later, for now please re-create the standard way - but note: It is recommended that we re-create Cold sancs, as the upgrade to dip3 will require cold sancs.  (Hot sancs cannot be upgraded to dip3).