V12 Testing Thread

UdjinM6 · Aug 8, 2015

crowning said:
For those interested, I just ran an integration test with v0.12.0.40 on main-net and it looks good so far:
View attachment 1716

NOTE: It's probable that you will need to reindex/re-download blockchain when you decide to run v11 with the same datadir

AjM said:
Zero mn:s?

Yes, masternode protocol is incompatible

EDIT: Hmm.. actually I think I wasn't 100% correct - "Total: 0" could be not what we want for migration if we want SPORK_10_MASTERNODE_PAY_UPDATED_NODES to work.
https://github.com/dashpay/dash/pull/494
https://github.com/dashpay/dash/pull/495

eduffield crowning flare review wanted

AjM thanks for pointing out

moli · Aug 9, 2015

Thanks to thelazier we now have a new faucet, and here are the current working Testnet faucets:

http://test.faucet.dash.siampm.com/submit (thelazier )
http://test.faucet.masternode.io/ (coingun)
http://test.faucet.dashninja.pl/ (elbereth)

thelazier , coingun , elbereth , Thanks!

TaoOfSatoshi · Aug 9, 2015

40 is great for me, no hanging, DS fast, feels smooth.

crowning · Aug 9, 2015

UdjinM6 said:
NOTE: It's probable that you will need to reindex/re-download blockchain when you decide to run v11 with the same datadir

Yes, masternode protocol is incompatible

EDIT: Hmm.. actually I think I wasn't 100% correct - "Total: 0" could be not what we want for migration if we want SPORK_10_MASTERNODE_PAY_UPDATED_NODES to work.
https://github.com/dashpay/dash/pull/494
https://github.com/dashpay/dash/pull/495

eduffield crowning flare review wanted

AjM thanks for pointing out

I just took a quick look (no time for more), but wouldn't this work exactly the other way around? v0.12 nodes see old nodes and probably pay them, but v0.11 nodes won't see us because we never send dsee and dseep pings?

moli · Aug 9, 2015

crowning - we have a new spork, "SPORK_10_MASTERNODE_PAY_UPDATED_NODES", i guess when this is enforced it won't pay masternodes that aren't updated?

AjM · Aug 9, 2015

UdjinM6 eduffield
Mixing testing, but, one denominate wont confirm, multiple blocks past, its stuck.
Any idea why?
Stuck denominate : 11:56, latest block 12:13, wallet fully synced.

Sub-Ether · Aug 9, 2015

I have an error when I try to enter the password on mainnet for Dash Core version v0.12.0.40-e8ba732 (64-bit),
if I click ignore, the password fails so the wallet is unusable.

Edit: upgrade wallet format fails and salvage wallet wipes the entire balance from the wallet!!

UdjinM6 · Aug 9, 2015

Sub-Ether said:
I have an error when I try to enter the password on mainnet for Dash Core version v0.12.0.40-e8ba732 (64-bit),
if I click ignore, the password fails so the wallet is unusable.

Edit: upgrade wallet format fails and salvage wallet wipes the entire balance from the wallet!!

View attachment 1717

Look in debug.log, should say "The wallet is probably corrupted: Some keys decrypt but not all."
Salvage wallet works really bad for encrypted wallets, that's a known bitcoin bug...

Sub-Ether · Aug 9, 2015

UdjinM6 said:
Look in debug.log, should say "The wallet is probably corrupted: Some keys decrypt but not all."
Salvage wallet works really bad for encrypted wallets, that's a known bitcoin bug...

Nothing in debug log, I had to use a backup wallet to come back.

UdjinM6 · Aug 9, 2015

crowning said:
I just took a quick look (no time for more), but wouldn't this work exactly the other way around? v0.12 nodes see old nodes and probably pay them, but v0.11 nodes won't see us because we never send dsee and dseep pings?

Hmmm.. SPORK_10_MASTERNODE_PAY_UPDATED_NODES was implemented to let old nodes be legit until it activates so we need them in our list. But maybe it's a good idea to inject new nodes in old nodes' list too..

EDIT:
https://github.com/dashpay/dash/pull/494#issuecomment-129188190
https://github.com/UdjinM6/dash/commit/5bd997f2558f3df7e32f798d8e9a1d95eb698bc0

moli · Aug 9, 2015

Sub-Ether said:
I have an error when I try to enter the password on mainnet for Dash Core version v0.12.0.40-e8ba732 (64-bit),
if I click ignore, the password fails so the wallet is unusable.

Edit: upgrade wallet format fails and salvage wallet wipes the entire balance from the wallet!!

View attachment 1717

Interesting...

if (keyPass && keyFail)
{
LogPrintf("The wallet is probably corrupted: Some keys decrypt but not all.");
assert(false);
}

https://github.com/dashpay/dash/blob/v0.12.0.x/src/crypter.cpp#L257

qwizzie · Aug 9, 2015

AjM said:
UdjinM6 eduffield
Mixing testing, but, one denominate wont confirm, multiple blocks past, its stuck.
Any idea why?
Stuck denominate : 11:56, latest block 12:13, wallet fully synced.

I have the same problem with 2 of my 6 wallets (Testdash1 & Testdash2), transactions do not get confirmed and stagnate the mixing process
Transaction id's :

5ce52957bd57b02fffa5d78107c47694f35e519c25e3d1e34a20c9dc80354cb2-000
5ce52957bd57b02fffa5d78107c47694f35e519c25e3d1e34a20c9dc80354cb2-000
Both from the exact same time, 14:19 hrs

edit : looks like testdash4 is staying unconfirmed too
Transaction id: 40c74dff56f06e4df86e4e8e0223ae670fb8c0a4cf72e87f8d41a32627b223e5-000

conclusion :

All wallets fully synced and up to date and after 2 hours of mixing the wallets do seem to stay in sync and dont freeze anymore... not yet anyways. Downside is that not all transactions are getting confirmed.

update : in the end they did get confirmed only very late..

moli · Aug 9, 2015

I also have Darksend Denominates that have been stuck for an hour...
Are we having a stuck DS party? lol

(v0.12.0.40-e8ba732 - windows 32bit)

moli · Aug 9, 2015

OH ... Now they're both OKAY!! LOL

AjM · Aug 9, 2015

qwizzie said:
I have the same problem with 2 of my 6 wallets (Testdash1 & Testdash2), transactions do not get confirmed and stagnate the mixing process
Transaction id's :

5ce52957bd57b02fffa5d78107c47694f35e519c25e3d1e34a20c9dc80354cb2-000
5ce52957bd57b02fffa5d78107c47694f35e519c25e3d1e34a20c9dc80354cb2-000
Both from the exact same time, 14:19 hrs

edit : looks like testdash4 is staying unconfirmed too
Transaction id: 40c74dff56f06e4df86e4e8e0223ae670fb8c0a4cf72e87f8d41a32627b223e5-000

conclusion :

All wallets fully synced and up to date and after 2 hours of mixing the wallets do seem to stay in sync and dont freeze anymore... not yet anyways. Downside is that not all transactions are getting confirmed.

After 3 hours i checked transactions and it was confirmed.
txid: 514d0e499a152a60e09be64a04906a19e00ebd293296f0c803c9d3b4f5f93591-000

AjM · Aug 9, 2015

moli said:
OH ... Now they're both OKAY!! LOL

View attachment 1719

Yep, but that is not good for mixing if confirmations take 1-3 hours

qwizzie · Aug 9, 2015

AjM said:
After 3 hours i checked transactions and it was confirmed.
txid: 514d0e499a152a60e09be64a04906a19e00ebd293296f0c803c9d3b4f5f93591-000

you are right, i see my transactions got confirmed too .. just very very late

Could it be that budget proposal payments took priority ? There are some finalized budgets out there..

moli · Aug 9, 2015

AjM said:
After 3 hours i checked transactions and it was confirmed.
txid: 514d0e499a152a60e09be64a04906a19e00ebd293296f0c803c9d3b4f5f93591-000

I think Testnet still has some syncing issue.... Maybe this is due to the multisig addresses we tested a few weeks ago? UdjinM6 ?

AjM · Aug 9, 2015

moli said:
I think Testnet has some syncing issue.... Maybe this is due to the multisig addresses we tested a few weeks ago? UdjinM6 ?

but but others confirmed ok earlier when i was testing about 3 hours, but then only this one got stuck.

moli · Aug 9, 2015

AjM said:
but but others confirmed ok earlier when i was testing about 3 hours, but then only this one got stuck.

Yes, me, you, and qwizzie had these stuck fees.. I think it has something to do with the sync issue that the devs have been working on to solve.

AjM · Aug 9, 2015

moli said:
Yes, me, you, and qwizzie had these stuck fees.. I think it has something to do with the sync issue that the devs have been working on to solve.

Ok, standby...

MangledBlue · Aug 9, 2015

Anybody explain why I just mined a 20DASH block??

Status: 6 confirmations, broadcast through 2 nodes
Date: 8/9/2015 11:27
Source: Generated
Credit: 20.89285715 tDASH (matures in 95 more blocks)
Net amount: 0.00000000 tDASH
Transaction ID: b73b92e7c20e55b4aeb188964dba9ba9ee27cbd7fcfdfb68edc7e690a4dbbb55-000

All others are 8Dash

moli · Aug 9, 2015

MangledBlue said:
Anybody explain why I just mined a 20DASH block??

Status: 6 confirmations, broadcast through 2 nodes
Date: 8/9/2015 11:27
Source: Generated
Credit: 20.89285715 tDASH (matures in 95 more blocks)
Net amount: 0.00000000 tDASH
Transaction ID: b73b92e7c20e55b4aeb188964dba9ba9ee27cbd7fcfdfb68edc7e690a4dbbb55-000

All others are 8Dash

b73b92e7c20e55b4aeb188964dba9ba9ee27cbd7fcfdfb68edc7e690a4dbbb55 is not found on:
http://test.explorer.darkcoin.qa/chain/tDash
or: http://test.insight.dash.siampm.com/
Maybe you mined on a wrong chain?

qwizzie · Aug 9, 2015

Situation on testnet with regards to confirmation of transactions seems to have stablized, most of my transactions get confirmed the next block now.
All my wallets kept full sync with this version (v0.12.0.40-e8ba732) and i experienced no more windows wallet freezes.
Instantx works good too.

MangledBlue · Aug 9, 2015

81454

My block is much smaller - I'd say so - hummmmm

edit: dumped everything but wallet
trying now

MangledBlue · Aug 9, 2015

looks like somethings new is about to come out of the oven

MangledBlue · Aug 9, 2015

resync'd now

and all those blocks mined are now gone -

edit: in fact 500+DASH now gone - lol

moli · Aug 9, 2015

MangledBlue said:
looks like somethings new is about to come out of the oven

Win build 297 just got done:
https://dashpay.atlassian.net/builds/browse/DASHW-DEV-297
"more dsee/dseep for migration: - inject our node in old masrternodes' list / ping accordingly - ignore dsee/dseep after SPORK_10_MASTERNODE_PAY_UPDATED_NODES is activated" .. "support old masternodes"
https://github.com/dashpay/dash/pull/494

~~UdjinM6 -does it mean masternodes on older versions still get paid until the spork is activated, and if they don't update they won't get paid?~~

EDIT: nvm.. i just saw your explanation here: https://dashtalk.org/threads/v12-testing-thread.5484/page-130#post-62512

MangledBlue · Aug 9, 2015

1 core on a Intel i7 is 10-15X more powerful then a single core on a Pi-2b

[just say'n]

AjM · Aug 9, 2015

qwizzie said:
Situation on testnet with regards to confirmation of transactions seems to have stablized, most of my transactions get confirmed the next block now.
All my wallets kept full sync with this version (v0.12.0.40-e8ba732) and i experienced no more windows wallet freezes.
Instantx works good too.

Just got again one stuck transaction.
v0.12.0.40-d54d64d
Transaction ID: f485519dc80f1cfa699ce0ea2b3325c06ac1f6a2bf0633c7c93f735ac8d44d16-000

Edit: and now confirmed, jumped over one block.

V12 Testing Thread

Official Dash Dev

Grizzled Member

Grizzled Member

Well-known Member

Grizzled Member

Well-known Member

Well-known Member

Official Dash Dev

Well-known Member

Official Dash Dev

Grizzled Member

Grizzled Member

Grizzled Member

Grizzled Member

Well-known Member

Well-known Member

Grizzled Member

Grizzled Member

Well-known Member

Grizzled Member

Well-known Member

MangledBlue

Guest

Grizzled Member

Grizzled Member

MangledBlue

Guest

MangledBlue

Guest

MangledBlue

Guest

Grizzled Member

MangledBlue

Guest

Well-known Member