search

myriadteam / myriadcoin

Myriadcoin cryptocurrency - Repository for community driven development
http://www.myriadcoin.org
MIT License
47 stars 16 forks source link

testnet #3

Closed cryptapus closed 8 years ago

cryptapus commented 8 years ago

Was going to attempt to test mining on testnet, but it didn't seem to connect, bad POW at block 151 on my testnet nodes, here is the debug.log (may not be very important in the grand scheme of things):

2016-03-02 22:10:38 Myriad version v0.11.2.0-a195a52-rc1 (2016-03-02 19:40:37 +1300) 2016-03-02 22:10:38 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015 2016-03-02 22:10:38 Using BerkeleyDB version Berkeley DB 5.3.28: (September 9, 2013) 2016-03-02 22:10:38 Default data directory /home/xxx/.myriadcoin 2016-03-02 22:10:38 Using data directory /home/xxx/.myriadcoin.testnet2/testnet3 2016-03-02 22:10:38 Using config file /home/xxx/.myriadcoin.testnet2/testnet/myriadcoin.conf 2016-03-02 22:10:38 Using at most 125 connections (65536 file descriptors available) 2016-03-02 22:10:38 Using 8 threads for script verification 2016-03-02 22:10:38 scheduler thread start 2016-03-02 22:10:38 Binding RPC on address :: port 22889 (IPv4+IPv6 bind any: 1) 2016-03-02 22:10:38 Using wallet wallet.dat 2016-03-02 22:10:38 init message: Verifying wallet... 2016-03-02 22:10:38 CDBEnv::Open: LogDir=/home/xxx/.myriadcoin.testnet2/testnet3/database ErrorFile=/home/xxx/.myriadcoin.testnet2/testnet3/db.log 2016-03-02 22:10:38 Bound to [::]:22888 2016-03-02 22:10:38 Bound to 0.0.0.0:22888 2016-03-02 22:10:38 Cache configuration: 2016-03-02 22:10:38 * Using 12.5MiB for block index database 2016-03-02 22:10:38 * Using 29.9MiB for chain state database 2016-03-02 22:10:38 * Using 57.6MiB for in-memory UTXO set 2016-03-02 22:10:38 init message: Loading block index... 2016-03-02 22:10:38 Opening LevelDB in /home/xxx/.myriadcoin.testnet2/testnet3/blocks/index 2016-03-02 22:10:38 Opened LevelDB successfully 2016-03-02 22:10:38 Opening LevelDB in /home/xxx/.myriadcoin.testnet2/testnet3/chainstate 2016-03-02 22:10:38 Opened LevelDB successfully 2016-03-02 22:10:38 LoadBlockIndexDB: last block file = 0 2016-03-02 22:10:38 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=278, heights=0...0, time=2014-02-20...2014-02-20) 2016-03-02 22:10:38 Checking all blk files are present... 2016-03-02 22:10:38 LoadBlockIndexDB: transaction index enabled 2016-03-02 22:10:38 LoadBlockIndexDB: hashBestChain=0000017ce2a79c8bddafbbe47c004aa92b20678c354b34085f62b762084b9788 height=0 date=2014-02-20 06:06:33 progress=0.000027 2016-03-02 22:10:38 init message: Verifying blocks... 2016-03-02 22:10:38 block index 26ms 2016-03-02 22:10:38 init message: Loading wallet... 2016-03-02 22:10:38 nFileVersion = 110200 2016-03-02 22:10:38 Keys: 102 plaintext, 0 encrypted, 102 w/ metadata, 102 total 2016-03-02 22:10:38 wallet 6ms 2016-03-02 22:10:38 init message: Activating best chain... 2016-03-02 22:10:38 mapBlockIndex.size() = 151 2016-03-02 22:10:38 nBestHeight = 0 2016-03-02 22:10:38 setKeyPool.size() = 101 2016-03-02 22:10:38 mapWallet.size() = 0 2016-03-02 22:10:38 mapAddressBook.size() = 1 2016-03-02 22:10:38 init message: Loading addresses... 2016-03-02 22:10:38 Loaded 0 addresses from peers.dat 0ms 2016-03-02 22:10:38 dnsseed thread start 2016-03-02 22:10:38 Loading addresses from DNS seeds (could take a while) 2016-03-02 22:10:38 net thread start 2016-03-02 22:10:38 opencon thread start 2016-03-02 22:10:38 addcon thread start 2016-03-02 22:10:38 msghand thread start 2016-03-02 22:10:38 init message: Done loading 2016-03-02 22:10:38 0 addresses found from DNS seeds 2016-03-02 22:10:38 dnsseed thread exit 2016-03-02 22:10:38 GUI: PaymentServer::LoadRootCAs: Loaded 174 root certificates 2016-03-02 22:10:38 receive version message: /Satoshi:0.9.2.16/: version 70003, blocks=384, us=75.19.27.26:60041, peer=1 2016-03-02 22:10:38 Added time data, samples 2, offset +0 (+0 minutes) 2016-03-02 22:10:38 ERROR: ContextualCheckBlockHeader: incorrect proof of work at height 151 2016-03-02 22:10:38 Misbehaving: 75.19.27.27:20888 (0 -> 100) BAN THRESHOLD EXCEEDED 2016-03-02 22:10:38 ERROR: invalid header received 2016-03-02 22:10:38 ProcessMessages(headers, 19036 bytes) FAILED peer=1 2016-03-02 22:10:39 receive version message: /Satoshi:0.9.2.16/: version 70003, blocks=384, us=75.19.27.26:41673, peer=2 2016-03-02 22:10:39 Added time data, samples 3, offset +0 (+0 minutes) 2016-03-02 22:10:39 ERROR: ContextualCheckBlockHeader: incorrect proof of work at height 151 2016-03-02 22:10:39 Misbehaving: 75.19.27.28:20888 (0 -> 100) BAN THRESHOLD EXCEEDED 2016-03-02 22:10:39 ERROR: invalid header received 2016-03-02 22:10:39 ProcessMessages(headers, 19036 bytes) FAILED peer=2 2016-03-02 22:11:39 Adding fixed seed nodes as DNS doesn't seem to be available. 2016-03-02 22:11:55 scheduler thread interrupt 2016-03-02 22:11:55 addcon thread interrupt 2016-03-02 22:11:55 opencon thread interrupt 2016-03-02 22:11:55 msghand thread interrupt 2016-03-02 22:11:55 net thread interrupt 2016-03-02 22:11:55 Shutdown: In progress... 2016-03-02 22:11:55 StopNode() 2016-03-02 22:11:55 Shutdown: done

nzsquirrell commented 8 years ago

ah yes, that should be on the known issues list, the parameters for testnet (hard forks etc) in no way match what was in 0.9.2.16/17. there would need to be quite a few changes to chainparams.cpp under the testnet section to bring them in line.

cryptapus commented 8 years ago

understood, perhaps I'll submit a pull request when I have some time...

nzsquirrell commented 8 years ago

fixed finally in commit 9b7f415

Please test and advise. my two testnet nodes (one is 0.11.2 the other 0.9.2.16) are up and talking to yours.

cryptapus commented 8 years ago

I see your nodes and have connections, thanks.

Works good, was able to mine all 5 algos (no aux-pow)...

so if I understand this correctly:

consensus.nStartAuxPow = 1402000; consensus.nBlockTimeWarpPreventStart1 = 740500; // block where time warp 1 prevention starts consensus.nBlockTimeWarpPreventStart2 = 766000; // block where time warp 2 prevention starts consensus.nBlockTimeWarpPreventStart3 = 1048320; // block where time warp 3 prevention starts

are quite far down the chain, I would guess testnet would be more useful if these started earlier? Maybe that doesn't jive with 0.9.16 testnet... but I don't have a longer testnet to use... Or maybe a plan to reset the testnet to start those earlier at a later date?

nzsquirrell commented 8 years ago

Yes, the settings for testnet currently are not good. This is due to what testing 8bitcoder was doing when introducing the changes to block time etc. I would suggest we release a 0.9.2.18 version as a maintenance release, which contains changes to testnet to make all of the above more sane for testnet purposes. then we make the same changes in 0.11.2 when it releases.

having a stable testnet would be beneficial, not only for other services, but also for the core wallet code. there's some things i want to try using the consensus machanisms, and testnet is the place for them.

cryptapus commented 8 years ago

Understood, good idea. I'll take a look at that when time permits.

Well done and Thanks!