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

Started by Rob Andrews, March 24, 2019, 01:17:09 PM

Previous topic - Next topic

togoshigekata

Quote from: Rob Andrews on April 22, 2019, 11:21:55 AM
After resyncing my sancs and starting them I see this hash:

getblockhash 40668
9c1b6d67d8737b9976eed162b8edce7018430a9f2d16cfd97e4c83b14943baf6

Anyone agree with mine?

I agree with that hash on my daemon and now Im on block 42305

./biblepay-cli getblockhash 42305
ad4e735a7db8aacd92dfd7e50775d35e528c441bb95fd440fb9a7956aa056619


Could I have some tBBP please? Thanks!
yUEdCwzLCm58oXksh42R3eBroTrU9MN3hX

Rob Andrews

Quote from: togoshigekata on April 22, 2019, 07:53:24 PM
Just documenting my adventure, Im compiling on Ubuntu
https://github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt

Line 16 after cloning the repo I needed to cd into it
cd biblepay-evolution

Line 23 I ran into issue trying to run make command

I ran:
uname -a
to confirm my architecture

For this command:
./configure --prefix {pwd}/depends/x86_64-pc-linux-gnu

I had to use:
./configure --prefix `pwd`/depends/x86_64-pc-linux-gnu

Nabbed it from here:
https://github.com/dashpay/dash/blob/master/doc/build-generic.md

I dont know anything about bash
https://ss64.com/bash/syntax-expand.html
https://unix.stackexchange.com/questions/98391/what-is-the-difference-between-echo-date-echo-date-and-echo-date

I also used the swap file commands since Im on 1GB:
free #check if swap is 0
dd if=/dev/zero of=/var/swap.img bs=1024k count=1000
mkswap /var/swap.img
swapon /var/swap.img
free #check if swap is 1024


Ill let you guys know when Im synced up and ready for some tBBP :)

Thanks -

1) I added the swap file commands to the BuildBiblePay.txt file at the beginning as Optional.

2) I see what you mean about {pwd}.  I believe I didnt run into that problem is I typed out the path.  I have changed it to `pwd` in the docs.

3) Our build-generic.md is in the repo also, but I realize it can't be found without navigating around github as its probably not searchable on google yet.

4) Glad you got through the depends hurdle, that is the main hurdle to upgrade to Evo.

5) Ill send some tBBP, but I see we have 20 new nodes online, so we are all at different heights. 

Rob Andrews

Quote from: vuli on April 23, 2019, 01:16:06 AM
well I resynced and my last block is 34929

I see a similar problem, my 3 sancs reorged back to 34929 when these 20 new nodes came online.

Let me explain to everyone one conundrum (this affects Dash also).  The sancs must be online in order for our daily superblock consensus to work, and for masternode payments to work (as their vote heights must be exact and correct), and the sancs go out of sync when the supermajority of the miners reorganize (meaning they need Re-Enabled manually).  While they are not enabled, the entire network is really just free-riding.  Its that chicken and egg issue I explained earlier.

Once the sancs are enabled while they are at a similar height as the supermajority things should clear up.

Right now all sancs are out of sync and disabled.


Rob Andrews

I'm seeing this hash:

09:12:55

getblockhash 42424


09:12:55

5bf45962948b72ca0d74a9cc353aa89d7765c702741954718809623656bb09a8



If your node does not agree, please try this additional step, in addition to deleting the normal 6 folders and files (evodb, chainstate, blocks, mnp*, mnc*, gov*) also delete : /SAN/*.*

Then restart.


jaapgvk

Quote from: Rob Andrews on April 23, 2019, 09:14:19 AM
I'm seeing this hash:

09:12:55

getblockhash 42424


09:12:55

5bf45962948b72ca0d74a9cc353aa89d7765c702741954718809623656bb09a8



If your node does not agree, please try this additional step, in addition to deleting the normal 6 folders and files (evodb, chainstate, blocks, mnp*, mnc*, gov*) also delete : /SAN/*.*

Then restart.

I've been trying to catch up with you guys for more than a week now :P Every time I finally had my nodes up and running, you guys already jumped to the next version :p

Anyway, I have two nodes that are also stuck in the 35*** range. Will try to delete these files and see what happens.

jaapgvk

Quote from: jaapgvk on April 23, 2019, 10:29:23 AM
I've been trying to catch up with you guys for more than a week now :P Every time I finally had my nodes up and running, you guys already jumped to the next version :p

Anyway, I have two nodes that are also stuck in the 35*** range. Will try to delete these files and see what happens.

Deleting those files helped :) I'm synced to the chain with the same hash for block 42424:
5bf45962948b72ca0d74a9cc353aa89d7765c702741954718809623656bb09a8

Next step will be to try and set up some sanctuaries I guess :)

Rob Andrews

Quote from: jaapgvk on April 23, 2019, 02:43:04 PM
Deleting those files helped :) I'm synced to the chain with the same hash for block 42424:
5bf45962948b72ca0d74a9cc353aa89d7765c702741954718809623656bb09a8

Next step will be to try and set up some sanctuaries I guess :)

Great!
Remember they are now 4,500,001 and they must be cold sancs now (so we can all upgrade to dip3 sancs later).

Let me know if you need tBBP.


Rob Andrews

I found a bug today that requires us to upgrade to 1.4.2.0.

Please know that the upgrade is coming in about an hour.


Rob Andrews

#248
1.4.2.0-Mandatory Upgrade for TestNet

- Fix bug not allowing QT to properly start
- Add -erasechain parameter (this allows you to erase the chain during
boot)
- Add Togos suggestions to the BuildBiblePay.txt docs file

** Note: The link has changed in the OP post due to rolling over to a new major version **

Rob Andrews

One thing that might make it easier to sync in future upgrades:  set gen=0 in the config file, upgrade, then after confirming you are synced then manually turn on generate.

I found its so easy to solve a block in testnet this will easily put you on your own chain.


togoshigekata

Upgraded to v1.4.2

I confirm same hash for 42424

./biblepay-cli getblockhash 42424
5bf45962948b72ca0d74a9cc353aa89d7765c702741954718809623656bb09a8


Im currently at:

./biblepay-cli getblockhash 43157
ffa38ab5eaf5b7516ed1891c78aedf428160fc1cc9493420927c6f7f7808fa62

Rob Andrews

Quote from: togoshigekata on April 23, 2019, 06:21:18 PM
Upgraded to v1.4.2

I confirm same hash for 42424

./biblepay-cli getblockhash 42424
5bf45962948b72ca0d74a9cc353aa89d7765c702741954718809623656bb09a8


Im currently at:

./biblepay-cli getblockhash 43157
ffa38ab5eaf5b7516ed1891c78aedf428160fc1cc9493420927c6f7f7808fa62


Good, we match.  Hopefully you received the tBBP.


togoshigekata

Thanks Rob! I have about 7.9 million tBBP now, Ill set up a masternode soon

Rob Andrews

Is everyone mining, because I only see a .10 diff and 4 people in the leaderboard.

Anyone who is not in the leaderboard, you can join by adding your cpk then 'exec join pog'. 

I'm reluctant to turn on ABN until diff is about 1. 

QT is enabled, we are now at qt level 2.  It appears the new GSC contract version is working (this version contains the prices).


Rob Andrews

Good news, things look pretty good.  I did discover a bug causing a couple issues that get logged as ERROR, and also a couple necessary enhancements for the anti-fork feature, but these can wait a tad longer til we add at least one more thing from the punch list.  I see we have 10 participants in the GSC block now.