• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

V12 Testing Thread

moli said:
UdjinM6 - When clicking the button "Start Darksend Mixing" there's a kinda like "freezing" moment for about 30 seconds which can make users wonder "what is this? did i start it? is it going to start?.... " So I'm thinking maybe you can put in a message right after the click, something like "Standby... Preparing a fun and exciting Darksend roller coaster for you..." ....Something to help users know what to anticipate and not wondering...

What do you think? :grin:
Click to expand...
Yeah, smth like this could be a solution... but I'm trying to figure out why it freeze like that at all - I first though it was because of creation of denominations and all that kind off stuff but it seems like it ignores (?) balance cache and that impacts the most. Or we clear it when we shouldn't somehow, not sure... can't find it yet.
 
v0.12.0.41-06fcb73 (i know there is a newer version with an added checkpoint but i dont think i need that checkpoint at the moment as my wallets are running very stable and in sync with 06fcb73 already)

* Darksend mixing goes fast and all transactions get confirmed fast
* All my 6 Windows 10 wallets stay in full sync during mixing
* no wallet crashes witnessed so far

I have got to get some sleep and so does my PC :rolleyes: so i will see you guys tomorrow, happy testing.
 
Dash - Reinventing Cryptocurrency

https://github.com/dashpay/dash/tree/v0.12.0.x


upload_2015-8-10_19-23-0.png
 
 
eduffield - this is win v0.12.0.41-06fcb73. I meant to report a masternode wallet that got stuck a few hours ago but forgot. It has these lines in the debug log:

Code: 
2015-08-11 01:47:57 UpdateTip: new best=0000001260da7cf03a76793806870c5fe721ae76e1f65ecb1eb9e5688afa4bf1  height=82394  log2_work=43.454153  tx=108340  date=2015-08-11 01:26:13 progress=0.999930  cache=741
2015-08-11 01:47:57 CheckForkWarningConditions: Warning: Found invalid chain at least ~6 blocks longer than our best chain.
Chain state database corruption likely.
2015-08-11 01:47:57 UpdateTip: new best=0000003c85613ecccc93530da231f813c5cc6c6c487990277da786d86accf796  height=82395  log2_work=43.454156  tx=108341  date=2015-08-11 01:27:10 progress=0.999933  cache=742
2015-08-11 01:47:57 CheckForkWarningConditions: Warning: Found invalid chain at least ~6 blocks longer than our best chain.
Chain state database corruption likely.


upload_2015-8-11_0-27-3.png
 
This seems a bit weird (4x darksend denominate transactions in 1 minute)

hDuFKEq.jpg


edit : it just keeps adding darksend denominate transactions without confirming them..
update : they got confirmed shortly after posting this post
 
qwizzie said:
interesting, and they do get confirmed now.. it will make mixing a lot faster i assume.
Click to expand...
Hmm some of mine haven't got confirmed for 22 min:

upload_2015-8-11_1-51-57.png



edit: actually looks like it's stuck at block 82499
edit: zapping this wallet now...
 
Last edited by a moderator:
moli said:
Hmm some of mine haven't got confirmed for 22 min:

View attachment 1731


edit: actually looks like it's stuck at block 82499
Click to expand...

v0.12.0.41-44e002f

My 6 wallets are all on the same current block and even i see older unconfirmed transactions appearing between newer transactions that do get confirmed.
So i guess the old bug of not all transactions getting confirmed as fast as we hope they would is still present in this version... it just gets more visible.

My oldest unconfirmed transactions are from 40 minutes ago .. while wallets are fully in sync.
One of my transactions even shows a "!" while the wallet is fully in sync and iaw http://test.insight.dash.siampm.com/ , the rest are "?" waiting to be confirmed.

vkWPgww.jpg


edit : damn, mixing 500 / 8 rounds sure creates a lot of transactions :eek: :grin:
 
Last edited by a moderator:
I just updated 3 wallets to v0.12.0.41-44e002f (32-bit), on re-start 1 synced fine, the other 2 get stuck at block 82299 and need -reindex, then fine.
The one that did sync okay has been running 6 MNs for past 5 hrs - all have stayed ENABLED (though not received any "Mined" fees).
 
I'm trying to zap that wallet but it says "No block source available" and it's stuck at "0 hours behind".. Got these lines in the debug:

Code: 
2015-08-11 06:00:20 Added time data, samples 9, offset +3 (+0 minutes)
2015-08-11 06:00:20 nTimeOffset = +3  (+0 minutes)
2015-08-11 06:00:20 ERROR: AcceptBlockHeader : block is marked invalid
2015-08-11 06:00:20 ERROR: invalid header received 000000068daa48bd716dcca00efd163b0f8384249d11953434be3603d518ab55
2015-08-11 06:00:20 ProcessMessage(headers, 1135 bytes) FAILED peer=12
2015-08-11 06:01:19 ERROR: AcceptBlockHeader : block is marked invalid
2015-08-11 06:01:19 ERROR: invalid header received 000000068daa48bd716dcca00efd163b0f8384249d11953434be3603d518ab55
2015-08-11 06:01:19 ProcessMessage(headers, 1135 bytes) FAILED peer=9
2015-08-11 06:01:20 CheckBlock() : WARNING: Couldn't find previous block, skipping IsBlockPayeeValid()
2015-08-11 06:01:20 ERROR: AcceptBlockHeader : prev block not found
2015-08-11 06:01:20 ERROR: ProcessNewBlock : AcceptBlock FAILED
2015-08-11 06:01:20 ERROR: AcceptBlockHeader : block is marked invalid
2015-08-11 06:01:20 ERROR: invalid header received 000000068daa48bd716dcca00efd163b0f8384249d11953434be3603d518ab55
2015-08-11 06:01:20 ProcessMessage(headers, 1135 bytes) FAILED peer=5
2015-08-11 06:01:21 CheckBlock() : WARNING: Couldn't find previous block, skipping IsBlockPayeeValid()
2015-08-11 06:01:21 ERROR: AcceptBlockHeader : prev block not found
2015-08-11 06:01:21 ERROR: ProcessNewBlock : AcceptBlock FAILED
2015-08-11 06:01:23 ERROR: AcceptBlockHeader : block is marked invalid
2015-08-11 06:01:23 ERROR: invalid header received 000000068daa48bd716dcca00efd163b0f8384249d11953434be3603d518ab55
2015-08-11 06:01:23 ProcessMessage(headers, 1135 bytes) FAILED peer=7
2015-08-11 06:01:23 CheckBlock() : WARNING: Couldn't find previous block, skipping IsBlockPayeeValid()
2015-08-11 06:01:23 ERROR: AcceptBlockHeader : prev block not found
2015-08-11 06:01:23 ERROR: ProcessNewBlock : AcceptBlock FAILED
2015-08-11 06:01:23 ERROR: AcceptBlockHeader : block is marked invalid
2015-08-11 06:01:23 ERROR: invalid header received 000000068daa48bd716dcca00efd163b0f8384249d11953434be3603d518ab55
2015-08-11 06:01:23 ProcessMessage(headers, 1135 bytes) FAILED peer=12
2015-08-11 06:01:23 CheckBlock() : WARNING: Couldn't find previous block, skipping IsBlockPayeeValid()
2015-08-11 06:01:23 ERROR: AcceptBlockHeader : prev block not found
2015-08-11 06:01:23 ERROR: ProcessNewBlock : AcceptBlock FAILED
2015-08-11 06:01:23 ERROR: AcceptBlockHeader : block is marked invalid
2015-08-11 06:01:23 ERROR: invalid header received 000000068daa48bd716dcca00efd163b0f8384249d11953434be3603d518ab55
2015-08-11 06:01:23 ProcessMessage(headers, 1135 bytes) FAILED peer=10
2015-08-11 06:01:23 CheckBlock() : WARNING: Couldn't find previous block, skipping IsBlockPayeeValid()
2015-08-11 06:01:23 ERROR: AcceptBlockHeader : prev block not found
2015-08-11 06:01:23 ERROR: ProcessNewBlock : AcceptBlock FAILED
 
moli said:
I'm trying to zap that wallet but it says "No block source available" and it's stuck at "0 hours behind".. Got these lines in the debug:

Code: 
2015-08-11 06:00:20 Added time data, samples 9, offset +3 (+0 minutes)
2015-08-11 06:00:20 nTimeOffset = +3  (+0 minutes)
2015-08-11 06:00:20 ERROR: AcceptBlockHeader : block is marked invalid
2015-08-11 06:00:20 ERROR: invalid header received 000000068daa48bd716dcca00efd163b0f8384249d11953434be3603d518ab55
2015-08-11 06:00:20 ProcessMessage(headers, 1135 bytes) FAILED peer=12
2015-08-11 06:01:19 ERROR: AcceptBlockHeader : block is marked invalid
2015-08-11 06:01:19 ERROR: invalid header received 000000068daa48bd716dcca00efd163b0f8384249d11953434be3603d518ab55
2015-08-11 06:01:19 ProcessMessage(headers, 1135 bytes) FAILED peer=9
2015-08-11 06:01:20 CheckBlock() : WARNING: Couldn't find previous block, skipping IsBlockPayeeValid()
2015-08-11 06:01:20 ERROR: AcceptBlockHeader : prev block not found
2015-08-11 06:01:20 ERROR: ProcessNewBlock : AcceptBlock FAILED
2015-08-11 06:01:20 ERROR: AcceptBlockHeader : block is marked invalid
2015-08-11 06:01:20 ERROR: invalid header received 000000068daa48bd716dcca00efd163b0f8384249d11953434be3603d518ab55
2015-08-11 06:01:20 ProcessMessage(headers, 1135 bytes) FAILED peer=5
2015-08-11 06:01:21 CheckBlock() : WARNING: Couldn't find previous block, skipping IsBlockPayeeValid()
2015-08-11 06:01:21 ERROR: AcceptBlockHeader : prev block not found
2015-08-11 06:01:21 ERROR: ProcessNewBlock : AcceptBlock FAILED
2015-08-11 06:01:23 ERROR: AcceptBlockHeader : block is marked invalid
2015-08-11 06:01:23 ERROR: invalid header received 000000068daa48bd716dcca00efd163b0f8384249d11953434be3603d518ab55
2015-08-11 06:01:23 ProcessMessage(headers, 1135 bytes) FAILED peer=7
2015-08-11 06:01:23 CheckBlock() : WARNING: Couldn't find previous block, skipping IsBlockPayeeValid()
2015-08-11 06:01:23 ERROR: AcceptBlockHeader : prev block not found
2015-08-11 06:01:23 ERROR: ProcessNewBlock : AcceptBlock FAILED
2015-08-11 06:01:23 ERROR: AcceptBlockHeader : block is marked invalid
2015-08-11 06:01:23 ERROR: invalid header received 000000068daa48bd716dcca00efd163b0f8384249d11953434be3603d518ab55
2015-08-11 06:01:23 ProcessMessage(headers, 1135 bytes) FAILED peer=12
2015-08-11 06:01:23 CheckBlock() : WARNING: Couldn't find previous block, skipping IsBlockPayeeValid()
2015-08-11 06:01:23 ERROR: AcceptBlockHeader : prev block not found
2015-08-11 06:01:23 ERROR: ProcessNewBlock : AcceptBlock FAILED
2015-08-11 06:01:23 ERROR: AcceptBlockHeader : block is marked invalid
2015-08-11 06:01:23 ERROR: invalid header received 000000068daa48bd716dcca00efd163b0f8384249d11953434be3603d518ab55
2015-08-11 06:01:23 ProcessMessage(headers, 1135 bytes) FAILED peer=10
2015-08-11 06:01:23 CheckBlock() : WARNING: Couldn't find previous block, skipping IsBlockPayeeValid()
2015-08-11 06:01:23 ERROR: AcceptBlockHeader : prev block not found
2015-08-11 06:01:23 ERROR: ProcessNewBlock : AcceptBlock FAILED
Click to expand...

-reindex?

Edit: and then -zapwallet
 
this latest version does turn out to be a nice way to stress test transaction confirmations on a large scale ....
 
I just wanted to post a few words of encouragement for all of us. This version is groundbreaking stuff, so it's no surprise that the version number is north of 40 now.

V12, by it's nature of having functionality that is so radically different from anything we have had before, will take a lot of work to perfect. It is critical that the finished product just works, from speedy Darksend Mixing to InstantX working 100% of the time, to flawless DGBB functionality.

However long it takes, we should be thorough. If it's not done by September, so be it. No one's going anywhere.

The wait for release on mainnet will be that much sweeter knowing how much work went into making this a masterpiece. Keep up the good work, everyone, and don't let the bugs bite you!

Here's to a solid release, whenever it may be. Now if you'll excuse me, I have to reindex my wallet again! :eek:
 
You must log in or register to reply here.
Back
Top