V12 Testing Thread

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
Click to expand...

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?
Click to expand...
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 :smile:
 
Last edited by a moderator:
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 :smile:
Click to expand...

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?
 
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?
 
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.

notconfirm.png
 
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!!

upload_2015-8-9_10-44-24.png
 
Last edited by a moderator:
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
Click to expand...
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...
 
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...
Click to expand...
Nothing in debug log, I had to use a backup wallet to come back.
 
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?
Click to expand...
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
 
Last edited by a moderator:
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
Click to expand...
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
 
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.

notconfirm.png
Click to expand...

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..

gO9PtaK.jpg
 
Last edited by a moderator:
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)


upload_2015-8-9_8-58-37.png
 
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.

gO9PtaK.jpg
Click to expand...
After 3 hours i checked transactions and it was confirmed.
txid: 514d0e499a152a60e09be64a04906a19e00ebd293296f0c803c9d3b4f5f93591-000
 
AjM said:
After 3 hours i checked transactions and it was confirmed.
txid: 514d0e499a152a60e09be64a04906a19e00ebd293296f0c803c9d3b4f5f93591-000
Click to expand...

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..
 
AjM said:
After 3 hours i checked transactions and it was confirmed.
txid: 514d0e499a152a60e09be64a04906a19e00ebd293296f0c803c9d3b4f5f93591-000
Click to expand...
I think Testnet still has some syncing issue.... Maybe this is due to the multisig addresses we tested a few weeks ago? UdjinM6 ?
 
moli said:
I think Testnet has some syncing issue.... Maybe this is due to the multisig addresses we tested a few weeks ago? UdjinM6 ?
Click to expand...
but but others confirmed ok earlier when i was testing about 3 hours, but then only this one got stuck.
 
AjM said:
but but others confirmed ok earlier when i was testing about 3 hours, but then only this one got stuck.
Click to expand...
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.
 
You must log in or register to reply here.
Back
Top