News:

F7000 COMING SOON!

Main Menu

Testnet - Test Proof of Giving

Started by Rob Andrews, December 06, 2018, 01:00:46 PM

Previous topic - Next topic

sunk818

So, will there be a GUI checkbox for participating in PoG?
Check on = tithe=1
Check off = tithe=0
BH6oxjLkyz3z8FYpvU3ZR7PTZ31Xt9DkXZ

sunk818

Can anyone test where tithe=6 (try to donate every 6 minutes).

I keep getting the QT wallet to crash.

2018-12-26 19:55:22 UpdateTip: new best=007420004458c7b618d772bf74067319f1a40381db7435f377c2c40d5d9dea84  height=98787  log2_work=44.53204  tx=106806  date=2018-12-26 19:55:18 progress=1.000000  cache=0.0MiB(39tx)
2018-12-26 19:55:22 ProcessNewBlock : ACCEPTED
2018-12-26 19:56:19 UpdateTip: new best=685640d2b4dc9f558f9c229abe1a4a81a247f7466c13e0f511297aabf3734826  height=98788  log2_work=44.532056  tx=106807  date=2018-12-26 19:56:17 progress=1.000000  cache=0.0MiB(40tx)
2018-12-26 19:56:19 ProcessNewBlock : ACCEPTED
2018-12-26 19:57:14 UpdateTip: new best=7883f86caa1c59bcee34abcb833a39831c83a22fbff9c5e343811b66653b4adb  height=98789  log2_work=44.532071  tx=106808  date=2018-12-26 19:57:13 progress=1.000000  cache=0.0MiB(41tx)
2018-12-26 19:57:14 ProcessNewBlock : ACCEPTED
2018-12-26 19:58:07 UpdateTip: new best=71407a035ae90859d80d46944d5cf59cc0c9be16c382074cb0792f7c06b97e75  height=98790  log2_work=44.532086  tx=106809  date=2018-12-26 19:58:01 progress=0.999999  cache=0.0MiB(42tx)
2018-12-26 19:58:07 ProcessNewBlock : ACCEPTED
2018-12-26 19:58:25  CreateTransaction::Requiring specific coin age 4.440000 and coin amount 1851 2018-12-26 20:00:37


BH6oxjLkyz3z8FYpvU3ZR7PTZ31Xt9DkXZ

MIP

Quote from: Rob Andrews on December 24, 2018, 08:43:37 PM
1.1.7.2b
Mandatory Upgrade for TestNet


Ready for MacOS and testnet PPAs are building now

sunk818

Can someone give me the addnodes again to put in the conf?

I tried

addnode=testnet.biblepay.org
addnode=node.biblepay.org

so far, I'm getting just solo mining blocks and can get any other peer.
BH6oxjLkyz3z8FYpvU3ZR7PTZ31Xt9DkXZ

Rob Andrews

Ive had my testnet nodes down for 2 1/2 days - I just made an attempt at resyncing - anyone up to provide a blockhash?


Rob Andrews

Quote from: thesnat21 on December 27, 2018, 06:04:05 AM
I'm the only one showing in the pool in testnet,  but I don't seem to be getting any rewards from the pool (just the mining rewards)

Yeah, if you are by yourself, your node is probably mining every block, and also paying you 100% of the tier payment block also.  You would have to pull up your txid and type 'getrawtransaction txid 1' to see it.




sunk818

Someone is running 1173 is that you Rob? I finally got peers. One test node seems to be okay but other two are just solo mining blocks with no peers
BH6oxjLkyz3z8FYpvU3ZR7PTZ31Xt9DkXZ

Rob Andrews

Quote from: sunk818 on December 28, 2018, 10:51:35 PM
Someone is running 1173 is that you Rob? I finally got peers. One test node seems to be okay but other two are just solo mining blocks with no peers
Yeah, 1.1.7.3 is why Ive been MIA for 2 1/2 days, yes its me.  It does not have any POG changes in it however.

Anyway, I see the problem in general in testnet.  When we have less than 3 nodes with a consensus, the nodes arent trusting each other to download blocks.  The other problem is chainstate contains a few too many chain tip problems (IE some blocks appear to be marked as bad from all these upgrades).

What we need to do is restart with -reindex (but not by deleting the chainstate and the blocks) and let it resync - that clears all the boolean masks on each block and then we should trust each other again.

Let me post a blockhash, I just reindexed 3 and they seem to be syncing up properly now.



getblockhash 96825


cf0e35c7142f305cfa3ff8efc3740b74d42e550d4d66975fc1207762a73ac566



Rob Andrews

Im synced on all my nodes now (after -reindex worked), but dont see TheSnat or anyone else yet - you guys are probably on all different chains.

Once we all get on the same chain Ill check the logs after that point.


Rob Andrews

I havent seen any crashing...

Just an FYI, a crash means the program actually ended (IE segfaulted).

If this happens please run it in valgrind.


Rob Andrews

Quote from: thesnat21 on December 29, 2018, 07:01:10 PM
I had 2 clients with hash of cd92bf4727388a839ef25c8dfc33879cebd034a7863fcfd32a5a09222a9d96c6 for your block.

trying the reindex

Yeah I saw that we had one fork; but I also saw looking at peers we had 5 not reindex and 5 indexed so its a crapshoot on what was going on - lets see if after you reindex we take another look and see if we can have a consistent 24 hours.

It should be apparent if pog diff stays relatively smooth (IE 20K+).  However I noticed on my two whale boxes, Im running out of tithe money (I have 25 tithes left at this diff level on each box).


Rob Andrews

Quote from: Rob Andrews on December 29, 2018, 07:13:45 PM
Yeah I saw that we had one fork; but I also saw looking at peers we had 5 not reindex and 5 indexed so its a crapshoot on what was going on - lets see if after you reindex we take another look and see if we can have a consistent 24 hours.

It should be apparent if pog diff stays relatively smooth (IE 20K+).  However I noticed on my two whale boxes, Im running out of tithe money (I have 25 tithes left at this diff level on each box).

Actually to elaborate when I first reindexed I had that hash, then my 3 nodes reorged and I did start getting Your hash (cd9) on all nodes.  Just to start this process over again, here is my new hash:


19:16:14

getblockhash 97175


19:16:14

bd0a9e17647121f030d406e05458894ef595127a64340b8d2defb05f82c3eab3


Pog Diff is around 20K.


Rob Andrews

Quote from: thesnat21 on December 29, 2018, 07:31:04 PM
Got that hash on the block explorer machine..

The other 2 crashed,  this is debug log from one, will grab the other if it does.  (this is during the reindex)


2018-12-30 01:25:47  Finished Loading Block Index 1546133147.000000 LoadBlockIndexDB: hashBestChain=698ac2d570dd63a89758c396681ca3ae8cab5f14323384d28959a55fcd878922 height=54303 date=2018-09-01 20:09:11 progress=0.163178
2018-12-30 01:25:47 init message: Verifying blocks...
2018-12-30 01:25:47 Verifying last 288 blocks at level 3
2018-12-30 01:25:48 No coin database inconsistencies in last 289 blocks (352 transactions)
2018-12-30 01:25:48  block index           13065ms
2018-12-30 01:25:48 init message: Loading wallet...
2018-12-30 01:25:48 nKeysLeftSinceAutoBackup: 1000
2018-12-30 01:25:48 nFileVersion = 1010702
2018-12-30 01:25:48 Keys: 2135 plaintext, 0 encrypted, 2135 w/ metadata, 2135 total
2018-12-30 01:25:49  wallet                  328ms
2018-12-30 01:25:49 init message: Activating best chain...
2018-12-30 01:25:49 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large at CBlockDiskPos(nFile=0, nPos=25459402), Context CONNECTTIP
2018-12-30 01:25:49 *** Failed to read block



Size too large means the block index is > 32 mb, meaning the block file is corrupted.  In this case you must kill the files and re-sync the chain.

This is a normal assert they put in for a corruption sanity check.

Rob Andrews

Good news, on my dev node running Pog I finally encountered a crash.  Btw, even though I was not running valgrind and the log is not useful, if you ever see a message printed on the console during the crash, that is useful.

In this case it was "An exception of UniValue was thrown and terminate called". 

Im running it in valgrind now - lets hope this is the same thing Sun reported.

If anyone else has crashed please run in valgrind - lets find the line #.


Rob Andrews

Quote from: Rob Andrews on December 30, 2018, 10:46:10 AM
Good news, on my dev node running Pog I finally encountered a crash.  Btw, even though I was not running valgrind and the log is not useful, if you ever see a message printed on the console during the crash, that is useful.

In this case it was "An exception of UniValue was thrown and terminate called". 

Im running it in valgrind now - lets hope this is the same thing Sun reported.

If anyone else has crashed please run in valgrind - lets find the line #.

TheSnat found it first in valgrind.  The great news is this appears to be the same error (during mining) affecting all 3 of us.

The fix is completed and the new version is being compiled now...