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

[MIP]

1.4.2.0-Mandatory Upgrade for TestNet

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

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

Daemon/cli for Linux amd64, available here
https://www.biblepay.org/biblepayd-1.4.2.0-x86_64-pc-linux-gnu.tar.gz

And MacOS QT version here
https://www.biblepay.org/biblepaycore-testnet.dmg

[Rob Andrews]

1.4.2.1b-Mandatory Upgrade for TestNet

- Improve anti-fork business logic
- Remove ABN error log spam
- Add Church Tithing subsystem

[togoshigekata]

Upgraded to v1.4.2.1b

Code Select Expand

./biblepay-cli getblockhash 48789
f8359bfbfa16f3faa02eaf6bab8c9d5143962ec24e3c99953e14f0a709d670a9

[uptimeminer]

getblockhash 48789
f8359bfbfa16f3faa02eaf6bab8c9d5143962ec24e3c99953e14f0a709d670a9

Agree....Just updated to 1.4.2.1b

[Rob Andrews]

getblockhash 48789
f8359bfbfa16f3faa02eaf6bab8c9d5143962ec24e3c99953e14f0a709d670a9

Agree....Just updated to 1.4.2.1b

Agreed.

[Rob Andrews]

Ok everyone, I was waiting for the code to stabilize and diff to increase and the height to pass a few hundred past all our changes before I started flipping switches.

It appears we are all staying in sync (although diff is only .50 - I think that is because we are mining with low power machines) so that should be fine.  My sanc#2 has 21 connections so that is good (none are banned).

In the last version, we fixed the ABN (anti-bot-net feature) to stop throwing errors in the log.  As of 44350, we now enforce the low abn height rule (minimum 1000 abn weight required per block).

So lets start by testing this.  Im going to look in the logs, and grep for "ERROR" and does not meet anti-bot-net-minimum required guidelines.  We should no longer see this in the log.  Then we will do a getblock 50560, 50561, ... etc, and check the anti-bot-net weight on each block- it should be > 1000.

Ok, Test #1 passed:  We no longer have this anti-bot-net ERROR in the log after the cutover height.  The only ERROR I see now is 'superblock has no recipients' at 50225 - thats normal. 

[Rob Andrews]

I just enabled our antigpu feature starting @ 50560.  This is similar to the rule we had in PODC, where a CPID could not solve any block within a 4 consecutive block lookback in prod (and 1 block in testnet).  So in Evo, this means a distinct CPK cannot solve more than 1 block per 1 block lookback in test (4 blocks in prod).

So to test this, we will do a getblock 50560, look for the CPK field, and ensure it is changing each consecutive block forward) - no back to back solutions in testnet.

[Rob Andrews]

I don't see any other cold sancs (other than my 3 in testnet).  It's going to be hard to perform quality testing with just me on board.
Is anyone planning on starting a sanc?

Im thinking about testing dip3 sancs tomorrow.

(We need to test upgrading a legacy sanc to a deterministic sanc).

[togoshigekata]

Im attempting to setup a masternode now

I was trying to do it by command line but sent coins to wrong address,
so now I installed lubuntu and am trying again

=

These are my old notes:
https://forum.biblepay.org/index.php?topic=190.msg3701#msg3701
https://forum.biblepay.org/index.php?topic=108.msg1444#msg1444

Attempt to use VNC:
https://forum.biblepay.org/index.php?topic=244.msg4525#msg4525
https://forum.biblepay.org/index.php?topic=244.msg4523#msg4523

Masternode guide:
http://wiki.biblepay.org/Create_Sanctuary_2

=

I get nothing back when typing masternode outputs,
then I tried checking the balance of the address (getbalance) I sent to and it was 0,
I turned on coin control and checked, and it seems almost all the coins are in a "(change)" address

Ill try again

I also noticed there was an additional 10% Foundation tithe added on to the initial transaction, even though I didnt click any checkboxes in the GUI

[togoshigekata]

Hmm it happened again, got screenshots:
https://imgur.com/a/F882yIp
looks like coins get split up into the "CHRISTIAN-PUBLIC-KEY" address automatically

[jaapgvk]

I've been trying to start a Sanctuary, but I can't seem to sync my wallets properly

[togoshigekata]

I've been trying to start a Sanctuary, but I can't seem to sync my wallets properly

rm blocks -r
rm chainstate -r
rm evodb -r
rm SAN -R
rm gov*
rm mnc*
rm mnp*

I just delete everything other than the wallet.dat, backups folder, biblepay.conf, peers list and masternode.conf

And then I do a ./biblepayd -dameon -reindex

[orbis]

Hmm it happened again, got screenshots:
https://imgur.com/a/F882yIp
looks like coins get split up into the "CHRISTIAN-PUBLIC-KEY" address automatically

Togo, there has to be sanctuary lockup collateral to 4,500,001, not for 4,500,000. Or am I wrong?
Maybe that is the problem.

[orbis]

Hi all,
finally after 1421b update I was back on chain.
I had really big problem with ABN feature and I wasn't be able to sync.
I've tried it for few days and I spent many hours with clean install and resync.
Mostly it tooks me more than 3-4 hours to reach last block, then ABN error stops me and I started whole process again.
I was really disappointed and upset
Yesterday I was finally synced and it looks good, but then I stopped my wallet and today it wont synced again
Today there is problem with antigpu:

Code Select Expand

2019-04-28 09:12:54  AntiGPU i 0.000000, CPK ygjQUutb2MnpVJKyjQ3mTne4rg71FFPcwg      ERROR: TestBlockValidity: Consensus::ContextualCheckBlock:  (code 0)

I'm stucked at block 50706, So I need to make resync again
That lead me to the question of whether you are thinking about creating "bootstrap.dat" copy on your servers to sync faster.
Others coins has this like common "service".

[orbis]

And there is also ABN error again:

Code Select Expand

2019-04-28 09:34:09
CreateNewBlock::Unable to add ABN because Sorry, must be unlocked to create an anti-botnet transaction.antibotnetsignature failed on tx baddb353bac2364d696ad7749c0237092d3e0409ee9bafd5c983144216d351dc with purported coin-age of 0.000000
2019-04-28 09:34:09 ERROR: TestBlockValidity: Consensus::ContextualCheckBlock:  (code 0)