Bible Pay

TestNet => TestNet Discussion Archive => Topic started by: Rob Andrews on June 06, 2018, 09:45:32 pm

Title: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 06, 2018, 09:45:32 pm
The goal is to test our next mandatory release for quality and stability.

Testnet Instructions:

Git pull origin master to the latest version (1.1.2.6+).
From ~/.biblepaycore
Create a file called biblepaytest.conf
Add the following lines:
testnet=1
server=1
masternodeprivkey=xxx
masternode=0

Launch testnet like this:
cd ~/biblepay/src/qt
./biblepay-qt -conf=biblepaytest.conf

This setup lets you run testnet side by side your prod node or masternode, and allows you to avoid problems finding a separate testnet configuration file.

To set up a hot testnet sanctuary:

Ask a forum member for 500,000 bbp.
Launch the wallet.
Type:  masternode genkey
Copy the key to the 'masternodeprivkey=xxxx' in the biblepaytest.conf file.
Send 500,000 bbp to one of your own receiving addresses.

Restart the wallet.


Testing objectives:

- Ensure monthly (weekly in testnet) superblock is capable of paying a dispursement, ensure getgovernanceinfo is correct
- Ensure daily PODC superblock is also capable of dispursing, ensure exec getboincinfo podc budget is correct
 (The above two tests verify the cascading superblock bug will be mitigated)
- Ensure wallet boots without memorizing prayers on the primary thread, but yet in the background thread (this is the speedy bootup feature)
- Ensure active proposal list view is available (Bhavani)
- Ensure active proposal list vote works (Bhavani)
- Ensure active proposal list pie chart works (Bhavani)
- Test new PODC mature consensus feature (Rob will explain)
   (  // Mature means we stake a point in history (one timestamp per day) as Yesterdays point, and mature means it is older than that historical point.
      // This should theoretically allow the sancs to come to a more perfect consensus each day for PODC elements: DCCs (Distinct CPIDs), UTXOWeights (UTXO Stake Amounts), TaskWeights (Task confirmations), and Unbanked Indicators.)

      

- Test exec podcvotingreport (Rob)
- Check Slovakian User Interface Language (Orbis) to ensure the ?'s have dissapeared
- After F13000 Cutover Height, Block speed has been increased by 4.5% (aiming for 205 blocks per day)

Thank you for your continued support that ultimately helps orphans globally.



Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 07, 2018, 05:48:52 am
Awesome! Just to confirm, we will need to run QT (GUI) version of BiblePay for testing?

UPDATE: I jumped the gun, BiblePay v1.1.2.5+ is not on Github yet, so wait for it to be released first: https://github.com/biblepay/biblepay/commits/master

====

TOGO NOTES:
Im going the route of setting up Testnet on a brand new server

1. Create $5 Vultr Ubuntu 16.04 server
https://www.vultr.com/

2. Use Putty to connect to it and Install BiblePay
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/
(Note: Use Swap File to increase RAM before running "sudo make")

Code: [Select]
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

====

3. Install Lubuntu GUI and Reboot
https://www.vultr.com/docs/install-gui-environment-for-ubuntu

Code: [Select]
apt-get update
apt-get install -y lubuntu-core
reboot

4. On Vultr Server Information page click "View Console" button in top right

5. Press Ctrl - Alt + T to open a Terminal

====

**IN PROGRESS**

6. Old Notes on Setting up Hot Testnet Sanctuary
http://forum.biblepay.org/index.php?topic=108.msg1444#msg1444
NOTE: Tesnet uses port 40001 (Prod uses port 40000)

6a. Set BiblePay Wallet to Testnet

Code: [Select]
cd ~/.biblepaycore
vi biblepay.conf
i
testnet=1
:wq

6b. Run BiblePay Daemon to Sync with Testnet Chain

Code: [Select]
cd ../..
cd home/biblepay/src
./biblepayd -daemon
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 08, 2018, 09:58:46 am
Togo, thanks a lot for the guides.

I just wanted to mention, I was shooting for making this a little easier on everyone who already has a running Prod sanctuary: To possibly save you some money and just run the testnet instance in the same VMS.

I tweaked the OP post with a hint that allows you to run the testnet instance side by side on your prod sanc.
But whatever is easier for all of you by all means.

The need for at least 5 hot sancs in testnet is primarily because we need to test the ability for the wallet to emit both a daily and weekly superblock and verify the chain does not throw any errors, and of course that requires the hot sancs to actually vote.

I'm debugging 1.1.2.5 now, will keep you all posted.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 11, 2018, 10:18:18 am
I'll put up a sanc when you're ready.. will need the funds to start it (testnet)

Thanks!  I'm compiling a windows version now.

It shouldnt be much longer.  I think tonight at the latest, we will be ready for testnet.

Sorry for the delays everyone.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: MIP on June 12, 2018, 03:09:02 am
So do we need 1.1.2.5 on both Sanc and windows controller wallet or just in Sanc?

Edit: ok I read again and it's about testing on a hot wallet Sanc.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 12, 2018, 08:09:48 am
So do we need 1.1.2.5 on both Sanc and windows controller wallet or just in Sanc?

Edit: ok I read again and it's about testing on a hot wallet Sanc.

You really just need a hot sanctuary running in testnet - if you dont mind voting from a QT hot sanc.  But if you do have a controller testnet QT wallet then it will make testing Bhavanis prod proposals the same as prod. 

In my case Im installing 3 QT testnet hot sancs, running in qt mode, side by side my prod sancs, and Im going to try voting from each hot sanc qt console. 

Note, there was a problem with last nights build, we now need 1.1.2.6.  Im recompiling 1.1.2.6 now (I updated the OP).

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 12, 2018, 01:16:43 pm
Alright 1.1.2.6 has been deployed for win + linux.

Testnet is ready to test.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 12, 2018, 02:28:33 pm
Good deal,  will grab it and get setup tonight, any concerns mixing this client with the current live/production?

Would it help if I setup a few mn's? 

I'll run a small mining instance as well,  PODC mapping is the same as production?

As far as mixing prod & testnet, no concerns, otherwise I wouldnt have released it.  Testnet starts with a different switch (see OP post).

Yes, setting up a couple MNs will help.  Im going to shoot for 3.  As long as we get the supermajority to vote like prod, we can then address the test cases.

Yes, PODC is the same in testnet, but you do have to associate your CPID with your wallet in testnet (like prod) otherwise exec getboincinfo wont show anything :).

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 13, 2018, 07:53:30 am
Alright, I'm up and running with two wallets.

I have one Sanctuary set-up:

Code: [Select]
14:47:41

masternode status


14:47:41

{
  "vin": "CTxIn(COutPoint(69dfd77724f5b369e19c42fdb9ef5d9416034ac6588da07dfd53db1ae21bfaa4, 1), scriptSig=)",
  "payee": "yYri6dXZEXtN5j6UhTduL1GSEHSDCW1Pif",
  "status": "Masternode successfully started"
}

Code: [Select]
14:52:02

getblockhash 26985


14:52:02

6e3be0e89df723d9bfe9ba9c64404e7643c3baaf667c315f8cc720f77949db57

I will set up the other Sanctuary when I have enough BBP (shouldn't take long).

I don't have any CPID associated with these wallets. Will that be necessary for testnet? 
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 13, 2018, 11:19:20 am
to test the PODC payments we need some folks setup and staking


I have one MN up and running will get another  going later today.

Okay, I'm going to set that up too :)

When I try to associate my CPID's I get a 'already in chain' message. Is this because this is still the old testnet? If so, I'll re-associate. I presume it's no problem to have the same CPID on both testnet and prod, right?
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 13, 2018, 05:07:17 pm
When I fired test back up it had a few months of history, so yeah most likely a continuation of the old testnet, and per Rob above no conflict having the same CPID in test and prod

2nd sanc up and running.. seems there are a lot of older version sanctuaries left alive for some reason..  curious

Thanks!

Yeah, I noticed a bunch of old-protocol-sanctuaries too...

I've associated my CPID again. Setting up my second Sanctuary right now.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 13, 2018, 05:09:39 pm
updated to v1.1.2.6,, cleaned .dat files, reindexed, 0 connections hmmm, any nodes (IP addresses) I should add?
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 13, 2018, 05:46:23 pm
updated to v1.1.2.6,, cleaned .dat files, reindexed, 0 connections hmmm, any nodes (IP addresses) I should add?

You can try these ones:
144.202.88.12
173.165.51.177
73.247.191.58
84.29.208.33
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 13, 2018, 11:06:24 pm
updated to v1.1.2.6,, cleaned .dat files, reindexed, 0 connections hmmm, any nodes (IP addresses) I should add?
Sorry, due to the race condition issue today, I had the testnet seed node down (the one compiled in the wallet).

I just brought up 1.1.2.7 lets see if we sync now.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 14, 2018, 04:00:01 am
Ok cool!, Updated to 1.1.2.7, cleaned .dat files, reindexed, Im synced now!

./biblepay-cli getblockhash 27834
046ad9e9c7070cbb8a1ebbc68ecef0f3ef3dfc1592663dc5570685085963dd49

===

Could anyone send me tBBP so I can setup a sanctuary? Thanks!
My Testnet tBBP Address: yZyLCtmNkDZmJrCD24MLpuAF2oqZ91hQB9
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 14, 2018, 07:35:37 am
Ok cool!, Updated to 1.1.2.7, cleaned .dat files, reindexed, Im synced now!

./biblepay-cli getblockhash 27834
046ad9e9c7070cbb8a1ebbc68ecef0f3ef3dfc1592663dc5570685085963dd49

===

Could anyone send me tBBP so I can setup a sanctuary? Thanks!
My Testnet tBBP Address: yZyLCtmNkDZmJrCD24MLpuAF2oqZ91hQB9

Looks like we match hashes!  Sent 1.25MM.

Btw, please test any of the bullet points- the names above were either to give credit to who programmed it or who knew the most about the feature.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 14, 2018, 07:37:18 am
So on the proposals, in order to see the testnet proposals in the pool, you have to click account - testnet first.

I created one proposal in testnet.  So far it has 0 votes.

If you go into the qt wallet, and click Proposals you should see the proposal.

The chart is blank until it has some votes.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 14, 2018, 12:27:40 pm
Okay, I've been trying a few things.

- If I vote 'no' from the wallet, the 'No ct' goes to 1 as expected, but the 'Yes ct' goes to -1, so it seems that the categories 'AbsoluteYesCount' and 'YesCount' and intermingled in some way?

-Voting 'yes' and 'abstain' doesn't seem to work from my wallet (works from 'tools window' but not from the 'proposal list window').
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 14, 2018, 02:26:55 pm
v1.1.2.7 - My Setup: auto mining 1 thread, no CPID, sanctuary setup/started

BiblePay daemon was running, this was written to command line three times:

Code: [Select]
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
biblepay in ProcessMessages()

and then this was written to command line:

Code: [Select]
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

and the daemon exited/crashed.
This is tail of debug.log:

Code: [Select]
2018-06-14 13:40:41
ProcessBlockFound::Generated 564.74545019
2018-06-14 13:40:41  DCC hash 0000000000000000000000000000000000000000000000000000000000000000  Age 14.000000
 Chosen Sanctuary - pulling down the DCC file... Aggregator 0.000000, Percentile 0.000000
2018-06-14 13:40:41 Downloading DC File NAME /root/.biblepaycore/SAN/user1.gz FROM URL https://boinc.bakerlab.org DCC download finished
2018-06-14 13:40:50 Gunzip /root/.biblepaycore/SAN/user1.gzDownloading DC File NAME /root/.biblepaycore/SAN/user2.gz FROM URL https:// Filter File 28126MemorizeBlockChainPrayers @ 1528983651 Finished MemorizeBlockChainPrayers @ 1528983652  Unbanked

====

Restarted daemon, let it run awhile, similar thing happened again, bad_alloc written to command line 3 times, here is last 50 lines of debug.log:

Code: [Select]
~/.biblepaycore/testnet3# tail -50 debug.log
2018-06-14 13:47:47 MemorizeBlockChainPrayers @ 1528984067 Finished MemorizeBlockChainPrayers @ 1528984067 UpdateTip: new best=2feddcd2a52ff201c0a49258dba1bf97edc11e0fc7889b3bdc60857d18de4b8c  height=28039  log2_work=42.741379  tx=28610  date=2018-06-14 13:44:06 progress=0.052292  cache=0.0MiB(12tx)
2018-06-14 13:47:47 ProcessNewBlock : ACCEPTED
2018-06-14 13:47:47 MemorizeBlockChainPrayers @ 1528984067 Finished MemorizeBlockChainPrayers @ 1528984067 UpdateTip: new best=c3b65f2252e400bd4655433f7a7e2a85626a001d7ebd2454db6cf0bbf89c784c  height=28040  log2_work=42.741424  tx=28611  date=2018-06-14 13:44:13 progress=0.052294  cache=0.0MiB(13tx)
2018-06-14 13:47:47 ProcessNewBlock : ACCEPTED
2018-06-14 13:47:47 MemorizeBlockChainPrayers @ 1528984067 Finished MemorizeBlockChainPrayers @ 1528984067 UpdateTip: new best=c0939fee490a8dee70a6f4b778c3dd233112ecae34797f16d1b61703dd239315  height=28041  log2_work=42.741476  tx=28612  date=2018-06-14 13:45:35 progress=0.052296  cache=0.0MiB(14tx)
2018-06-14 13:47:47 ProcessNewBlock : ACCEPTED
2018-06-14 13:47:47 MemorizeBlockChainPrayers @ 1528984067 Finished MemorizeBlockChainPrayers @ 1528984067 UpdateTip: new best=6d6a86be672de6bff384f878ebbfab80fb945477f73163d28658edcbed98e343  height=28042  log2_work=42.741568  tx=28613  date=2018-06-14 13:46:07 progress=0.052298  cache=0.0MiB(15tx)
2018-06-14 13:47:47 ProcessNewBlock : ACCEPTED
2018-06-14 13:47:47 keypool added key 1014, size=1001
2018-06-14 13:47:47 init message: Loading wallet... (101.30 %)
2018-06-14 13:47:47 Finished MemorizeBlockChainPrayers @ 1528984066 P2P peers available. Skipped DNS seeding.
2018-06-14 13:47:57 dnsseed thread exit
2018-06-14 13:48:07 CActiveMasternode::ManageStateRemote -- STARTED!
2018-06-14 13:52:50  DCC hash 0000000000000000000000000000000000000000000000000000000000000000  Age 728.000000
 Chosen Sanctuary - pulling down the DCC file... Aggregator 0.000000, Percentile 0.000000
2018-06-14 13:52:50 Downloading DC File NAME /root/.biblepaycore/SAN/user1.gz FROM URL https://boinc.bakerlab.org DCC download finished
2018-06-14 13:52:58 Gunzip /root/.biblepaycore/SAN/user1.gzDownloading DC File NAME /root/.biblepaycore/SAN/user2.gz FROM URL https:// Filter File 28126MemorizeBlockChainPrayers @ 1528984379 Finished MemorizeBlockChainPrayers @ 1528984380  Unbanked
2018-06-14 13:53:01

************************
EXCEPTION: St9bad_alloc
std::bad_alloc
biblepay in ProcessMessages()

2018-06-14 13:53:01  DCC hash 0000000000000000000000000000000000000000000000000000000000000000  Age 10.000000
 Chosen Sanctuary - pulling down the DCC file... Aggregator 0.000000, Percentile 0.000000
2018-06-14 13:53:01 Downloading DC File NAME /root/.biblepaycore/SAN/user1.gz FROM URL https://boinc.bakerlab.org DCC download finished
2018-06-14 13:53:10 Gunzip /root/.biblepaycore/SAN/user1.gzDownloading DC File NAME /root/.biblepaycore/SAN/user2.gz FROM URL https:// Filter File 28126MemorizeBlockChainPrayers @ 1528984392 Finished MemorizeBlockChainPrayers @ 1528984393  Unbanked
2018-06-14 13:53:14

************************
EXCEPTION: St9bad_alloc
std::bad_alloc
biblepay in ProcessMessages()

2018-06-14 13:53:25  DCC hash 0000000000000000000000000000000000000000000000000000000000000000  Age 23.000000
 Chosen Sanctuary - pulling down the DCC file... Aggregator 0.000000, Percentile 0.000000
2018-06-14 13:53:25 Downloading DC File NAME /root/.biblepaycore/SAN/user1.gz FROM URL https://boinc.bakerlab.org DCC download finished
2018-06-14 13:53:33 Gunzip /root/.biblepaycore/SAN/user1.gzDownloading DC File NAME /root/.biblepaycore/SAN/user2.gz FROM URL https:// Filter File 28126MemorizeBlockChainPrayers @ 1528984414 Finished MemorizeBlockChainPrayers @ 1528984415  Unbanked
2018-06-14 13:53:36 unbanked 04fba56d89a5eb38b1b82f8a6240132c unbanked 3c4dbf398e2a1062bd695366dad41f8a

************************
EXCEPTION: St9bad_alloc
std::bad_alloc
biblepay in ProcessMessages()

2018-06-14 13:54:13  DCC hash 0000000000000000000000000000000000000000000000000000000000000000  Age 47.000000
 Chosen Sanctuary - pulling down the DCC file... Aggregator 0.000000, Percentile 0.000000
2018-06-14 13:54:13 Downloading DC File NAME /root/.biblepaycore/SAN/user1.gz FROM URL https://boinc.bakerlab.org DCC download finished
2018-06-14 13:54:22 Gunzip /root/.biblepaycore/SAN/user1.gzDownloading DC File NAME /root/.biblepaycore/SAN/user2.gz FROM URL https:// Filter File 28126MemorizeBlockChainPrayers @ 1528984463 Finished MemorizeBlockChainPrayers @ 1528984464  Unbanked


Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 14, 2018, 05:02:20 pm
v1.1.2.7 - My Setup: auto mining 1 thread, no CPID, sanctuary setup/started

BiblePay daemon was running, this was written to command line three times:

Code: [Select]
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
biblepay in ProcessMessages()

and then this was written to command line:

Code: [Select]
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

and the daemon exited/crashed.
This is tail of debug.log:

Code: [Select]
2018-06-14 13:40:41
ProcessBlockFound::Generated 564.74545019
2018-06-14 13:40:41  DCC hash 0000000000000000000000000000000000000000000000000000000000000000  Age 14.000000
 Chosen Sanctuary - pulling down the DCC file... Aggregator 0.000000, Percentile 0.000000
2018-06-14 13:40:41 Downloading DC File NAME /root/.biblepaycore/SAN/user1.gz FROM URL https://boinc.bakerlab.org DCC download finished
2018-06-14 13:40:50 Gunzip /root/.biblepaycore/SAN/user1.gzDownloading DC File NAME /root/.biblepaycore/SAN/user2.gz FROM URL https:// Filter File 28126MemorizeBlockChainPrayers @ 1528983651 Finished MemorizeBlockChainPrayers @ 1528983652  Unbanked

====

Restarted daemon, let it run awhile, similar thing happened again, bad_alloc written to command line 3 times, here is last 50 lines of debug.log:

Code: [Select]
~/.biblepaycore/testnet3# tail -50 debug.log
2018-06-14 13:47:47 MemorizeBlockChainPrayers @ 1528984067 Finished MemorizeBlockChainPrayers @ 1528984067 UpdateTip: new best=2feddcd2a52ff201c0a49258dba1bf97edc11e0fc7889b3bdc60857d18de4b8c  height=28039  log2_work=42.741379  tx=28610  date=2018-06-14 13:44:06 progress=0.052292  cache=0.0MiB(12tx)
2018-06-14 13:47:47 ProcessNewBlock : ACCEPTED
2018-06-14 13:47:47 MemorizeBlockChainPrayers @ 1528984067 Finished MemorizeBlockChainPrayers @ 1528984067 UpdateTip: new best=c3b65f2252e400bd4655433f7a7e2a85626a001d7ebd2454db6cf0bbf89c784c  height=28040  log2_work=42.741424  tx=28611  date=2018-06-14 13:44:13 progress=0.052294  cache=0.0MiB(13tx)
2018-06-14 13:47:47 ProcessNewBlock : ACCEPTED
2018-06-14 13:47:47 MemorizeBlockChainPrayers @ 1528984067 Finished MemorizeBlockChainPrayers @ 1528984067 UpdateTip: new best=c0939fee490a8dee70a6f4b778c3dd233112ecae34797f16d1b61703dd239315  height=28041  log2_work=42.741476  tx=28612  date=2018-06-14 13:45:35 progress=0.052296  cache=0.0MiB(14tx)
2018-06-14 13:47:47 ProcessNewBlock : ACCEPTED
2018-06-14 13:47:47 MemorizeBlockChainPrayers @ 1528984067 Finished MemorizeBlockChainPrayers @ 1528984067 UpdateTip: new best=6d6a86be672de6bff384f878ebbfab80fb945477f73163d28658edcbed98e343  height=28042  log2_work=42.741568  tx=28613  date=2018-06-14 13:46:07 progress=0.052298  cache=0.0MiB(15tx)
2018-06-14 13:47:47 ProcessNewBlock : ACCEPTED
2018-06-14 13:47:47 keypool added key 1014, size=1001
2018-06-14 13:47:47 init message: Loading wallet... (101.30 %)
2018-06-14 13:47:47 Finished MemorizeBlockChainPrayers @ 1528984066 P2P peers available. Skipped DNS seeding.
2018-06-14 13:47:57 dnsseed thread exit
2018-06-14 13:48:07 CActiveMasternode::ManageStateRemote -- STARTED!
2018-06-14 13:52:50  DCC hash 0000000000000000000000000000000000000000000000000000000000000000  Age 728.000000
 Chosen Sanctuary - pulling down the DCC file... Aggregator 0.000000, Percentile 0.000000
2018-06-14 13:52:50 Downloading DC File NAME /root/.biblepaycore/SAN/user1.gz FROM URL https://boinc.bakerlab.org DCC download finished
2018-06-14 13:52:58 Gunzip /root/.biblepaycore/SAN/user1.gzDownloading DC File NAME /root/.biblepaycore/SAN/user2.gz FROM URL https:// Filter File 28126MemorizeBlockChainPrayers @ 1528984379 Finished MemorizeBlockChainPrayers @ 1528984380  Unbanked
2018-06-14 13:53:01

************************
EXCEPTION: St9bad_alloc
std::bad_alloc
biblepay in ProcessMessages()

2018-06-14 13:53:01  DCC hash 0000000000000000000000000000000000000000000000000000000000000000  Age 10.000000
 Chosen Sanctuary - pulling down the DCC file... Aggregator 0.000000, Percentile 0.000000
2018-06-14 13:53:01 Downloading DC File NAME /root/.biblepaycore/SAN/user1.gz FROM URL https://boinc.bakerlab.org DCC download finished
2018-06-14 13:53:10 Gunzip /root/.biblepaycore/SAN/user1.gzDownloading DC File NAME /root/.biblepaycore/SAN/user2.gz FROM URL https:// Filter File 28126MemorizeBlockChainPrayers @ 1528984392 Finished MemorizeBlockChainPrayers @ 1528984393  Unbanked
2018-06-14 13:53:14

************************
EXCEPTION: St9bad_alloc
std::bad_alloc
biblepay in ProcessMessages()

2018-06-14 13:53:25  DCC hash 0000000000000000000000000000000000000000000000000000000000000000  Age 23.000000
 Chosen Sanctuary - pulling down the DCC file... Aggregator 0.000000, Percentile 0.000000
2018-06-14 13:53:25 Downloading DC File NAME /root/.biblepaycore/SAN/user1.gz FROM URL https://boinc.bakerlab.org DCC download finished
2018-06-14 13:53:33 Gunzip /root/.biblepaycore/SAN/user1.gzDownloading DC File NAME /root/.biblepaycore/SAN/user2.gz FROM URL https:// Filter File 28126MemorizeBlockChainPrayers @ 1528984414 Finished MemorizeBlockChainPrayers @ 1528984415  Unbanked
2018-06-14 13:53:36 unbanked 04fba56d89a5eb38b1b82f8a6240132c unbanked 3c4dbf398e2a1062bd695366dad41f8a

************************
EXCEPTION: St9bad_alloc
std::bad_alloc
biblepay in ProcessMessages()

2018-06-14 13:54:13  DCC hash 0000000000000000000000000000000000000000000000000000000000000000  Age 47.000000
 Chosen Sanctuary - pulling down the DCC file... Aggrehed MemorizeBlockChainPrayers @ 1528984464  Unbanked


So I believe that st9bad_alloc is actually in every version not introduced in 1.1.2.7. 
I belive that is the point where we try to download the WCG missing file :).
I need to look into this issue.
As I see that error on all my sancs in the background :)  In prod, on 1.1.2.4.

EDIT:  We found the root issue last night, thanks MIP.  Releasing fix in 1.1.2.8 now.



Jaap, on your absolute yes count,  I need to reproduce this, I'll look into this also.....


EDIT: Fixed in 1.1.2.8
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 14, 2018, 05:18:26 pm
Okay, I've been trying a few things.

- If I vote 'no' from the wallet, the 'No ct' goes to 1 as expected, but the 'Yes ct' goes to -1, so it seems that the categories 'AbsoluteYesCount' and 'YesCount' and intermingled in some way?

-Voting 'yes' and 'abstain' doesn't seem to work from my wallet (works from 'tools window' but not from the 'proposal list window').

Looks like its counting the "absolute yes count" instead of the Yes Count in the first column.

Ill fix that and see if I can add AbsoluteYesCount in there also.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: orbis on June 14, 2018, 05:51:56 pm
Hi,
tested Slovak translation in 1127 WIN 64bit.
It looks OK, but there are still many untranslated words or sentences which weren't in locale file.
But it is without "?" problem :)

Wallet was loading faster (in comparision with normal version) without prayer memorizing
I'm without CPID in testnet, but it all works without problem.
I'm POW mining and all my tBBP are safe from previous version (but I almost forgot my testnet password) :D
Proposals looks good, but I haven't MN (I wasn't succesful with MN start) so I can't test it. But for me, voting was with failure message (so it looks that it is working). I see only 1 proposal and I wasn't able to see proposal list pie chart (it was blank window)

I have tested "news".
In editor it rewrittes letters (like when INS is off)
HTML code works good (etc. <b>)
Preview is not so good on my PC. Preview window after showing just "jump" to background, not foreground and it is not possible to get to foreground. After maximize this window (accidentaly doubleclick on window) it wasn't able to restore size back to window mode. Buttons min, max and close didn't works.
Publishing article was without problems. Costs me 500 tBBP.
TXid: d07a330faf6d0462bd59ca0d49a680f730bbaf0e7fab809ea22c0c12fb9f941f
Article name: Testing article
But I wasn't able to see it :) I don't know where, my TXid article is blank.
On second attempt, it costs 0 tBBP, but after accepting 0 tBBP fee, was the publishing rejected, so I wasn't able to publish next article.

So, thats all from my first contact with 1127 :D
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 14, 2018, 06:54:18 pm
Togo, I reproduced the crash in my vultr node, now running it in valgrind to see whats the problem.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 14, 2018, 08:50:13 pm
Awesome!

Should I mess with debug config variables and/or valgrind?

"debug=true, debugmaster=true, If that does not work you will have to run it in valigrind mode:
./valgrind biblepay-qt"
https://bitcointalk.org/index.php?topic=2388064.msg33239779#msg33239779

Valgrind
https://wiki.ubuntu.com/Valgrind
http://valgrind.org/
http://valgrind.org/docs/manual/quick-start.html
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 15, 2018, 03:43:18 am
If anyone wants some tBBP, this private key holds 1.000.001 tBBP:

cPqBQ7xEKMvkkxscUHb9xvCoo4RbE633si8Uiv5WrqPFPb8c1VNR
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 15, 2018, 09:41:13 am
Awesome!

Should I mess with debug config variables and/or valgrind?

"debug=true, debugmaster=true, If that does not work you will have to run it in valigrind mode:
./valgrind biblepay-qt"
https://bitcointalk.org/index.php?topic=2388064.msg33239779#msg33239779

Valgrind
https://wiki.ubuntu.com/Valgrind
http://valgrind.org/
http://valgrind.org/docs/manual/quick-start.html


On valgrind it would be better if you put all the config variables in biblepaytest.conf like this:
testnet=1
debugmaster=true
...

Then launch it like this:

valgrind ./biblepay-qt -conf=biblepaytest.conf

Then it is clean and simple and config is in same dir as prod dir... But In This Case, the valgrind output is more complex than normal, and last night MIP and I happened to pull the actual problem out of the log so I think we have enough to go on now, but thanks for learning even more about it.  Ive never had to run it with more than the default switches (the default valgrind switches) as its usually a segfault.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 15, 2018, 09:48:12 am
Hi,
tested Slovak translation in 1127 WIN 64bit.
It looks OK, but there are still many untranslated words or sentences which weren't in locale file.
But it is without "?" problem :)

Wallet was loading faster (in comparision with normal version) without prayer memorizing
I'm without CPID in testnet, but it all works without problem.
I'm POW mining and all my tBBP are safe from previous version (but I almost forgot my testnet password) :D
Proposals looks good, but I haven't MN (I wasn't succesful with MN start) so I can't test it. But for me, voting was with failure message (so it looks that it is working). I see only 1 proposal and I wasn't able to see proposal list pie chart (it was blank window)

I have tested "news".
In editor it rewrittes letters (like when INS is off)
HTML code works good (etc. <b>)
Preview is not so good on my PC. Preview window after showing just "jump" to background, not foreground and it is not possible to get to foreground. After maximize this window (accidentaly doubleclick on window) it wasn't able to restore size back to window mode. Buttons min, max and close didn't works.
Publishing article was without problems. Costs me 500 tBBP.
TXid: d07a330faf6d0462bd59ca0d49a680f730bbaf0e7fab809ea22c0c12fb9f941f
Article name: Testing article
But I wasn't able to see it :) I don't know where, my TXid article is blank.
On second attempt, it costs 0 tBBP, but after accepting 0 tBBP fee, was the publishing rejected, so I wasn't able to publish next article.

So, thats all from my first contact with 1127 :D

On the Slovak translation, great!  The missing non translated phrases are actually a different issue unrelated to Slovak translation.  Those need translate commands around the code in the core.  If you want to put a github in for it please do.

On the News, 616 made some good points about why we should not pursue it.  Its just complicating the wallet.  Besides we dont have a place to host the pictures on the web in a decentralized way.  So I will look into disabling it for now.  Maybe Ill leave the code in so we can adapt it to a biblepay in-wallet help guide in the future.

Im fixing the crash and the pie chart and vote count now.


Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 15, 2018, 10:06:45 am
I put a second proposal in the pool in testnet (wait 1 hr for it to propagate), then we can vote yes on it (as the other one seems like it will be a loser).

Then we can check out the pie chart.


Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 15, 2018, 10:07:44 am
I just upgraded to .7,  i'm watching to see if PODC updates are sent.  .6 was mining ok but no podc update for the last few days.

Feature request:  transaction list, add PODC payment and PODC updates as filter options.

I saw the voting issue,  voting worked from the ui just the display is incorrect.

On the feature request, do you mean In the existing transaction list, add a filter to only see PODC related items?  Btw, on a side note, and this is just a hack, but you can currently filter by podc payments once you label your PODC receive address - you can type that label into the label field.  So that one works.  For podc Updates, you can type in '.01' for the amount, and sort descending, but again that is a real hack.

For PODC updates you can type 'exec utxoreport cpid' and see the updates from the rpc.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 15, 2018, 10:29:21 am
Ok, 1.1.2.8 is out in github which fixes the crash, the Yes count, and the pie chart.

Compiling windows now....


Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 15, 2018, 03:06:18 pm
Updated to v1.1.2.8, got a bad_alloc crash,
wiped all the .dat files and folders, reindexed, got a bad_alloc crash

Ive been using console version of BiblePay, so I just tried QT version, and I got:

Code: [Select]
Segmentation fault (core dumped)
re-ran QT again, and got:

Code: [Select]
************************
EXCEPTION: St11logic_error
basic_string::_M_construct null not valid
biblepay in ProcessMessages()

terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted (core dumped)
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 15, 2018, 03:08:08 pm
Updated to v1.1.2.8, got a bad_alloc crash,
wiped all the .dat files and folders, reindexed, got a bad_alloc crash

Ive been using console version of BiblePay, so I just tried QT version, and I got:

Code: [Select]
Segmentation fault (core dumped)
re-ran QT again, and got:

Code: [Select]
************************
EXCEPTION: St11logic_error
basic_string::_M_construct null not valid
biblepay in ProcessMessages()

terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted (core dumped)

Could you please try it in valgrind mode?

Ill take a look...


EDIT:  Im running it in valgrind now...


Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 15, 2018, 06:29:17 pm
Ok all, we didn't really fix the general protection fault in 1.1.2.8 or 1.1.2.9, but the good news is I found the root cause to be old testnet CPIDs whom do not have the unbanked indicator, causes the GPF error in the new version, in testnet only, hence the reason this didnt affect prod.

I'm compiling 1.1.3.0 now - will notify when ready....
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 15, 2018, 09:54:18 pm
Ok all, we didn't really fix the general protection fault in 1.1.2.8 or 1.1.2.9, but the good news is I found the root cause to be old testnet CPIDs whom do not have the unbanked indicator, causes the GPF error in the new version, in testnet only, hence the reason this didnt affect prod.

I'm compiling 1.1.3.0 now - will notify when ready....

1.1.3.0 is ready for testing!

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 15, 2018, 09:55:45 pm
Someone is voting against the 'groundbreaking proposal'.  Why dont we vote For it so we can test the pie chart?

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 15, 2018, 11:32:28 pm
Updated to v1.1.3.0, running for 2 hours console, no crashes,
(usually was crashing within first minute or two previously), now running in QT mode

===

Proposals >>> Proposal List

I right clicked >>> "Vote For" >>> Yes >>> Ok
on both proposals, but no values changed,
closed and reopened proposal list, values were the same,
basically my votes arent showing up, which makes me think maybe my Sanctuary isnt Enabled

but Sanctuaries tab shows my masternode as ENABLED, "masternode status" shows it as running successfully, watchman is set to testnet, crontab is setup, "cd ~/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py" runs successfully with no output

Does my Sanctuary show as Enabled?
Payee: yaoWiP*****yqZUUo

===

EDIT: 3 hours QT, no crashes

Thank you Rob!  8)
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 16, 2018, 02:30:26 am
Someone is voting against the 'groundbreaking proposal'.  Why dont we vote For it so we can test the pie chart?

I voted 'for' in QT but my vote got added to the 'no ct'  :-\
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 16, 2018, 09:29:12 am
I voted 'for' in QT but my vote got added to the 'no ct'  :-\


Oh my :), LOL, I think we fixed the wrong thing in voting.  Ok, I do confirm that we are sending the wrong signal.

Alright fixed.  So I just pushed out 1.1.3.1 to fix the voting, windows is compiling now.

10-4 Togo on the crash, thats at least 70% of the weight of the camel off our back now in testnet!

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 16, 2018, 11:32:51 am
Updated to v1.1.3.0, running for 2 hours console, no crashes,
(usually was crashing within first minute or two previously), now running in QT mode

===

Proposals >>> Proposal List

I right clicked >>> "Vote For" >>> Yes >>> Ok
on both proposals, but no values changed,
closed and reopened proposal list, values were the same,
basically my votes arent showing up, which makes me think maybe my Sanctuary isnt Enabled

but Sanctuaries tab shows my masternode as ENABLED, "masternode status" shows it as running successfully, watchman is set to testnet, crontab is setup, "cd ~/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py" runs successfully with no output

Does my Sanctuary show as Enabled?
Payee: yaoWiP*****yqZUUo

===

EDIT: 3 hours QT, no crashes

Thank you Rob!  8)

Hi Togo, once we get 1.1.3.1 up, try this:
gobject list all proposals
gobject vote-many gobjectid funding yes

See if there is a different outcome when voting from RPC, and that will let us isolate the proposal code from the standard voting code.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 16, 2018, 02:48:16 pm
1.1.3.1 has been released. 

Now we should have no crashes and be able to vote properly and see the pie chart.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 16, 2018, 03:06:49 pm
Updated to v1.1.3.1

Voted with Proposal List, vote didnt change, but if I opened a new Proposal List, the change is there!,
Voting For, Against and Abstain all worked, but only reflected in new Proposal List windows.
Viewing the pie charts and proposal links worked.

Note: I had to install a web browser to use View Proposal, I installed Firefox
sudo apt-get install firefox
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 16, 2018, 03:31:52 pm
Updated to v1.1.3.1

Voted with Proposal List, vote didnt change, but if I opened a new Proposal List, the change is there!,
Voting For, Against and Abstain all worked, but only reflected in new Proposal List windows.
Viewing the pie charts and proposal links worked.

Note: I had to install a web browser to use View Proposal, I installed Firefox
sudo apt-get install firefox

Same here. Everything seems to work now, you just have to close the 'proposal list' window and open it again to see the changes. Perhaps some kind of 'refresh' button would be helpful, or an auto-refresh after voting?
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 16, 2018, 04:07:19 pm
Updated to v1.1.3.1

Voted with Proposal List, vote didnt change, but if I opened a new Proposal List, the change is there!,
Voting For, Against and Abstain all worked, but only reflected in new Proposal List windows.
Viewing the pie charts and proposal links worked.

Note: I had to install a web browser to use View Proposal, I installed Firefox
sudo apt-get install firefox

So I just reproduced the error you had yesterday with failed to vote via proposal list (gobject mngovernance error).

In my case, I had created a hot masternode, put masternode=1 and masternodeprivkey=xxx in the biblepaytest.conf, then I couldnt vote because there was no masternode.conf for it to iterate through during voting (vote-many).
So I entered the outpoint and the genkey in masternode.conf, and I was able to vote unsuccessfully, and got the error you got.
Then I copied masternode.conf into \testnet3, and then I *was* able to vote successfully.

So I think this is OK for testnet, as this particular voting system iterates through registered masternodes in the masternode.conf.
It might be nice for us to add some options to allow it to vote Once (using the first masternode), or Vote Many...  But lets add that to the wish list for now as there are important things to do first (like form our DAO trust and make the pool list total charitable expenses) etc.

Glad you were able to vote!

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 16, 2018, 04:10:25 pm
Same here. Everything seems to work now, you just have to close the 'proposal list' window and open it again to see the changes. Perhaps some kind of 'refresh' button would be helpful, or an auto-refresh after voting?

Yes, I confirm it doesnt really refresh after it votes.  Ill take a look at that. 

Please, if anyone else has any very high priority wish list items for this release by all means please list them...



PS  I was able to vote successfully through the UI on my hot masternode.    Overall this is a real breakthrough, as I believe we are the first masternode coin with a Proposals UI in the wallet.  This is something Dash has to go to the dash-central to do, yet we can vote within the wallet!



Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 16, 2018, 07:14:31 pm
PS  I was able to vote successfully through the UI on my hot masternode.    Overall this is a real breakthrough, as I believe we are the first masternode coin with a Proposals UI in the wallet.  This is something Dash has to go to the dash-central to do, yet we can vote within the wallet!

This is really neat, good work Bhavani and Rob!

I believe PIVX has it on their roadmap for this year:
https://pivx.org/pivx-roadmap-2018/
"In Wallet Proposal Tab" and "In Wallet Voting Tab"

but I havent seen it released yet:
https://github.com/PIVX-Project/PIVX/releases

(Im curious to try out different coin wallets now)

I see this helping make voting easier! as well as spread awareness!

===

Feedback & Ideas:

- Move Proposals menu to a tab like Sanctuaries? (its more hidden as a menu item)

- Set Proposal List to be its own internal window vs a new spawned window?

- Add Scrolling and Dragging abilities to Proposal List or try way to Compact Info?
(my proposal list window goes off the screen on a small screen computer, a lot of information on the width)

=

Going Further:

- Add Visual Indicator or Sort/Separate Proposals based on if they are currently passing or not
Example: https://dashvotetracker.com/

- Integrate any BiblePay Pool and/or BiblePay Central Proposal/Governance Info/Charts
https://www.biblepay-central.org/en/proposals/
https://pool.biblepay.org/ >>> Governance >>> Proposal List

--- Add Superblock Budget Amount to UI
--- Add Next Superblock Block Number to UI
--- Add Estimated Superblock Date/Time to UI

--- Add Full Budget Bar Chart (Total Budget and Currently Passing Budget)

--- Add Multi Bar Chart Split by Budget sections/types
(I believe main BiblePay Pool only knows which budget section a proposal is set to?
In the future do we want to add Budget sections into the core code?)

--- Add ability to View Previous/Past Superblocks proposals/charts/info

=

- Add ability to Create Proposal with UI

=

- Pop Up / Notification when New Proposal submitted?
- Pop Up / Notification Reminder to Vote on Proposals X days before end of cycle?
- Pop Up / Notification when Superblock is mined?
- Pop Up / Notification when Masternode leaves ENABLED state?
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 17, 2018, 05:59:54 am
Updated to v1.1.3.1b 
"- Add ability for Proposal UI to refresh the list view after a vote occurs"
Tested and it works!
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 17, 2018, 08:48:37 am
This is really neat, good work Bhavani and Rob!

I believe PIVX has it on their roadmap for this year:
https://pivx.org/pivx-roadmap-2018/
"In Wallet Proposal Tab" and "In Wallet Voting Tab"

but I havent seen it released yet:
https://github.com/PIVX-Project/PIVX/releases

(Im curious to try out different coin wallets now)

I see this helping make voting easier! as well as spread awareness!

===

Feedback & Ideas:

- Move Proposals menu to a tab like Sanctuaries? (its more hidden as a menu item)

- Set Proposal List to be its own internal window vs a new spawned window?

- Add Scrolling and Dragging abilities to Proposal List or try way to Compact Info?
(my proposal list window goes off the screen on a small screen computer, a lot of information on the width)

=

Going Further:

- Add Visual Indicator or Sort/Separate Proposals based on if they are currently passing or not
Example: https://dashvotetracker.com/

- Integrate any BiblePay Pool and/or BiblePay Central Proposal/Governance Info/Charts
https://www.biblepay-central.org/en/proposals/
https://pool.biblepay.org/ >>> Governance >>> Proposal List

--- Add Superblock Budget Amount to UI
--- Add Next Superblock Block Number to UI
--- Add Estimated Superblock Date/Time to UI

--- Add Full Budget Bar Chart (Total Budget and Currently Passing Budget)

--- Add Multi Bar Chart Split by Budget sections/types
(I believe main BiblePay Pool only knows which budget section a proposal is set to?
In the future do we want to add Budget sections into the core code?)

--- Add ability to View Previous/Past Superblocks proposals/charts/info

=

- Add ability to Create Proposal with UI

=

- Pop Up / Notification when New Proposal submitted?
- Pop Up / Notification Reminder to Vote on Proposals X days before end of cycle?
- Pop Up / Notification when Superblock is mined?
- Pop Up / Notification when Masternode leaves ENABLED state?


Thanks Togo, these are all excellent suggestions.

Wow, I had no idea PIVX's roadmap had the Proposal UI!  This is interesting.  I find it invaluable looking at these other crypto roadmaps, maybe we should make a spreadsheet of all possible things.

Bhavani do you have an account here yet, maybe you can take something from this list you would enjoy?

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 17, 2018, 08:51:46 am
So I suppose we should test a boinc superblock and an actual proposal (for the weekly DAO budget payment process).

I just associated my CPID with my testnet vultr, and I sent a PODC update, so Im going to have to wait on that.
I see that in 'exec getboincinfo' no one has been paid yet, so this might be a good time guys to set up your boinc cpids and ensure podc updates have been sent. 

exec podc update
(Ensure a transaction went out), if it doesnt go out try 'exec podc update true' (this is to force it as we might not have the task sporks set up fully in testnet).

Ill take a look at creating a proposal for this weekly budget superblock.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 17, 2018, 09:16:07 am
So I suppose we should test a boinc superblock and an actual proposal (for the weekly DAO budget payment process).

I just associated my CPID with my testnet vultr, and I sent a PODC update, so Im going to have to wait on that.
I see that in 'exec getboincinfo' no one has been paid yet, so this might be a good time guys to set up your boinc cpids and ensure podc updates have been sent. 

exec podc update
(Ensure a transaction went out), if it doesnt go out try 'exec podc update true' (this is to force it as we might not have the task sporks set up fully in testnet).

Ill take a look at creating a proposal for this weekly budget superblock.

Yes, I was just about to post about this. I have two wallets with associated CPIDs which are sending out PODC updates, but I haven't received any payout yet. Also, I don't have any magnitude, and the UTXOWeight seems way too low.

Code: [Select]
16:12:16

exec getboincinfo


16:12:18

{
  "Command": "getboincinfo",
  "CPID": "d9b22fccfae5582d4ee7838883aaa3cf",
  "Address": "yYri6dXZEXtN5j6UhTduL1GSEHSDCW1Pif",
  "CPIDS": "d9b22fccfae5582d4ee7838883aaa3cf;",
  "CPID-Age (hours)": 424790,
  "NextSuperblockHeight": 31096,
  "NextSuperblockBudget": 1279917,
  "d9b22fccfae5582d4ee7838883aaa3cf_ADDRESS": "yYri6dXZEXtN5j6UhTduL1GSEHSDCW1Pif",
  "d9b22fccfae5582d4ee7838883aaa3cf_RAC": 3618.14,
  "d9b22fccfae5582d4ee7838883aaa3cf_TEAM": 15044,
  "d9b22fccfae5582d4ee7838883aaa3cf_WCGRAC": 0,
  "d9b22fccfae5582d4ee7838883aaa3cf_TaskWeight": 100,
  "d9b22fccfae5582d4ee7838883aaa3cf_UTXOWeight": 397,
  "Total_RAC": 3618.14,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 76218,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 147,
  "Superblock Hit Count (One Week)": 1,
  "Superblock List": "16533",
  "Last Superblock Height": 30997,
  "Last Superblock Budget": 1279917,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

Code: [Select]
16:14:50

exec getboincinfo


16:14:53

{
  "Command": "getboincinfo",
  "CPID": "8791a036b545f35e9ebd9333922738ac",
  "Address": "yfSRwqLaiKac2vNtXAaasuLyunCCzfCurW",
  "CPIDS": "8791a036b545f35e9ebd9333922738ac;",
  "CPID-Age (hours)": 424790,
  "NextSuperblockHeight": 31096,
  "NextSuperblockBudget": 1279917,
  "8791a036b545f35e9ebd9333922738ac_ADDRESS": "yfSRwqLaiKac2vNtXAaasuLyunCCzfCurW",
  "8791a036b545f35e9ebd9333922738ac_RAC": 160.88,
  "8791a036b545f35e9ebd9333922738ac_TEAM": 15044,
  "8791a036b545f35e9ebd9333922738ac_WCGRAC": 0,
  "8791a036b545f35e9ebd9333922738ac_TaskWeight": 100,
  "8791a036b545f35e9ebd9333922738ac_UTXOWeight": 17,
  "Total_RAC": 160.88,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 147,
  "Superblock Hit Count (One Week)": 1,
  "Superblock List": "16533",
  "Last Superblock Height": 30997,
  "Last Superblock Budget": 1279917,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

I have more than enough BBP to stake.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 17, 2018, 10:57:19 am
I tried to use my current Rosetta Account in the Distributed Computing tab, but it popped up "ALREADY_IN_CHAIN",
So I used a 2nd Rosetta account, forgot to join Team BiblePay, got error message in "exec getboincinfo"

Installed BOINC Manager, and attached project using Account Key

Now I am waiting to have positive RAC, so I just need 1 task completed

UPDATE: There wasnt enough RAM for the task, had to:

Code: [Select]
swapoff -a
and make swap file bigger:

Code: [Select]
dd if=/dev/zero of=/var/swap.img bs=1024k count=3000
mkswap /var/swap.img
swapon /var/swap.img
free

Ill check up on things in 4+ hours when I have some RAC :)

UPDATE: Task is taking 10 hours to complete, Im at 9 hours complete so far
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 17, 2018, 11:15:59 am
I tried to use my current Rosetta Account in the Distributed Computing tab, but it popped up "ALREADY_IN_CHAIN",
So I used a 2nd Rosetta account, forgot to join Team BiblePay, got error message in "exec getboincinfo"

Installed BOINC Manager, and attached project using Account Key

Now I am waiting to have positive RAC, so I just need 1 task completed

UPDATE: There wasnt enough RAM for the task, had to:

Code: [Select]
swapoff -a
and make swap file bigger:

Code: [Select]
dd if=/dev/zero of=/var/swap.img bs=1024k count=3000
mkswap /var/swap.img
swapon /var/swap.img
free

Ill check up on things in 4+ hours when I have some RAC :)

The reason you got "ALREADY_IN_CHAIN" is probably because we're still on the same testnet as when we started testing for PODC, so that CPID is still associated to an old/deleted wallet. You have to force a re-association to your new wallet. You probably know the command, the one with 'true' at the end. I forgot :P
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 17, 2018, 02:47:47 pm
The reason you got "ALREADY_IN_CHAIN" is probably because we're still on the same testnet as when we started testing for PODC, so that CPID is still associated to an old/deleted wallet. You have to force a re-association to your new wallet. You probably know the command, the one with 'true' at the end. I forgot :P

Yes, Togo, I had the same problem, cant find my old testnet node, so i did
exec associate user pass true
and I reassociated mine also...


Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 17, 2018, 07:45:29 pm
So I voted from a few sancs on the groundbreaking proposal, and barely got it up to a net Yes, so Im not sure if it will pass in this next budget.
Nevertheless if you look at getgovernanceinfo we have a superblock coming at 31570.
I created the budget item trigger and voted on it on my sancs, lets see if it pays or not. 

Also, I ran exec testvote on my sancs on the next daily superblock, and I see ONE cpid in the list, not sure who it is.  That is not for 100 more blocks so lets see what happens on these two things.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 17, 2018, 08:01:56 pm
v1.1.3.1b - $5 Vultr Ubuntu 16.04 cloud server - Hot Sanctuary /w BOINC

ok I finally got some RAC a few minutes ago,
I ran exec getboincinfo, saw that I have RAC, TaskWeight and UTXOWeight
I ran exec podcupdate

I changed my vote to Yes on Groundbreaking proposal
I ran exec testvote (what does it do?)

Current Block:  31,546
Monthly Super: 31,570
Daily PODC Super: 31,591
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 17, 2018, 10:15:19 pm
v1.1.3.1b - $5 Vultr Ubuntu 16.04 cloud server - Hot Sanctuary /w BOINC

ok I finally got some RAC a few minutes ago,
I ran exec getboincinfo, saw that I have RAC, TaskWeight and UTXOWeight
I ran exec podcupdate

I changed my vote to Yes on Groundbreaking proposal
I ran exec testvote (what does it do?)

Current Block:  31,546
Monthly Super: 31,570
Daily PODC Super: 31,591

Whose CPID is 8791*?  It looks like this cpid got 1.2 million reward!  So that part appears to be working.  I was the other CPID, I got 5500 bbp.

The weekly budget superblock worked.  I got 30,000 rewarded for the groundbreaking proposal.

So far so good.

PS:  Exec testvote only works on Sancs properly.  It goes through the motions of simulating a create contract (IE it gather the magnitude), then if its valid it also votes for that contract, then shows the results.  Its useful to know that all the various systems that go into a contract are working.


Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 17, 2018, 10:58:49 pm
My CPID is c9a2****

So I guess I will be in the next PODC superblock since I got RAC late

==

I checked Proposal List, I can still view the proposals and I can still change votes on them,
What should the behavior of the Proposal List be after Budget SuperBlock is mined?
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 17, 2018, 11:28:41 pm
My CPID is c9a2****

So I guess I will be in the next PODC superblock since I got RAC late

==

I checked Proposal List, I can still view the proposals and I can still change votes on them,
What should the behavior of the Proposal List be after Budget SuperBlock is mined?

In the QT wallet I guess you mean, yes I see I didn't give Bhavani any instructions on that, so the code doesn't remove paid items.  I never tried adjusting votes on a paid proposal (manually in the past).  I can see the 'very boring proposal' not being updated, but its counterintuitive that the paid proposal can still be changed, interesting.  I just tried and confirm I can adjust votes on both.

We do call out to get the 'active' proposals when we list these.  So it looks like what we need is the ability to filter those down to unpaid...

Ill take care of this tomorrow.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 17, 2018, 11:34:59 pm
Awesome! Thanks Rob!
Just let me know if theres anything else I can do :)
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 18, 2018, 02:44:43 am
Whose CPID is 8791*?  It looks like this cpid got 1.2 million reward!  So that part appears to be working.  I was the other CPID, I got 5500 bbp.

The weekly budget superblock worked.  I got 30,000 rewarded for the groundbreaking proposal.

So far so good.

PS:  Exec testvote only works on Sancs properly.  It goes through the motions of simulating a create contract (IE it gather the magnitude), then if its valid it also votes for that contract, then shows the results.  Its useful to know that all the various systems that go into a contract are working.

That's me! I'm rich! 8) But I still have the 'uxto-weight' bug. I don't stake nearly the amount I should stake:

Code: [Select]
09:31:43

getblockhash 31800


09:31:43

3dedbfc71a2fd1b7798cbcc7c3b6871bb088aa492ddb2ebb872933a1b0dfbf00


09:41:24

exec getboincinfo


09:41:26

{
  "Command": "getboincinfo",
  "CPID": "8791a036b545f35e9ebd9333922738ac",
  "Address": "yfSRwqLaiKac2vNtXAaasuLyunCCzfCurW",
  "CPIDS": "8791a036b545f35e9ebd9333922738ac;",
  "CPID-Age (hours)": 424807,
  "NextSuperblockHeight": 31888,
  "NextSuperblockBudget": 1279917,
  "8791a036b545f35e9ebd9333922738ac_ADDRESS": "yfSRwqLaiKac2vNtXAaasuLyunCCzfCurW",
  "8791a036b545f35e9ebd9333922738ac_RAC": 176.18,
  "8791a036b545f35e9ebd9333922738ac_TEAM": 15044,
  "8791a036b545f35e9ebd9333922738ac_WCGRAC": 0,
  "8791a036b545f35e9ebd9333922738ac_TaskWeight": 100,
  "8791a036b545f35e9ebd9333922738ac_UTXOWeight": 18,
  "Total_RAC": 176.18,
  "Total Payments (One Day)": 1279916,
  "Total Payments (One Week)": 1279916,
  "Total Budget (One Day)": 1279917,
  "Total Budget (One Week)": 1279917,
  "Superblock Count (One Week)": 155,
  "Superblock Hit Count (One Week)": 2,
  "Superblock List": "31591,16533",
  "Last Superblock Height": 31789,
  "Last Superblock Budget": 1279917,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 999.9992186993375,
  "Magnitude (One-Week)": 999.9992186993375
}

The other wallet seems to be on a fork btw. I'm going to fix it:

Code: [Select]
09:32:13

getblockhash 31800


09:32:13

0a65256e91201387cdb30a38e6afad83851b82f865ad88b43bfdb15a6758578a


09:44:02

exec getboincinfo


09:44:05

{
  "Command": "getboincinfo",
  "CPID": "d9b22fccfae5582d4ee7838883aaa3cf",
  "Address": "yYri6dXZEXtN5j6UhTduL1GSEHSDCW1Pif",
  "CPIDS": "d9b22fccfae5582d4ee7838883aaa3cf;",
  "CPID-Age (hours)": 424807,
  "NextSuperblockHeight": 31888,
  "NextSuperblockBudget": 1279917,
  "d9b22fccfae5582d4ee7838883aaa3cf_ADDRESS": "yYri6dXZEXtN5j6UhTduL1GSEHSDCW1Pif",
  "d9b22fccfae5582d4ee7838883aaa3cf_RAC": 3658.2,
  "d9b22fccfae5582d4ee7838883aaa3cf_TEAM": 15044,
  "d9b22fccfae5582d4ee7838883aaa3cf_WCGRAC": 0,
  "d9b22fccfae5582d4ee7838883aaa3cf_TaskWeight": 100,
  "d9b22fccfae5582d4ee7838883aaa3cf_UTXOWeight": 423,
  "Total_RAC": 3658.2,
  "Total Payments (One Day)": 5006,
  "Total Payments (One Week)": 81224,
  "Total Budget (One Day)": 1279917,
  "Total Budget (One Week)": 1279917,
  "Superblock Count (One Week)": 155,
  "Superblock Hit Count (One Week)": 2,
  "Superblock List": "31591,16533",
  "Last Superblock Height": 31789,
  "Last Superblock Budget": 1279917,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 3.911191116298947,
  "Magnitude (One-Week)": 63.46036500804349
}


09:32:43

getchaintips


09:34:37

[
  {
    "height": 31814,
    "hash": "29c602984eb82edbf9782d79498fabc7b79aad05f4877e4d4480f4f46a1452bd",
    "difficulty": 1,
    "chainwork": "000000000000000000000000000000000000000000000000000007c7d0a682bf",
    "branchlen": 0,
    "status": "active"
  },
  {
    "height": 31570,
    "hash": "b6a9feef7875ad5a589faa30f3539105670f812dd210a9ff4825a981ea5dfaac",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007c39dfe64a0",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 31503,
    "hash": "d98e01504a9dcaf30af84b64886dfd5b8d5d46c0c904507b607f40db226eb2d9",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007be56267148",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 31503,
    "hash": "fcf6eae649f608e0aed25a6c017c8a12e8264c477d7a3a4592126e377b268cff",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007be56267148",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 31470,
    "hash": "61f51288182fe213db7fcd40ee14322e42f1cd626f2c24c92e63b1a73a96238e",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007bb46193432",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 31465,
    "hash": "452f9e4435354811ae3929b739a4bdf28c79c10fa9aaed15cd200599172e003e",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007bb045a26a8",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 31448,
    "hash": "ab97cf1cd5b80a1958a20ee8bfac5b86e58b64f4dcfbc53226e56b15d53b0fbb",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007ba32af3afe",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 31438,
    "hash": "f57eb6353370cb1ce3ddcc7d82fee440ca9e86fe98e237f2658ba541a7093d41",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007b960ab882d",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 31424,
    "hash": "fbafea0ac6d348d2267e9eb2073f12309d434314ec87e5bb6daec03f16d450ab",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007b85669efb0",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 31421,
    "hash": "9acf386b53da3e39e88d04acef6582103e802dec53dedb7c37c1efe1f211984f",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007b7fb19a5a0",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 31401,
    "hash": "6440c8e73d22120fe051b67377737c9f465af843f29292f1a081ba269ca7912c",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007b6d23c492e",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 31394,
    "hash": "4644229b036214fbf5bb44fbf11fdd280864bbe40e20150e93eb5ffbe4e3156e",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007b668a4a244",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 31324,
    "hash": "2c3a751c956412a6f55f8a0eb372b2846f5a003ae2cbf98a35392f9cb6a2ace6",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007b34b6f5428",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 31288,
    "hash": "293a714a375a46b4ad8a25d50a53d4a3357d41811518c16a7044e4bdb06d3e33",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007b0d5761f41",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 31232,
    "hash": "c6066f589a8a2264618db854037ffaa051542c5022028083ff1e6935e5836b51",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007acb6b043e3",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 31171,
    "hash": "43b2979c722bbbd90b8b35ec8e2c7d225e3710c0a988f8856ef0e0c7f3dcd57b",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007a79d13f0b5",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 31142,
    "hash": "2f22caca66d97002a86c4856cc3cca5aec53e6a116d75b58c49bf9efe38cae1b",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007a583c926e1",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 31138,
    "hash": "b9bf7915a3c53d41923d69642e8f052650ef622193472112ef1943bdd592426f",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007a5556b70be",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 31126,
    "hash": "0dc2feaa90ebce1d10d0d9d8929b533cdc2905407a7d0e5cd5263452eb99726b",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007a4de7b833d",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 31111,
    "hash": "0ee4bedd7f52bbc0b125809331057e43ef70a64cdbe77c66101ff2ede7444485",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007a386551e98",
    "branchlen": 2,
    "status": "valid-fork"
  },
  {
    "height": 31059,
    "hash": "c3c649e2771bbee666e9ee8c75ee1347acdef95fae4ad69515af9be7262864d6",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000079f0f6e1d82",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 31043,
    "hash": "0febcc132a91a61107b1aa5c2a19396292db2280ce729526e06b47765eb256ad",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000079d6b0fde01",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 31027,
    "hash": "11692d5e1dec3864538fbfd55d7fdfeaa8fdf92e4a900beea29bd8f3186cc518",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000079c8292e074",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 31019,
    "hash": "4b172d1a13b42401f140853380cfa354ede6f000e90a375685dbc201a808231c",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000079c3a4e66a0",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 31009,
    "hash": "7fbed4cc6efaf6c70f2c740b7a49abdc7b676c1962e0040dd4698454f919ba4b",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000079bf7b9886d",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 30966,
    "hash": "caf502bb39bff6d6d87257205b24085314bc9e697638dce9e3b5c2d23fffe590",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007991bcde27f",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 30950,
    "hash": "8cec1e0b5533a9d1bdafabbf88913af2599cf42f7aeaec4021c9cd30f25d2fd3",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007986c89f65e",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 30947,
    "hash": "6db949576e81628345e24a25869a17d9a5d6c234470280e93bc3dca832081e10",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007982d1301be",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 30915,
    "hash": "3879e1f6115b2b308c9bafcb59ddfc43ee3a3f79e8325ec1ba989323e87932bf",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000795bafaa14a",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 30778,
    "hash": "6c172aee6bb94dfe7f8980d52e6e36a53c2b5210e5ab9fa2a3bce42189aab725",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000078c381fcb77",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 30769,
    "hash": "e31809a628c972239e0aa2d79cd845edd7541867f10ae2f9e149aa2359581696",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000078b48ae70d7",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 30761,
    "hash": "f4b6351e8225d8dc9d1dd91c0ba86348fde683752ef561928b8971d5663d7fb7",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000078acb322176",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 30682,
    "hash": "e4ef76fe145fd7ec5fdd47fb2992dbad5368f509779d5b466d9d470fb206dd65",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007847843ec17",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 30670,
    "hash": "a79f6b63307e983a44cb64c8b4bc169045e17b3ce320ccb6c9662767b67528c9",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000783c1c76d72",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 30637,
    "hash": "413c095d9db66eb2f9d17d11b9f6aa6a7ee7b5ef786ecaf01748b043f78f73b3",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000078198a8d5e2",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 30620,
    "hash": "54806eca06495150e343561db358607d8fe9e158347065bc3086b5ee84cc9ce5",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000780604bd246",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 30612,
    "hash": "7f28f98fea82fb8ffa78874d0c2cfc5042ef9f334158a77dfc26eda86059ffea",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000077fe0b1134a",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 30570,
    "hash": "63530cef45838216c9a61002ea714057a337f37c94264a2ca12afc062005a8ca",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000077e17c160fa",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 30564,
    "hash": "696ef288e843afaeee7aaa9c7423a73c3fcf5a6a935807f82fe7106392aac3e0",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000077db40e98a5",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 30480,
    "hash": "d1193a893fcc3081b46ab18134e308d59218e92f82dca554ffdf855de21bbcab",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000077937dfb748",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 30467,
    "hash": "f1a4d1138eedf694f971a5e997a6fc4a1afee62a45e44510f68dfb481923e780",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007787a4c58f1",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 30459,
    "hash": "b38c64f32adada29ef29a4a319f847b1f578d4a84b557290c09774b8d082bb65",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000778135357ba",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 30456,
    "hash": "fe898545e51fb046b6b997cdb2b0d8fbc11c9aa459c10413df4a03b23566453d",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000777f8e2bbf6",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 30451,
    "hash": "de66b100c4cea6bfee02aea08e165a6c4389ce3f79bb028f0548e69700061929",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000777a2b87da5",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 30442,
    "hash": "65b193171dc09decba8dc5b5cb8ba501560f9a28241a2591697f3b11a03ab617",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007771e0832ec",
    "branchlen": 2,
    "status": "valid-fork"
  },
  {
    "height": 30425,
    "hash": "7c41e27f7b5a410bc259c5266ccd24f918a85458336db8cba0062a3e318ff0be",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000776245bd21b",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 30422,
    "hash": "aecd75255354afef8eaff80d5b17da004c549710a3f22b4c3eb7476d722c7c5b",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000775f089ac0c",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 30418,
    "hash": "5ae882fc3f4241ace54ea3c0b5a66f8fc7a8c8e8c17fcd7ddd723fbc1cf5fe4e",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000775a72a7b3b",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 30360,
    "hash": "cecfecc0eec602bc21c4d2785b4a185b99bd536b5a49e62f991d451543390878",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000077147672238",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 29741,
    "hash": "3e71b91f421643b2c6a80faa1d5b991c2dee7d619d4e322c4156832e7574f56d",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000073f0b429386",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 29725,
    "hash": "b0152bd41a51477c2172b6ca542244b0f12780a8efab18267efe91b21c1cf810",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000073d45d29df8",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 29668,
    "hash": "142a1e8666cf0445aad0a16e9ff07c90a7f2fa819efb476d5b62f510a9a1f86c",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000736fd45e8f8",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 29637,
    "hash": "825185f16c89a7c88a3ea3c0e5966427c7ebd0d3aaaf3d3bc86712ef7f68d14a",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007344674094c",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 29635,
    "hash": "1e1522865ddc1c209e224a4f22fbbb1c24c0bf7a74a12c1fc36931c07e6ac9f7",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000073429fe3457",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 29631,
    "hash": "6fc18a486f6e7e7a879cd3112cc8adb59b9ff3ddc5112d9438f26b61eef48f3b",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000733ea3fa2b0",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 29625,
    "hash": "535c4482e7184d92b3570934fbb360c79cc6473ba3c91d9cf06007a0f7b356b7",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000073387420d15",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 29607,
    "hash": "7cb618176987ce6cde31e3893a130396f2af56d0f1072df627740811c317eea4",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007319e5624b1",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 29594,
    "hash": "677c8e4c05c58a83058693bdd66a74a44817237f466a92e6c8c8345e4ca1a8f4",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000730257f30ee",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 29585,
    "hash": "2e5d20df8a7f79ed0e91d1201ef04eeb9159c58a13f5b266fac09ac7d729e521",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000072f5aa70e53",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 29570,
    "hash": "2122d1bf5124393e31f3d62234a16064f6c936bb851cccf3ba6a556c94c47a36",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000072e092a115a",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 29563,
    "hash": "e3e6553325aae7f45a7add8aaf57e3549f51811bddd5f27f76482191a0a7216b",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000072d9577e637",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 29542,
    "hash": "48687948761edfbbde33083c0592f3c27e945717fe96431a28dc054febd9c3eb",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000072bda19436b",
    "branchlen": 2,
    "status": "valid-fork"
  },
  {
    "height": 29532,
    "hash": "16b876a0df7eb846fb7e64dec45e62cbd02a888d3b64637cf3766a505b26d83c",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000072b3abeb049",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 29508,
    "hash": "02793ebeedeab9d0216fdc6f35d3dc97c7fa7caafe93cf4ee4b577f98a1647c9",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000729e2910010",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 29464,
    "hash": "ad3bf1faaf4a7c1b9bcaa5b715648ca5e2711acea9f22bd862c142eb738a3be0",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007271b5c9b3f",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 29463,
    "hash": "48c84731002f78bf2392a3ea2cbffc03f692d9090f4ac0d89a73c28af9eaefc7",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000726fce72c02",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 29452,
    "hash": "5ca484112146e1542b37a2093c89ee63c0000c8eace59977d6574fff8c17ba4c",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000725eb42b439",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 29122,
    "hash": "1e5dcbf277483af085cd9f760ef4ddebe8e2e00cbb3c0a2000388d1330b7cf12",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000710fc7d56b0",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 29112,
    "hash": "731ca59df2cb8d0183a668cc4a63a970360876d07e9f5aad562e5f5b7c9fe1c7",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000071039bd7535",
    "branchlen": 2,
    "status": "valid-fork"
  },
  {
    "height": 29098,
    "hash": "dc41631a8d33dc3755f5c119d3bdc41f569513840304795dc4c3c099ca13781e",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000070f097f525e",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 29075,
    "hash": "182c7d8b126d3c9c81b1dae1fc897216aaf06fc2c09feed00f60ffeaa5f9db0e",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000070d98d90477",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 29047,
    "hash": "3c244eb6887990e9561c325d8199e1271b32dbe9a27b4bfd084238414900a657",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000070af5941387",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 29046,
    "hash": "4f1322c2f7e884377a874df60940b7e95f601c98fa063dd76d494bcfcb95c678",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000070ae9f7558b",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 29032,
    "hash": "095fb1ac73d5ee6cfa2709c90d3dc8b62de3a4eea7faf420f73934a866216166",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000708ec381bd8",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 29023,
    "hash": "256ba5d436084c3aa28fa90a6e0c05144c611341c2f5d67e73e4678e795a53e8",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000070851145211",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 29013,
    "hash": "40d8cf3dcc9f05339d87f7d7491fd43ec9e7602dfe0991b32330e7b3ba280a67",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000070787efd61b",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28994,
    "hash": "7ce9b6258eda2350b34315bb11f1c62edda35fbb225723942f22accf73510d96",
    "difficulty": 36.26775666655811,
    "chainwork": "00000000000000000000000000000000000000000000000000000705db576f87",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28981,
    "hash": "7964ddc1ab8d036004fd61ba399085d1e4bfa66b1c25ef8f929b72113582ce73",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000070466b589f0",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 28950,
    "hash": "dfe2e29bf43a567e93f7764c58a63a2bbcc2e430f6a9f1c9d3b2aa7e0df3d1c1",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007013d0bda3e",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28943,
    "hash": "c64fa4407f50b7ec218711f1f1623b34909bca57164ee47a778d1c1093704ba4",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000007009d9ece39",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28940,
    "hash": "96fb0c208173a17760668f705750e55c37497d414ea825b86ee42a4f3da3f22c",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000070065c5e642",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 28929,
    "hash": "eabdbc2264453cd062cf119f639f7f7b058d29e970aacd38b3f526d0f8776042",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006ff80b38f7e",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28924,
    "hash": "70e83d6de677f05034ffe30e50f95ada2ea00290597b94a5bbd7f6c23edb3c0b",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006ff35919ee5",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28916,
    "hash": "4f14cff7cf3c549e8808d71a80b88bbbbdf3c639770adfef9a9b286a7b6f2015",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006fea3d5996d",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28899,
    "hash": "8dd2b7d430ed5a927279815102183d0ef784a09af7ebc7c59fc9ed22b2135e3d",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006fceab0382c",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28898,
    "hash": "136177656dab53a0c504500dec3be58cef726477ea4d19deaca7b9027166ad08",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006fcda80aa76",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 28867,
    "hash": "f6d1677b98d7595989a7722dfe3804ef790427b8efbd72681ab2ecfd9f1120e7",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006fa7bd82325",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 28865,
    "hash": "cb2963c37cf7d6efaca3dd2a4d49b253436bba4be77598cd54cf6ea8d089c45d",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006fa55ad6a02",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28832,
    "hash": "3fc47c01e4475a01f12e91b75ee499c7db2bfb569fcb86a50fc439d6586fe248",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006f6f0307b06",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28797,
    "hash": "c2d1322c3b6d086658fb51b46396d81f708ba55a22fcc3c56311e248a9aa29a9",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006f34037d37e",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28794,
    "hash": "e87749ac4e6e8c7ce4b7f5f2413642ec8c2c9f215857ce65ec5cdcdda9ce55bd",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006f2eb20d9e1",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28773,
    "hash": "01f6f43adcb40b8e8751bca40ccc45cf00df7c464521095578e1f25ef2ed5b7e",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006f130e12c2f",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28768,
    "hash": "bf8169c941ae3a4c59565da0d523eb21be26d96fcd8a725cddc5bc54eb15594c",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006f0db3cb87e",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28764,
    "hash": "af8c36ab9a8587474fd250f2020f41628664f095f3e773d54a32bbcb3245ba25",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006f0a775965f",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28759,
    "hash": "b3a799cff22403c6efce8824a381da81e0baf04d4a010d7df854bada9fb0e932",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006f0040407ba",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 28757,
    "hash": "a473643c188590ed353260f112dea6155f78b2327883a10940e07135b316e3b1",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006efcfe51612",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28753,
    "hash": "ff355fc72ab14da8bf499522770b1a0793b8599dac5fe5ebb8bf827dbe52d161",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006ef708cda8a",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28731,
    "hash": "dea80e410789292ef985be758c4ef6ebdcab796c08707c3483fa385878ba8586",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006ed3c3579ac",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28730,
    "hash": "deaca4d69bd19911b5cde2044851c12e1b8ae970d6440159ad47829babafe1d8",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006ed2aa034b0",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28723,
    "hash": "c96d4265c7bdf7a45e5cdffd9eabfd4509230496175de9eb5ea622010d66f9f2",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006ecad7c9790",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28707,
    "hash": "d757c04dfa1d65a918a61a495305a69ef52ea8d322db5140bf4d64667f58c463",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006eb31522abc",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 28705,
    "hash": "c601900e4e40644a5c8b4e2d22e7f242faeaafbe4b1eadeab13e3b88231ab86f",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006eb069d67fd",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 28692,
    "hash": "80e1668e559020e0e81b960022c89e2a68135924f4ae3c95276f3c8a0f77efce",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006ea64bfc884",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 28681,
    "hash": "599dab0401c4160507dd56423077f7845ff76c4025d09cdb2700b2cd14cb2dbe",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006e9c9888dc6",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28675,
    "hash": "5be31ec24a8decb34056ffea1d94718afa00c8eadda893f2668af63c962e8c0a",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006e8d294da1c",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 28667,
    "hash": "a7777e900bee041f94053e8ec0a807452cb1c3355ff954f55049dd6078779752",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006e7634901f9",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28645,
    "hash": "b6cb7579b7d03455796354d899953e876df503ee1ceaee9ef175fef1146080b9",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006e47fe2c999",
    "branchlen": 2,
    "status": "headers-only"
  },
  {
    "height": 28610,
    "hash": "6388649e75613840e80a6e3679e49a5ecacf5db4ee270198d878fb712c4db1ec",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006e0e7e3cf10",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 28584,
    "hash": "6a4d03fa9cd6658dcfd5b8de0a946a671cd87059b40cc5be739ef93083cbc129",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006df532e8f63",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28582,
    "hash": "88eb109b0c520befcbe4ed7156e606430d61d28eb2e7fc99341dc2a683fe4ab3",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006df3ee7932b",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28579,
    "hash": "c359cda18bc2010bd6130b02e467688e581397d51a48ee946fbb6cf0ba97cfc8",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006df15cc7ede",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 28561,
    "hash": "3ad369fa7da539aa5184cbb441de778290fd6921936a027274f705f990142e69",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006dd60e5f00c",
    "branchlen": 2,
    "status": "valid-fork"
  },
  {
    "height": 28555,
    "hash": "630b0aed70769d4144b0ef05535d9e415f4fbfe300edc18a5ca6e0f9c49668b9",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006dce02e0b44",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 28547,
    "hash": "dfc4654f8f7699d4a45971ef46338ed5d4565c25f69e2e0ee6daea01ffa2c90c",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006dc28515acf",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28534,
    "hash": "0aa83304c9b8b500d8937fd8eeb66d722e47983b4a42857b843096dff3acb8ca",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006db091ddac1",
    "branchlen": 2,
    "status": "headers-only"
  },
  {
    "height": 28530,
    "hash": "bf50afa243494fca96daadda31aa3b5620882451a2c0659e664299fa89e2eecb",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006dade2fc6d0",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28511,
    "hash": "e92c67005ec3220355f594e95298b4bdc169f94cf30e11581548a24df966c811",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006d908e7eed0",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28510,
    "hash": "636613ba132f29204417ba628abe12f97ba19ce6b268f34924544d81703f7395",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006d8dbbed055",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28487,
    "hash": "0914c4f7781c3bb9aba6640824893abf28ae4f21f43ab767274cb18354ef22ee",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006d63343b775",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28483,
    "hash": "67038bbcbbe819902a1e7484e0341cce918489e1869a30d3f5ade7a702fb82f4",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006d600858d09",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 28481,
    "hash": "6193dae027ea989b5fb5921ef9c076607bdf2e6e69cff1100a9acfde23622c09",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006d5ebff1978",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 28473,
    "hash": "4966abbbee1498f0f255aade7697ab6936eb068cd2f4f0d67af5619cabfc470d",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006d585fc0c6b",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28466,
    "hash": "766e8f103352f8c09f27aec25cb368d4f85bd9cbf66fff33d8417ceaecb9637a",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006d50c462a07",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28464,
    "hash": "843724bc3d4591e707017cae9d70e0192511ddcb3582ecd542276678811c7607",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006d4e6ba42ce",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 28462,
    "hash": "aff5ffba9f9b362b0ac60f0c0f3fdef754320e29ee425804725a29b9cf48b2c3",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006d4c823e6c4",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28458,
    "hash": "5b13b80b048dd3639dbd2ba8d8684e8cee6f556ca5d95feea29ac69caaed0867",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006d46bb14b95",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28447,
    "hash": "0e5b6c6611e76b713891b01a159c156ca7b0c01ce1f158efdfebf196b5ddd210",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006d2f573aece",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 28443,
    "hash": "c1e4d406ad22b746214b32130e1b19febf3618a9a97d0d3a7bc49dd9d07f2b29",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006d290123155",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 28438,
    "hash": "e36ac5bf90cad7bc1e5f5a7cdc888ec65088eb0ae40d575d62b2689c232390e1",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006d1cc796800",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28392,
    "hash": "34ad28cfba701d362e5742828e242e4eba4e3b67879922dd0221560a5170d637",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006cb7b737fa4",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28376,
    "hash": "d27d35dcf2af6ef70f1f05673738646e552983c72b464bc7ae53795de7056d1a",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006c99d1555dc",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28369,
    "hash": "6e38a9e9cd986ee33e2ae97e1fc7592d65483699aaa58e748164165b4e03f124",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006c930d90beb",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28367,
    "hash": "e9e24cf6495e813e7c3183b31c865d28c3c723e623a09aa1c11242c083ad487a",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006c9146b7199",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28343,
    "hash": "a696e5a4459162651108b04846939b44060b40a555adb5d5f2afe7ad91ebdf14",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006c71f9b6c19",
    "branchlen": 2,
    "status": "valid-fork"
  },
  {
    "height": 28332,
    "hash": "7610a0172af596928229b5e0caec76645cca2ec30a4af612517e8881065c0c30",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006c6320d2246",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 28302,
    "hash": "f1be9b317694317ad30bc204d785c601a87dda231fd6b9b68bb09f6ae90860e6",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006c4259a160d",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28294,
    "hash": "d56c69faa0a0196299bf4b70aba7027e2d6b8c0f26a17c394328790b7c6ba6d7",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006c3c4935250",
    "branchlen": 2,
    "status": "headers-only"
  },
  {
    "height": 28285,
    "hash": "59d9f8a25b37fe97472cc11112479aa57ff154973ec0089de61011feebc2a740",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006c34b0b940f",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28283,
    "hash": "d718a5e5d059f74864f8420fefb4feb6b1ef482da92cb88335984dab33957c5d",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006c32e136439",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 28246,
    "hash": "baf1e2752954e4d4f4a10dcc641286d5527391696ddc84f3177f6a4d57547cb7",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006c0f6cca598",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 28245,
    "hash": "e015d63b8556028909bf36a8f89a79101dae263ba7eee832ca528b82641b9c71",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006c0e32bb65d",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28216,
    "hash": "53834c647af72777ba6da4083cd0c25dc8c26a9ac357d7f70c73934618b19461",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006bea2862237",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 28209,
    "hash": "d15df4ce5262c60a3b836d4a7be77fffdf5fb909bf4263dc53a96d2a0c37f252",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006be4ab6d144",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28201,
    "hash": "7a9b7b802ee2b42a634309b8d64916105b3512acf81a1041c11b99f7f6ca2618",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006bd98e4fae4",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 28192,
    "hash": "25e0414c9472bd8b93102f031282f39246baa1ba6e93a2b9f22289e0d6f3eb9f",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006bd0c2e4d51",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28190,
    "hash": "b5772056bc98dd1d8a1271d64e475b428613042be7e86f6b818325148623eb9f",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006bcec0485cb",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28188,
    "hash": "35a5bfc271af2d679b49babc7cb9c4e0c673a5573058c36406634c62c06b86b5",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006bcd2f649b2",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28139,
    "hash": "510d4757b6ca7bb0f0b9c036516b7126f69ea6fc50f718beb98758896fc16ddb",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006b7a3c91118",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28104,
    "hash": "33f1afacf0ab7502b159f4e4a68b6f45457296b362efa7290edfd18b7f295f73",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006b462f24f35",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28102,
    "hash": "975dbc706bf1ec3f609a3cb3924e10272579609a8a5480c2448b1afd00c980cc",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006b43d200699",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28096,
    "hash": "001bf5f8ddae3eebe08506e7a8426bef5bf1d3cfe1f05b885f325c54cb060e9d",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006b3df43c652",
    "branchlen": 2,
    "status": "valid-fork"
  },
  {
    "height": 28077,
    "hash": "51c96cb62693ccdc665d8ca842787dcdfbf6363f8b9fb2f5cbb08cb3a73d0584",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006b27c188a55",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28072,
    "hash": "87b613fcc79d028386ed68973c78f1fefef031b7dd05793d35f399ad95a5b262",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006b2139d2917",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28050,
    "hash": "3d9e7f2e94f0a643c9e3fc2d2967df5fe4d26f76f4434935d2446cea1d3bb82a",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006b092251cc5",
    "branchlen": 1,
    "status": "invalid"
  },
  {
    "height": 28049,
    "hash": "4366d31e6249a20f28c0ea3ea3abd5d8e41051be8cc1348b480a6c5fe66a94d2",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006b0891485a0",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 28024,
    "hash": "0cc3b8ae2c9629902164a92b7f9a41879d896d19af3330fb267e971062ee8827",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006aecbaa0d39",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28009,
    "hash": "256e22a1aeb5282b175f06c781e7bd6bbdeefbae0ed71cd20566251b7f904c51",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006acc1752c59",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 28005,
    "hash": "b52d99bd824fbc03e33cee370a1729e20aba7e97e7db20149a3da45c47223e39",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006ac404b630b",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 27998,
    "hash": "c58096369638d8e84cb6c0889e807c5a9c97adf5a7200eebea0a42024a12383e",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006abbdef497a",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 27997,
    "hash": "7137c2b09d5141710a6a274d1e557ad934e2d4b986714439e2edb0811f1e855c",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006abaaa8219f",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 27972,
    "hash": "5d0b7e8ea32c6b17d1c903bfaa1707a974ee353610f90c851d0e4f5c73fad745",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006a996cbb9d4",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 27964,
    "hash": "ce47bca0cb599bcccdfd99eee110883f61df426b359308952f0f8d169859655d",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006a8ff74aae2",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 27960,
    "hash": "bc3f2fafb7500ab23d9bb74c0c4f26ce28b48ee85dd24a767b47443b63c2f9dc",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006a8b3eccce7",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 27949,
    "hash": "8080338c17c5a458831d5ab7aff2bcb0c4fb7961cb65c3ead1e418b18cdb6e97",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006a7e0d095d8",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 27949,
    "hash": "85bd8167e4e6a98652bda539dc20e014a12856275b3a6b0bc5c618afe0a9b7a1",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006a7e0d095d8",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 27939,
    "hash": "ff0483b14ffeb1ffa0ae93c6be21fe352cd23fa7c01c093bca60ede0f5af8ff1",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006a73c771c21",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 27933,
    "hash": "29fc7ea65be3b80d8c71a51f7decda50b937ae201be12a3df9a14749428b2cdc",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006a6b466596c",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 27929,
    "hash": "95af337fd9818e46e0cb5ea4b1d551ccbdfc73f9bd9829763bd2156e925148ec",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006a6560286f9",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 27926,
    "hash": "c5bf3d2f91ee765cf01ad5469e459766595b2c6986b331c9d369f1d3c0726ea6",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006a63a06617d",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 27914,
    "hash": "9b185936db6327c3a6d614364247444935754e4e2c9289846abf03bb477837e9",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006a531c0fee7",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 27910,
    "hash": "6ba676d4e5ad1e89c92538f53a9a8cb4459b1febf89c1125e8df94ef0122c452",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006a4b7a0ce62",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 27887,
    "hash": "6d57b60baf0f703af908a1e290e98d0e3741a91f2f3d02f1a0828dafebf875e2",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006a2c8e6a23d",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 27885,
    "hash": "a584fad009966e6b32ae942617ba83313ee719e30dbab1b95bf75f2107c470d8",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006a2a22e084b",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 27882,
    "hash": "10d0fd342d29420313c87ba7ddeb14ad49c53fa5e4b8e4fe115be0ad9b27dee3",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006a24a5bdd5f",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 27864,
    "hash": "46f946a3f6c2e8fcff4167d07ceebc4fc6e3b61112fcf785a3b44e99b629141d",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006a00efe4190",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 27851,
    "hash": "3a9c6ab58d2c4b8f5504891cb017c0ee45cef4e2eec5b7f3f88e5a6a572c47ee",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000069e8637f587",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 27849,
    "hash": "bbf288e52c27948003bd85574329b3fc45070bfa54dbdde6b455bf5c9acbb242",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000069e643a8128",
    "branchlen": 1,
    "status": "headers-only"
  },
  {
    "height": 27826,
    "hash": "1bbb45d1e3982d420502380a5d7b69483a39ef077108e88519b0fa3c60b8bbca",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000069c71577105",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 27819,
    "hash": "99aa7e15f4b1b7f1ef73b21b7cf2d19ae3a8d850a1d0862a3e54001f78675a16",
    "difficulty": 36.26775666655811,
    "chainwork": "0000000000000000000000000000000000000000000000000000069be7c6c978",
    "branchlen": 1,
    "status": "valid-fork"
  },
  {
    "height": 27787,
    "hash": "01f760550d9783855a6c103a0f8362759421a9c29efee8145b070047cf4cedc1",
    "difficulty": 36.26775666655811,
    "chainwork": "000000000000000000000000000000000000000000000000000006985abcde9b",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {<b
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 18, 2018, 10:51:37 am


Hi Jaap,

Oh OK, I see the problem, we dont have the 20bbp requirement spork set up in testnet yet.  So everyone is kind of freeriding right now.

Ill set it up in a couple hours when I look at that filtering of active proposal issue.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 18, 2018, 12:55:37 pm

Hi Jaap,

Oh OK, I see the problem, we dont have the 20bbp requirement spork set up in testnet yet.  So everyone is kind of freeriding right now.

Ill set it up in a couple hours when I look at that filtering of active proposal issue.

Oh, right! That explains is :)
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: orbis on June 18, 2018, 02:02:05 pm
Rob, I have compared those translation and I don't know how, but there was many differences to my "update".
I have made new pull request: https://github.com/biblepay/biblepay/pull/26.
Can you please tell me how to get those english phrases from source to SK locale?
Is it enought just to type there new block like this?
Code: [Select]
    <message>
        <source>any text from source code</source>
        <translation>text translation</translation>
    </message>
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 18, 2018, 04:03:49 pm
I dont think I was in the PODC superblock again

CPID:  c9a2065f******
https://boinc.bakerlab.org/rosetta/show_user.php?userid=1987760

RAC: 32.59
TaskWeight: 100
UTXOWeight: 19

I dont think its auto sending PODC Updates, hmmm, I have a lot of available coins for staking so Id expect to see 100 for utxoweight, and I also dont see any of the podc update transactions in my transactions tab (I forgot how they look exactly, but I believe the look like payments to yourself, which I only have 1 of, and I think thats when I ran exec podcupdate the one time manually)

I only added config options to set up Sanctuary, I dont think config is the issue?:

Code: [Select]
testnet=1
addnode=***
rpcuser=***
rpcpassword=***
rpcallowip=127.0.0.1
rpcport=***
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=250
externalip=***
masternode=1
masternodeprivkey=***
debug=true
debugmaster=true

BOINC Manager and BiblePay Daemon are both running and fighting for CPU, I wonder if that could be a potential issue?

Maybe I am missing something?

https://www.biblepay-central.org/en/documentations/mining-how-to/
http://wiki.biblepay.org/Distributed_Computing_2
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 19, 2018, 03:35:01 am
I dont think I was in the PODC superblock again

CPID:  c9a2065f******
https://boinc.bakerlab.org/rosetta/show_user.php?userid=1987760

RAC: 32.59
TaskWeight: 100
UTXOWeight: 19

I dont think its auto sending PODC Updates, hmmm, I have a lot of available coins for staking so Id expect to see 100 for utxoweight, and I also dont see any of the podc update transactions in my transactions tab (I forgot how they look exactly, but I believe the look like payments to yourself, which I only have 1 of, and I think thats when I ran exec podcupdate the one time manually)

I only added config options to set up Sanctuary, I dont think config is the issue?:

Code: [Select]
testnet=1
addnode=***
rpcuser=***
rpcpassword=***
rpcallowip=127.0.0.1
rpcport=***
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=250
externalip=***
masternode=1
masternodeprivkey=***
debug=true
debugmaster=true

BOINC Manager and BiblePay Daemon are both running and fighting for CPU, I wonder if that could be a potential issue?

Maybe I am missing something?

https://www.biblepay-central.org/en/documentations/mining-how-to/
http://wiki.biblepay.org/Distributed_Computing_2

I don't think I was either. Maybe it's because we're running with so few sanctuaries?

Code: [Select]
10:31:14

exec getboincinfo


10:31:16

{
  "Command": "getboincinfo",
  "CPID": "d9b22fccfae5582d4ee7838883aaa3cf",
  "Address": "yYri6dXZEXtN5j6UhTduL1GSEHSDCW1Pif",
  "CPIDS": "d9b22fccfae5582d4ee7838883aaa3cf;",
  "CPID-Age (hours)": 424832,
  "NextSuperblockHeight": 32878,
  "NextSuperblockBudget": 1279917,
  "d9b22fccfae5582d4ee7838883aaa3cf_ADDRESS": "yYri6dXZEXtN5j6UhTduL1GSEHSDCW1Pif",
  "d9b22fccfae5582d4ee7838883aaa3cf_RAC": 3787.02,
  "d9b22fccfae5582d4ee7838883aaa3cf_TEAM": 15044,
  "d9b22fccfae5582d4ee7838883aaa3cf_WCGRAC": 0,
  "d9b22fccfae5582d4ee7838883aaa3cf_TaskWeight": 100,
  "d9b22fccfae5582d4ee7838883aaa3cf_UTXOWeight": 409,
  "Total_RAC": 3787.02,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 81224,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 1279917,
  "Superblock Count (One Week)": 165,
  "Superblock Hit Count (One Week)": 2,
  "Superblock List": "31591,16533",
  "Last Superblock Height": 32779,
  "Last Superblock Budget": 1279917,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 63.46036500804349
}

Code: [Select]
10:30:13

exec getboincinfo


10:30:17

{
  "Command": "getboincinfo",
  "CPID": "8791a036b545f35e9ebd9333922738ac",
  "Address": "yfSRwqLaiKac2vNtXAaasuLyunCCzfCurW",
  "CPIDS": "8791a036b545f35e9ebd9333922738ac;",
  "CPID-Age (hours)": 424832,
  "NextSuperblockHeight": 32878,
  "NextSuperblockBudget": 1279917,
  "8791a036b545f35e9ebd9333922738ac_ADDRESS": "yfSRwqLaiKac2vNtXAaasuLyunCCzfCurW",
  "8791a036b545f35e9ebd9333922738ac_RAC": 176.18,
  "8791a036b545f35e9ebd9333922738ac_TEAM": 15044,
  "8791a036b545f35e9ebd9333922738ac_WCGRAC": 0,
  "8791a036b545f35e9ebd9333922738ac_TaskWeight": 100,
  "8791a036b545f35e9ebd9333922738ac_UTXOWeight": 24,
  "Total_RAC": 176.18,
  "Total Payments (One Day)": 15017,
  "Total Payments (One Week)": 1294933,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 1279917,
  "Superblock Count (One Week)": 165,
  "Superblock Hit Count (One Week)": 2,
  "Superblock List": "31591,16533",
  "Last Superblock Height": 32779,
  "Last Superblock Budget": 1279917,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 1007.820819631273,
  "Magnitude (One-Week)": 1011.732010747572
}
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 19, 2018, 10:45:37 am
I dont think I was in the PODC superblock again

CPID:  c9a2065f******
https://boinc.bakerlab.org/rosetta/show_user.php?userid=1987760

RAC: 32.59
TaskWeight: 100
UTXOWeight: 19

I dont think its auto sending PODC Updates, hmmm, I have a lot of available coins for staking so Id expect to see 100 for utxoweight, and I also dont see any of the podc update transactions in my transactions tab (I forgot how they look exactly, but I believe the look like payments to yourself, which I only have 1 of, and I think thats when I ran exec podcupdate the one time manually)

I only added config options to set up Sanctuary, I dont think config is the issue?:

Code: [Select]
testnet=1
addnode=***
rpcuser=***
rpcpassword=***
rpcallowip=127.0.0.1
rpcport=***
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=250
externalip=***
masternode=1
masternodeprivkey=***
debug=true
debugmaster=true

BOINC Manager and BiblePay Daemon are both running and fighting for CPU, I wonder if that could be a potential issue?

Maybe I am missing something?

https://www.biblepay-central.org/en/documentations/mining-how-to/
http://wiki.biblepay.org/Distributed_Computing_2


I dont think its anything on your end; I found some problems with the testnet sporks.  It didnt have DR mode, WCG was not disabled, RequiredSPR was not set (I set it to 2 just now), the team was empty, etc.  So I just set these, lets regroup in a little bit and see if the next daily superblock is better.

In the mean time, Im working on filtering the active proposals down to unpaid, adding this now.

EDIT: Please ensure you have genproclimit=1 or not set at all, and your mining HPS > 0.  The PODC update is sent from mining thread 0.  Btw, you should have an error in your log if your miner has been running more than 24 hours with "PODCUpdate" in front of it, that should shed light on why its not sending one. 

Also, you can run your 'exec utxoreport cpid' to see exactly which ones it sent.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 19, 2018, 01:27:19 pm
I'm having trouble with my Sanctuary (never had it running well this time in testnet). I first had the Sanctuary on my windows wallet, but of course that got a 'watchman expired' error after a while. So I tried my linux wallet.

When I start the wallet I get the following messages:

Quote
"Unable to bind to 0.0.0.0:40001 on this computer. Biblepay Core is probably already running."

"Failed to listen on any port. Use -listen=0 if you want this."

After that the wallet just closes.

The port is open on my router. If I add 'listen=0' to my config, the Sanctuary won't start.

Strange. I deleted the testnet folder (excluding wallet.dat and masternode.conf, but I still get the same error.

Code: [Select]
testnet=1
rpcuser=***
rpcpassword=***
rpcallowip=127.0.0.1
rpcport=40001
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
externalip=***
masternode=1
masternodeprivkey=***
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 19, 2018, 02:29:08 pm
I'm having trouble with my Sanctuary (never had it running well this time in testnet). I first had the Sanctuary on my windows wallet, but of course that got a 'watchman expired' error after a while. So I tried my linux wallet.

When I start the wallet I get the following messages:

After that the wallet just closes.

The port is open on my router. If I add 'listen=0' to my config, the Sanctuary won't start.

Strange. I deleted the testnet folder (excluding wallet.dat and masternode.conf, but I still get the same error.

Code: [Select]
testnet=1
rpcuser=***
rpcpassword=***
rpcallowip=127.0.0.1
rpcport=40001
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
externalip=***
masternode=1
masternodeprivkey=***


The main problem is your rpcport, in 'biblepaytest.conf', the rpcport must never be 40001 (as that is your P2P port in testnet), and it must be a different port number than the rpcport of any running instance (IE prod).  So say for example you were running your rpcport as 35000 on prod, it would have to be different than 40000, 40001, and 35000.  So just make it something lower etc.

Biblepay uses 2 ports in testnet : 40001 (for sharing blocks), and the rpc port (for administering the node).

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 19, 2018, 03:29:02 pm

The main problem is your rpcport, in 'biblepaytest.conf', the rpcport must never be 40001 (as that is your P2P port in testnet), and it must be a different port number than the rpcport of any running instance (IE prod).  So say for example you were running your rpcport as 35000 on prod, it would have to be different than 40000, 40001, and 35000.  So just make it something lower etc.

Biblepay uses 2 ports in testnet : 40001 (for sharing blocks), and the rpc port (for administering the node).

Oops  :o Thanks for the explanation. I probably was tired and didn't really think about what I was doing when I put that number there.

Wallet is working like a charm now! Sanctuary started without problems.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 19, 2018, 06:13:08 pm
I saw a PODC Update Transaction fire off 10 minutes ago :)
(It doesnt look like I can filter by Type "PODC Update" in the Transactions Tab)

Update: Now I saw a "PODC Payment" transaction, I paid 1,045.4 tBBP
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 20, 2018, 12:57:30 pm
I saw a PODC Update Transaction fire off 10 minutes ago :)
(It doesnt look like I can filter by Type "PODC Update" in the Transactions Tab)

Update: Now I saw a "PODC Payment" transaction, I paid 1,045.4 tBBP

Great!  So things appear to be shaping up.

So I found a bug only affecting the mature_consensus (after go live feature) (I was testing the mature_consensus bullet point) and it needs a little work.  I am going to send this in today for the next testnet version.  Note that this causes the sancs to not come to consensus until all sancs upgrade, so (that is why) the boinc superblocks are not really staking regularly.  Lets try those again after we upgrade.

As far as the cosmetic features like the sort, if you would like to pick the top 5 most important ones and give them to Bhavani that may work.  Im going to be focused on making the pool add tax accountability records for Bloom & cameroon 1, and doing the grand total in the pool by month that Luke requested.  Even after that Ill be focusing on making stratis sync above block 129, so Im looking for Bhavani and others to help on those.

Note that Anton is also jumping in to do more theming.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 21, 2018, 08:47:54 am
I just deployed 1.1.3.3.

Please upgrade all testnet sancs so we can test the mature_consensus feature for the daily PODC superblock.

Its OK if non participating sancs are not upgraded; we only need a few that are actually online and synced to make this work.

(I think we had 3 sancs as of yesterday running out of a list of 20 with 17 offline).

(We need 2 for a consensus).

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 21, 2018, 07:29:11 pm
I just deployed 1.1.3.3.

Please upgrade all testnet sancs so we can test the mature_consensus feature for the daily PODC superblock.

Its OK if non participating sancs are not upgraded; we only need a few that are actually online and synced to make this work.

(I think we had 3 sancs as of yesterday running out of a list of 20 with 17 offline).

(We need 2 for a consensus).

Just started my 1.1.3.3. Sanctuary. Should be 'ENABLED' in a few hours...
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 21, 2018, 07:49:46 pm
Upgraded to v1.1.3.3, re-enabling my sanc
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 22, 2018, 07:01:47 am
Upgraded to v1.1.3.3, re-enabling my sanc

Ok, Im up to 1133 on my two sancs now.

Have you guys been getting paid daily superblock rewards?  I got one while my sanc was off.

So btw, an update on the proposal filter feature:  Its in this version, but as you can see in proposals list, both are still there even though the Groundbreaking one was paid.  I took a look at this in depth, and what it is is that since the supermajority of the sancs went down (Or were not running watchman), they lost the trigger that links the proposal to the trigger to the superblock.  Another words the chain cant see that it was paid.  I was taking a look at this in prod, and I dont think this particular thing can happen with 100+ sancs on line.  So I wrote some debug info for the feature and what I think Ill do is when we deem proposals safe to enable in prod (IE the next leisure release), we can log in on the prod side and test it.  But from what I see from the debug info, it should work in prod as-is and filter paid proposals in prod.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 22, 2018, 12:10:53 pm
Ok, Im up to 1133 on my two sancs now.

Have you guys been getting paid daily superblock rewards?  I got one while my sanc was off.

So btw, an update on the proposal filter feature:  Its in this version, but as you can see in proposals list, both are still there even though the Groundbreaking one was paid.  I took a look at this in depth, and what it is is that since the supermajority of the sancs went down (Or were not running watchman), they lost the trigger that links the proposal to the trigger to the superblock.  Another words the chain cant see that it was paid.  I was taking a look at this in prod, and I dont think this particular thing can happen with 100+ sancs on line.  So I wrote some debug info for the feature and what I think Ill do is when we deem proposals safe to enable in prod (IE the next leisure release), we can log in on the prod side and test it.  But from what I see from the debug info, it should work in prod as-is and filter paid proposals in prod.

I have been getting daily superblock rewards, but looking at my boincinfo it says something strange:

Code: [Select]
18:57:06

exec getboincinfo


18:57:08

{
  "Command": "getboincinfo",
  "CPID": "d9b22fccfae5582d4ee7838883aaa3cf",
  "Address": "yYri6dXZEXtN5j6UhTduL1GSEHSDCW1Pif",
  "CPIDS": "d9b22fccfae5582d4ee7838883aaa3cf;",
  "CPID-Age (hours)": 424912,
  "NextSuperblockHeight": 36244,
  "NextSuperblockBudget": 575962,
  "d9b22fccfae5582d4ee7838883aaa3cf_ADDRESS": "yYri6dXZEXtN5j6UhTduL1GSEHSDCW1Pif",
  "d9b22fccfae5582d4ee7838883aaa3cf_RAC": 4034.31,
  "d9b22fccfae5582d4ee7838883aaa3cf_TEAM": 15044,
  "d9b22fccfae5582d4ee7838883aaa3cf_WCGRAC": 0,
  "d9b22fccfae5582d4ee7838883aaa3cf_TaskWeight": 100,
  "d9b22fccfae5582d4ee7838883aaa3cf_UTXOWeight": 8814,
  "Total_RAC": 4034.31,
  "Total Payments (One Day)": 281920,
  "Total Payments (One Week)": 636046,
  "Total Budget (One Day)": 1151924,
  "Total Budget (One Week)": 4991675,
  "Superblock Count (One Week)": 199,
  "Superblock Hit Count (One Week)": 6,
  "Superblock List": "35650,35551,34264,33472,31591,16533",
  "Last Superblock Height": 36145,
  "Last Superblock Budget": 575962,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 244.7383681562325,
  "Magnitude (One-Week)": 127.4213565586702
}

Code: [Select]
19:00:53

exec getboincinfo


19:00:56

{
  "Command": "getboincinfo",
  "CPID": "8791a036b545f35e9ebd9333922738ac",
  "Address": "yfSRwqLaiKac2vNtXAaasuLyunCCzfCurW",
  "CPIDS": "8791a036b545f35e9ebd9333922738ac;",
  "CPID-Age (hours)": 424913,
  "NextSuperblockHeight": 36244,
  "NextSuperblockBudget": 575962,
  "8791a036b545f35e9ebd9333922738ac_ADDRESS": "yfSRwqLaiKac2vNtXAaasuLyunCCzfCurW",
  "8791a036b545f35e9ebd9333922738ac_RAC": 141.73,
  "8791a036b545f35e9ebd9333922738ac_TEAM": 15044,
  "8791a036b545f35e9ebd9333922738ac_WCGRAC": 0,
  "8791a036b545f35e9ebd9333922738ac_TaskWeight": 100,
  "8791a036b545f35e9ebd9333922738ac_UTXOWeight": 353,
  "Total_RAC": 141.73,
  "Total Payments (One Day)": 25262,
  "Total Payments (One Week)": 1372885,
  "Total Budget (One Day)": 1151924,
  "Total Budget (One Week)": 4991675,
  "Superblock Count (One Week)": 199,
  "Superblock Hit Count (One Week)": 6,
  "Superblock List": "35650,35551,34264,33472,31591,16533",
  "Last Superblock Height": 36145,
  "Last Superblock Budget": 575962,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 21.93026623284175,
  "Magnitude (One-Week)": 275.0349331637176
}

Both my rigs have been paid in the same daily superblocks it appears, but it says:
"  "Superblock Count (One Week)": 199,
  "Superblock Hit Count (One Week)": 6,"

The superblock count seems weird. Anyway, PODC-payments seem to be working. Are we still on one minute blocktimes? Because then there should me more like seven 'daily superblocks' each day, right?
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 23, 2018, 10:26:37 am
From Jaap
"
Both my rigs have been paid in the same daily superblocks it appears, but it says:
"  "Superblock Count (One Week)": 199,
  "Superblock Hit Count (One Week)": 6,"

The superblock count seems weird. Anyway, PODC-payments seem to be working. Are we still on one minute blocktimes? Because then there should me more like seven 'daily superblocks' each day, right?
"


Yes, its weird but its to be expected for various reasons so I dont find it alarming.
But yes you are correct, testnet blocks are still 1 minute, so we would normally have 4 superblocks a day etc.
However, we only have 3 sancs running out of 20, and up to last night 2 of my 3 were down or on the wrong version.

But analyzing closely, the mature consensus part is working and we are generating superblocks when all 3 of us come online.

I just ran exec testvote on 2 of mine, and I can see from exec podcvotingreport, the next boinc superblock will emit.

Anyway, Im glad you mentioned this regardless, because I do see one feature we really need to squeeze in this mandatory, so thanks!
We now have (as of the next version) we have a locked consensus on the CPID list (as of 4 hours prior to the quorum), we have locked UTXO list, and the quorum is using the same source data, so it is close.  However, I do see that we have a staggered schedule set up for downloading the rosetta data (Its more of an issue where the local client is honoring the file for up to 24 hours to save bandwidth).  Im going to look into making our mature consensus attempt to pull the files at exactly the same 4 hour window across sancs and get this in the next version.  (I noticed this recently, that some of the CPIDs has slightly higher rac on one of my sancs, and then I realized whats happening with the cache rules).

We need to reach out to Bhavani to see if he will take care of any of Togos UI bullets.  Togo, were you going to make a list of the top 5 requests?

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: thesnat21 on June 23, 2018, 01:42:01 pm
We need to reach out to Bhavani to see if he will take care of any of Togos UI bullets.  Togo, were you going to make a list of the top 5 requests?

I submitted a pull request to for some simple UI filter options.  It seems there are a few more on github waiting to be merged /reviewed as well.

edit: re-enabled my masternodes on the latest ver.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 23, 2018, 02:39:11 pm
I submitted a pull request to for some simple UI filter options.  It seems there are a few more on github waiting to be merged /reviewed as well.

edit: re-enabled my masternodes on the latest ver.

I'll take a look at this pull.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: thesnat21 on June 24, 2018, 08:03:09 am
how do you deal with WATCHDOG_EXPIRED message when i'm running the masternode from the wallet?
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 25, 2018, 12:56:05 am
how do you deal with WATCHDOG_EXPIRED message when i'm running the masternode from the wallet?

Did you make sure to set the watchdog.conf to testnet?
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: thesnat21 on June 25, 2018, 05:24:21 am
Did you make sure to set the watchdog.conf to testnet?

i dont have watchdog setup, the MN is runnin on windows same as the controller wallet.  maybe thats my problem?

Based on the instructions on pg1 it didn't sound like this was required.. i'll see about setting it up
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 25, 2018, 08:59:55 am
i dont have watchdog setup, the MN is runnin on windows same as the controller wallet.  maybe thats my problem?

Based on the instructions on pg1 it didn't sound like this was required.. i'll see about setting it up

Currently, a sanctuary only runs well on Linux because of the watchdog requirement. You can start a Sanctuary on a Windows-rig, but it will eventually say 'Watchdog expired'.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 26, 2018, 05:31:41 am
===
MINOR  UI:

- Move Proposals menu to a tab like Sanctuaries
---- Set Proposal List to be its own internal window
- Add Scrolling and Dragging abilities to Proposal List
---- or Find way to Shorten the information

===
QUESTION #1:
Should the Proposals Window also show other Governance information?

===
NICE TO HAVE:

--- Add Next Superblock Block Number (getgovernanceinfo: "nextsuperblock")
--- Add Superblock Budget Amount (getgovernanceinfo: "nextbudget")

--- Add Estimated Superblock Date/Time
(("nextsuperblock" - currentblock) * 7 min avg block time)

--- Add Visual Indicator or Sort/Separate Proposals based on if they are currently passing or not.
Example: https://dashvotetracker.com/

--- Add Full Budget Bar Chart (Total Budget and Currently Passing Budget)

===
HARDER:

--- Add ability to View Previous/Past Superblocks proposals/charts/info
--- Add Multi Bar Chart Split by Budget sections/types (IT, PR, P2P)

===
QUESTION #2:
- Add ability to Create Proposal to Wallet,
I assume we still need to wait on this?

============
IDEAS (NEED FEEDBACK):

- Pop Up / Notification
--- when New Proposal submitted?
--- Reminder to Vote on Proposals X days before end of cycle?
--- when Superblock is mined?
--- when Masternode leaves ENABLED state?

===
REFERENCES:

https://www.biblepay-central.org/en/proposals/
https://pool.biblepay.org/ >>> Governance >>> Proposal List
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 26, 2018, 07:49:50 am
Awesome list Togo 8)

Quote
IDEAS (NEED FEEDBACK):

- Pop Up / Notification
--- when New Proposal submitted?
--- Reminder to Vote on Proposals X days before end of cycle?
--- when Superblock is mined?
--- when Masternode leaves ENABLED state?

I think that these are great ideas. I don't know it it's technically possible, but it sounds awesome. I especially like the 'voting reminder' one.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 26, 2018, 04:52:24 pm
Thanks for the list, I'm looking at the github commits and internally debugging the consensus feature, please hang on all.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 26, 2018, 05:34:33 pm
I'll take a look at this pull.

Wow, nice work!  I actually thought you were pulling my leg all this time, I didn't know you actually knew how to program.

Great job dude!

Alright I merged it in and the next version is out there for Linux, but I have to get my son, so I don't think I can get windows out til tomorrow.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 26, 2018, 07:22:59 pm
Updated to v1.1.3.4, Sanctuary Enabled still

Update: Few hours, No problems so far

Im filtering by PODC Update, and my transactions are 1,100 BBP
and I check my RAC and its 462.94
https://boinc.bakerlab.org/rosetta/show_user.php?userid=1987760

so I need 462.94 x 18 BBP staked to get max reward, which is: 8,332.92 BBP
The wallet has 18.9 million BBP

exec getboincinfo:
UTXOWeight: 1112
Total_RAC: 462.94
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 27, 2018, 02:03:10 am
I submitted a pull request to for some simple UI filter options.  It seems there are a few more on github waiting to be merged /reviewed as well.

edit: re-enabled my masternodes on the latest ver.

I took a look at the pull request. I was actually looking for a 'superblock payment' filter last week when I needed an overview of BBP payments for CameroonONe. ;D Awesome!

Unrelated: I've updated my Sanctuary to 1.1.3.4. Rob, are there specific things we need to test now?
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: thesnat21 on June 27, 2018, 08:31:34 am
Wow, nice work!  I actually thought you were pulling my leg all this time, I didn't know you actually knew how to program.

Great job dude!

Alright I merged it in and the next version is out there for Linux, but I have to get my son, so I don't think I can get windows out til tomorrow.

That's was a small thing.. but yeah not entirely sure how to take this! lol

Got  a few more things i'd like to throw in .. things have been a bit more hectic the last week or so ... hopefully it'll be ready soon.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 27, 2018, 08:39:14 am
Could someone do me a favor who is running the daemon and see if this has stopped happening?

https://github.com/biblepay/biblepay/issues/5

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 27, 2018, 08:42:36 am
I took a look at the pull request. I was actually looking for a 'superblock payment' filter last week when I needed an overview of BBP payments for CameroonONe. ;D Awesome!

Unrelated: I've updated my Sanctuary to 1.1.3.4. Rob, are there specific things we need to test now?

I just released the latest version as a windows version also btw.


Let me see what test cases are left.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 27, 2018, 11:14:27 am
Could someone do me a favor who is running the daemon and see if this has stopped happening?

https://github.com/biblepay/biblepay/issues/5

I never had this happen to me...
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: sunk818 on June 27, 2018, 10:13:19 pm
biblepaytest.conf
testnet=1
server=1
masternodeprivkey=xxx
masternode=0

-conf as a parameter to cdhoose different .conf file didn't work for me, but putting testnet=1 in biblepay.conf worked.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 28, 2018, 02:33:27 am
biblepaytest.conf
testnet=1
server=1
masternodeprivkey=xxx
masternode=0

then i ran biblepay-qt -conf=biblepaytest.conf but when i go to tools debug console, says network is main.

my receive address starts with a b, so i don't think i'm in testnet

-conf didn't work for me, but putting testnet=1 in biblepay.conf worked.

sorry if you covered in this thread or another...

looks like i mined 1M in a few minutes enough for MN.

I never tried the '-conf' line, but you can also add the '-testnet' line, and your wallet will start in testnet.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 28, 2018, 05:45:25 am
Could someone do me a favor who is running the daemon and see if this has stopped happening?

https://github.com/biblepay/biblepay/issues/5

I tested from QT Wallet, Tools >> Debug Console >>> stop, no issues

Ran command line daemon, waited for blocks to load and verify, ./biblepay-cli stop, no issues
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: thesnat21 on June 28, 2018, 07:44:31 am
I'm not sure if its the same thing, but when heatmining on windows I see several c++ crash messages pop up briefly as i'm closing the wallet. 

Still trying to get to debug it, my assumptionis the mining threads are not stopping before the rest of the client is shutting down.

Once I can find the smoking gun i'll let you know.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 28, 2018, 08:42:57 am
I tested from QT Wallet, Tools >> Debug Console >>> stop, no issues

Ran command line daemon, waited for blocks to load and verify, ./biblepay-cli stop, no issues


Thanks, I strongly believe I caused the stop issue when I was working on the podc unlock feature.  It had something to do with asking the headless user for the password modally.  I remember I moved that feature over to the the biblepay-cli tool (so it would be on demand not modal).

Im pretty sure that fixed the problem on that day, so Ill close the stop issue for now.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 28, 2018, 11:58:01 am
biblepaytest.conf
testnet=1
server=1
masternodeprivkey=xxx
masternode=0

-conf as a parameter to cdhoose different .conf file didn't work for me, but putting testnet=1 in biblepay.conf worked.

Using the -conf parameter is a way to get around adding all the other flags on boot (IE -testnet=1) etc.  But more importantly it allows you to set a different rpcport than your running prod instance.

Anyway if you put your biblepaytest.conf in your ~/.biblepaycore directory it should work. 
Start with

./biblepay-qt -conf=biblepaytest.conf

Also, you can put testnet=1 in your biblepaytest.conf, and leave it out of biblepay.conf. 

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 28, 2018, 12:07:29 pm
===
MINOR  UI:

- Move Proposals menu to a tab like Sanctuaries
---- Set Proposal List to be its own internal window
- Add Scrolling and Dragging abilities to Proposal List
---- or Find way to Shorten the information

===
QUESTION #1:
Should the Proposals Window also show other Governance information?

===
NICE TO HAVE:

--- Add Next Superblock Block Number (getgovernanceinfo: "nextsuperblock")
--- Add Superblock Budget Amount (getgovernanceinfo: "nextbudget")

--- Add Estimated Superblock Date/Time
(("nextsuperblock" - currentblock) * 7 min avg block time)

--- Add Visual Indicator or Sort/Separate Proposals based on if they are currently passing or not.
Example: https://dashvotetracker.com/

--- Add Full Budget Bar Chart (Total Budget and Currently Passing Budget)

===
HARDER:

--- Add ability to View Previous/Past Superblocks proposals/charts/info
--- Add Multi Bar Chart Split by Budget sections/types (IT, PR, P2P)

===
QUESTION #2:
- Add ability to Create Proposal to Wallet,
I assume we still need to wait on this?

============
IDEAS (NEED FEEDBACK):

- Pop Up / Notification
--- when New Proposal submitted?
--- Reminder to Vote on Proposals X days before end of cycle?
--- when Superblock is mined?
--- when Masternode leaves ENABLED state?

===
REFERENCES:

https://www.biblepay-central.org/en/proposals/
https://pool.biblepay.org/ >>> Governance >>> Proposal List

So taking a look at this list, 
on the minor UI:

- Move Proposals menu to a tab like Sanctuaries
---- Set Proposal List to be its own internal window
- Add Scrolling and Dragging abilities to Proposal List
---- or Find way to Shorten the information

we have Anton (Bezaleel) who volunteered to do this, so we are good here. 

On the Full Budget Bar Chart:
I have Bhavani working on our new Great Tribulation feature (thats the one where we have a Map of all Christians with longitude and latitude of the street corner they are near for privacy), so I think I can get Bhavani to add this Full Budget Bar Chart feature also.

On the Adding Proposals through the wallet itself:
I like the idea, it will help our decentralization.  Since I need to add some code to the pool to give it ability to pick up proposals entered through the core, I can take care of this feature. 


On everything else:  All I can suggest is if TheSnat wants to do them.  Snat, if you want to do the popups, there is a place in the code where we show a bible verse upon receiving BBP inbound.  You could potentially use that code to make these other pop ups, if you want.






Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: thesnat21 on June 28, 2018, 12:29:32 pm
On the Full Budget Bar Chart:
I have Bhavani working on our new Great Tribulation feature (thats the one where we have a Map of all Christians with longitude and latitude of the street corner they are near for privacy), so I think I can get Bhavani to add this Full Budget Bar Chart feature also.

I'm curious the logic behind this feature...  If in fact its during the great Tribulation, the last thing i'd want is to give away my position..
What is the source for this data?  (sounds interesting overall)

On everything else:  All I can suggest is if TheSnat wants to do them.  Snat, if you want to do the popups, there is a place in the code where we show a bible verse upon receiving BBP inbound.  You could potentially use that code to make these other pop ups, if you want.

Sure sounds good.

I think there should be a control option for the popups as well..  (ie simple way to turn them off in the gui)
Perhaps a new tab on the options screen?
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 28, 2018, 12:50:22 pm
I'm curious the logic behind this feature...  If in fact its during the great Tribulation, the last thing i'd want is to give away my position..
What is the source for this data?  (sounds interesting overall)

Sure sounds good.

I think there should be a control option for the popups as well..  (ie simple way to turn them off in the gui)
Perhaps a new tab on the options screen?


Well its sort of a multi-use feature.  Im thinking of having people store their nickname, long, lat (of street corner) and Christian testimony in the chain, and optionally e-mail address and BBP receive address (using a Contact Card - Add feature).  This would allow us to send/receive to each other by nickname or email.  And read others Christian testimonies.

The idea behind the great trib feature is if the rapture occurs, the idea is a user could go to our map and find areas of light (IE other biblepay users) to camp with. 

If you want to add a checkable option, sure, you could add it somewhere in the settings page, what about in Settings | Options | Wallet as another checkbox?  If you want a new tab go for it.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 28, 2018, 02:18:06 pm
Regarding the last outstanding test issues before go-live, I think we are now 95% there.

Recently 616 had a feature request in github suggesting we allow PODCH-heat mining to occur as long as the user has magnitude within the last 7 days, to keep them operating continiously.  This has been merged in the newest version, 1.1.3.5.  So that needs tested from the perspective that 1.1.3.5 can still heat mine without an error.

(I tested from the perspective to see if all CPIDs who have mag in the last 7 days are in my exec datalist search feature, and they are, so its relatively safe).

I believe we tested TheSnat's filters.  They look good.

On this next version, I enabled Proposals List UI in Prod so we can not only see the list of our 10 in prod, but lets test the filter to see if they dissapear after this superblock hits.

Regarding mature consensus, it passed test.  I also see we have been making quite a lot of PODC superblocks.

Ill take a look to see if we missed anything.

Windows is compiling.  Linux has been released to github.



Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: sunk818 on June 28, 2018, 11:50:26 pm
Also, you can put testnet=1 in your biblepaytest.conf, and leave it out of biblepay.conf. 

BTC Talk said you could run biblepay-qt as a portable app.
So, I have a folder called biblepay and another one for biblepaytest

I thought adding -testnet automatically uses different rpcport

Can someone send me 501k tBBP to yW3evG8mKvbb8oL6Tq9bys7KrxxadMuWMj ?

Thanks.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 29, 2018, 02:04:31 am

Can someone send me 501k tBBP to yW3evG8mKvbb8oL6Tq9bys7KrxxadMuWMj ?

Sent :)
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 29, 2018, 02:29:43 am
One of my testnet-wallets crashed with this message:

Quote
terminate called after throwing an instance of 'std::runtime_error'
  what():  CWallet::GenerateNewKey(): AddKey failed
Aborted (core dumped)

I don't think there is anything unusual in the debug.log.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 29, 2018, 03:36:56 pm
All,

1.1.3.6 is ready for testing for all platforms.

In this version we now have the ability to add proposals.
NOTE: You must have your wallet unlocked before submitting the proposal.
After submitting the proposal you must check back on the Proposal Add page after 6 confirms to see if it went in the chain.

Lets test that.

Lets also test the ability to heat mine in 1136.

We also moved the Proposal List to an integrated tab for more professionalism.
Additionally, we made the List update whenever you switch tabs and give it focus.

Hopefully this version will become the release candidate.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: thesnat21 on June 29, 2018, 04:10:46 pm
All,

1.1.3.6 is ready for testing for all platforms.

In this version we now have the ability to add proposals.
NOTE: You must have your wallet unlocked before submitting the proposal.
After submitting the proposal you must check back on the Proposal Add page after 6 confirms to see if it went in the chain.

Lets test that.

Lets also test the ability to heat mine in 1136.

We also moved the Proposal List to an integrated tab for more professionalism.
Additionally, we made the List update whenever you switch tabs and give it focus.

Hopefully this version will become the release candidate.

hmm, testing heat mining, did you change something there?

I noticed .3.6 seems to take longer to load the block index. (could be cause of the forks going on currently in prod).

I also had some crashes on the windows client on 3.6 while mining.  (go back to machine and the wallet is just gone heh)

edit: crashes seem to be because of the mining issues today, may not be related to the update. so far had 3.1,3.3, and 3.6 crash
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 29, 2018, 07:09:55 pm
hmm, testing heat mining, did you change something there?

I noticed .3.6 seems to take longer to load the block index. (could be cause of the forks going on currently in prod).

I also had some crashes on the windows client on 3.6 while mining.  (go back to machine and the wallet is just gone heh)

edit: crashes seem to be because of the mining issues today, may not be related to the update. so far had 3.1,3.3, and 3.6 crash

Hmm lets test everything in testnet today; not a good day to intermingle testing with prod.

No, doesn't take longer to load the block index.  Lets try to only post a statement if you KNOW its true.  Meaning that you ran a baseline and have something to compare to.  And you know your hard drive cache was empty both times.

Hmm, shouldnt have any crashes if you are mining on one thread.  What are you mining with, 60 threads?  And what OS?  It would be helpful to post the tail of the log (in a code snippet of course) if you encounter a crash.  Try to reproduce it on linux with valgrind then you can give me the line #.






Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: thesnat21 on June 29, 2018, 10:28:11 pm
No, doesn't take longer to load the block index.  Lets try to only post a statement if you KNOW its true.  Meaning that you ran a baseline and have something to compare to.  And you know your hard drive cache was empty both times.

Hmm, shouldnt have any crashes if you are mining on one thread.  What are you mining with, 60 threads?  And what OS?  It would be helpful to post the tail of the log (in a code snippet of course) if you encounter a crash.  Try to reproduce it on linux with valgrind then you can give me the line #.
Loading of the index, was noticeably longer on several machines in prod(I'm talking 30sec to 5+min difference) I suspect this is due to the current issue and all the orphan blocks.   


as for mining,  I have several machines mining 4 cores...  windows of course so no valgrind.  I won't be around tomorrow, but i'll see if i can get logs.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 30, 2018, 08:39:08 am
I'm creating some proposals from the wallet now. Am I correct in asserting that the fee for the proposals are paid right from the wallet (the fee seems to be 5 BBP now, but that's probably because we are in testnet)?

Frankly, I think that is amazing!
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 30, 2018, 08:47:35 am
I'm creating some proposals from the wallet now. Am I correct in asserting that the fee for the proposals are paid right from the wallet (the fee seems to be 5 BBP now, but that's probably because we are in testnet)?

Frankly, I think that is amazing!
Yes, the reason its currently 5 bbp, is we went live with that value last year.  However I feel that will end up eventually being abused (as it was in the pool at first), and also, we have been charging 2500 historically in the pool, so I made a transition point as of August 1 to switch over to 2500 BBP for the collateral fee.  So in prod, it will temporarily be 5 also until that date.

Im going to look at any outstanding test cases; we really need to ramp up testing this weekend in order to try to get a version out soon; we cant notify the exchanges of a coming mandatory unless we are sure of a release date.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 30, 2018, 08:48:56 am
Loading of the index, was noticeably longer on several machines in prod(I'm talking 30sec to 5+min difference) I suspect this is due to the current issue and all the orphan blocks.   


as for mining,  I have several machines mining 4 cores...  windows of course so no valgrind.  I won't be around tomorrow, but i'll see if i can get logs.

Testing this morning on one home linux and one VM block index seems to load fast, I think it might have been an anomaly.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: jaapgvk on June 30, 2018, 09:02:51 am
Yes, the reason its currently 5 bbp, is we went live with that value last year.  However I feel that will end up eventually being abused (as it was in the pool at first), and also, we have been charging 2500 historically in the pool, so I made a transition point as of August 1 to switch over to 2500 BBP for the collateral fee.  So in prod, it will temporarily be 5 also until that date.

Im going to look at any outstanding test cases; we really need to ramp up testing this weekend in order to try to get a version out soon; we cant notify the exchanges of a coming mandatory unless we are sure of a release date.

I feel that the 5 BBP will definitely make it easy to abuse the function. 2500BBP I think works well, as you can ask the 2500BBP back in your proposal. If you have a good proposal you have nothing to fear.

This Sunday will be my 'BiblePay day', so I will test a lot and try a lot. A tiny thing that I have for now is that you can still also access the proposal-tab from the top menu. That's probably redundant now.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on June 30, 2018, 09:44:04 am
I feel that the 5 BBP will definitely make it easy to abuse the function. 2500BBP I think works well, as you can ask the 2500BBP back in your proposal. If you have a good proposal you have nothing to fear.

This Sunday will be my 'BiblePay day', so I will test a lot and try a lot. A tiny thing that I have for now is that you can still also access the proposal-tab from the top menu. That's probably redundant now.

Yes, Im in total agreement, and I have it set to where we can move the Proposal-Add to the top menu, and just see the Proposals from the left menu; I figured I would leave it like this until Anton gets it as he is working on some things that affect the menu right now.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on June 30, 2018, 08:36:41 pm
Updated to v1.1.3.6

New tabbed Proposals List
Proposal Add
and "exec totalrac"
 are AWESOME!
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on July 01, 2018, 10:22:43 am
Hey, sorry TheSnat, I finally accidentally encountered the long load time for the block index on one of my windows machines (IE > 5 mins, compared to normally 20 seconds).

I think this has something to do with the loading of the prayers in the background...  It makes me nervous; will need to look into it today.

At the worst, I feel its safer if we let the prayers load serially like we used to-and delay the start by 10 seconds... Ill take a look.  I hate to delay the release much longer.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: noxpost on July 01, 2018, 12:48:19 pm
Quick comment/note about the new proposal view (which is really nice to see!) - it would be great if the spacing on the amounts was done the same way as in the rest of the wallet.

For instance, instead of:
8000000

It read:
8 000 000

Not a major thing by any means, but something to consider for a later leisure.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: thesnat21 on July 01, 2018, 07:29:08 pm
Testing this morning on one home linux and one VM block index seems to load fast, I think it might have been an anomaly.

I deleted and re-created the chain and let it re-sync.

I think it was due to all the forks and the client processing through them(memory was clocking in at 2-2.5gb on a few machines that were online in prod throughout the last few days)

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: thesnat21 on July 01, 2018, 07:34:20 pm
Hey, sorry TheSnat, I finally accidentally encountered the long load time for the block index on one of my windows machines (IE > 5 mins, compared to normally 20 seconds).

I think this has something to do with the loading of the prayers in the background...  It makes me nervous; will need to look into it today.

At the worst, I feel its safer if we let the prayers load serially like we used to-and delay the start by 10 seconds... Ill take a look.  I hate to delay the release much longer.

I appreciate the apology, I tend to run things harder than most :)
I posted separately I think I understand why my clients were acting up,  (mining slowed to 1/4 the speed with the large mem usage as well)

I don't know if it has been resolved, but there was an issue in the older clients if you delete the block data, and let the client re-sync it won't pick up the CPID for mining until you restart. Easy workaround i'll see if it still happens here. (Edit: still there i'll throw it as an issue on the github later)


I started working on the UI notifications, 
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on July 02, 2018, 07:29:47 am
Quick comment/note about the new proposal view (which is really nice to see!) - it would be great if the spacing on the amounts was done the same way as in the rest of the wallet.

For instance, instead of:
8000000

It read:
8 000 000

Not a major thing by any means, but something to consider for a later leisure.

Thanks for the heads up, Yes, we'll add this to a coming leisure.
If you dont see it in the next version after the mandatory please add an issue to github.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on July 02, 2018, 07:32:21 am
So here is a recap on where we are:

I'm nervous about the background prayers, so I put it back in the foreground serially (during load).  I tested this last night.  1.1.3.7 is checked in for linux and now compiling for windows.

As far as test cases, I did test the paid-proposals filter in prod and it passed.  The two proposals left in Prod are the ones we voted down to enter the replacement proposals.  They fall off after 31 days (since the entry date).

As far as test case coverage, to my knowledge everything else passed.

If anyone has any concerns please apprise us.



EDIT:  Windows version is out also.


Today,  I will consolidate all of our release notes together for the mandatory version and we can assess if we are ready for release.


Please take 1.1.3.7 for a spin to ensure nothing is awry.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on July 02, 2018, 09:12:27 pm
Updated to v1.1.3.7

left it running for a few hours, mnsync status  was stuck syncing, I was worried I was on a fork,
so I did a clean and reindex, mnsync status is still stuck syncing,
my masternode shows as Missing,
so I enabled it again and its in PRE_ENABLED state

getblockhash 46512
6268ef875***ea90589
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on July 03, 2018, 02:42:26 am
Updated to v1.1.3.7

left it running for a few hours, mnsync status  was stuck syncing, I was worried I was on a fork,
so I did a clean and reindex, mnsync status is still stuck syncing,
my masternode shows as Missing,
so I enabled it again and its in PRE_ENABLED state

getblockhash 46512
6268ef875***ea90589

My hash matches.. let me do some sanc testing to make sure we are emitting PODC superblocks.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on July 03, 2018, 04:21:08 am
TheSnat, could you please see if you introduced this bug with the PODC filters?

https://github.com/biblepay/biblepay/issues/28

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on July 03, 2018, 07:25:23 am
My debug.log got filled up, I think its from leaving debug=true and debugmaster=true on for all this time, saved last 100 lines of log and removed it and commented out the config options
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: thesnat21 on July 03, 2018, 08:58:05 am
TheSnat, could you please see if you introduced this bug with the PODC filters?

https://github.com/biblepay/biblepay/issues/28

Oddly I'm not seeing this on all my wallets, only a few i'm trying to figure out why.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on July 03, 2018, 11:25:02 am
My debug.log got filled up, I think its from leaving debug=true and debugmaster=true on for all this time, saved last 100 lines of log and removed it and commented out the config options

Only in testnet, or in prod?

EDIT: Ill run two nodes in prod on 1138 and see if something should be done if so we can rerelease a patch.

EDIT:  Is there anything in your saved file we should remove?
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: togoshigekata on July 03, 2018, 11:53:32 am
This was in testnet, on v1.1.3.7.
Looks like its up to 21MB already hmmm

Im seeing a ton of this message:

ProcessBlockFound: Generated: ######
CPID has solved prior blocks. Contextual check block failed. CPID ######### ERROR: ProcessnewBlock: AcceptBlock FAILED
PrcoessBlockFound -- ProcessNewBlock() failed, block not accepeted
CBlock(hash= **** CTransaction ** CtxIn ** CTxOut

Maybe its because of too small amount of miners in testnet?

Hmmm I accidentally put a $ symbol in front of debugmaster=true instead of a hashtag to turn it off, I wonder what that did
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on July 03, 2018, 12:23:05 pm
This was in testnet, on v1.1.3.7.
Looks like its up to 21MB already hmmm

Im seeing a ton of this message:

ProcessBlockFound: Generated: ######
CPID has solved prior blocks. Contextual check block failed. CPID ######### ERROR: ProcessnewBlock: AcceptBlock FAILED
PrcoessBlockFound -- ProcessNewBlock() failed, block not accepeted
CBlock(hash= **** CTransaction ** CtxIn ** CTxOut

Maybe its because of too small amount of miners in testnet?

Hmmm I accidentally put a $ symbol in front of debugmaster=true instead of a hashtag to turn it off, I wonder what that did

Try removing or renaming debugmaster=true.  The parser probably interpreted that wrong.

Im using 231K on linux and 269K on windows in Prod on 1138 after running for a half hour and being fully synced.

21 Meg means something is really wrong on the node.  Could be those settings...

My log is clean now but I did release a small patch, but it only removed 2 messages.

Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: thesnat21 on July 04, 2018, 09:18:22 am
submitted fix for the recent transaction issue to github.
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on July 05, 2018, 09:06:52 am
submitted fix for the recent transaction issue to github.

Thanks, will look into this asap!

Been making great progress on stratis, need to put this down...


Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Dynaxius on August 14, 2018, 02:57:03 pm
Hi, Rob. Is the current plan for the upcoming BBP migration involving Stratis to create a fork of Stratis, or are you hoping to leverage the new sidechain tech they have released in recent months and actually deploy BBP beneath the Stratis Blockchain?

https://academy.stratisplatform.com/Sidechains/sidechains-introduction.html
Title: Re: Testnet June 2018 Mandatory Upgrade Testing Thread
Post by: Rob Andrews on September 07, 2018, 07:42:20 pm
Hi, Rob. Is the current plan for the upcoming BBP migration involving Stratis to create a fork of Stratis, or are you hoping to leverage the new sidechain tech they have released in recent months and actually deploy BBP beneath the Stratis Blockchain?

https://academy.stratisplatform.com/Sidechains/sidechains-introduction.html

We ported our POBH and kjv.cpp into stratis, so not sidechain, but actual real chain, and full compatibility with biblepay-qt production.  Except we haven't started porting the governance module yet, so you cant have a stratis Sanctuary (yet).