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

V12.1 Testnet Launch Thread

Status
Not open for further replies.
One more thing: On the latest build, and I believe previous builds, but my memory fails me, the hot wallet (with the funds) says it started the masternode, but the remote wallet (the one on the server) says it's waiting for remote activation.

The message isn't propagating or something? It shows up immediately on mainnet nodes, is this different now? I do see on my local "hot" wallet, that the MN was "Pre Enabled". Is this some kind of new safety step?

That is normal behaviour. I had the same doubt myself and @flare explained it to me. When the QT says "successful" it means it successfully sent the signed message to the nodes. It does not necessarily mean that the node successfully activated.

Could be for several reasons (bad config, ban, on a fork, etc), but the best thing to do to troubleshoot is

- shut down the node daemon for more than an hour, for it to drop
- check all the configs (ip's, genkeys, tx hashes, etc), including QT
- update the daemon if not already, and QT
- start the nodes reindexing the blockchain (fix forking) + QT
- let it sync up to block height and check latest block hash to verify if they are all on the correct chain + QT
- Start-many

I think that should do it.

For the miners, the same procedure, but please check "masternode winners" to see if you have a populated winner's list. If not, don't start mining. Wait until you have winners list and then you're good to go.

.
 
For the miners, the same procedure, but please check "masternode winners" to see if you have a populated winner's list. If not, don't start mining. Wait until you have winners list and then you're good to go.
Actually @UdjinM6 resolved this bug, winners list is syncronized now.
 
So I have my test client set up as a liquidity provider. I check coin control and see that I have plenty of 8-round denoms available. Yet my PrivateSend balance shows 0, and when I go to coin control and try to PS myself some funds, it says there isn't enough PrivateSend funds.

This may not be a bug, but the function should probably be more user friendly. Is it normal for LPs not to be able to PrivateSend?
 
3 wallets, 3 different chains, LOL. Is this supposed to be resolved in the latest version posted yesterday? do I have the wrong version? Dash Core version v0.12.1.0-d0ad4ad (64-bit)

Note: after a few restarts and deleting all except wallet.dat and MN.conf I got them on the same chain (hopefully correct one) and all is well :)
 
Last edited:
Currently @flare's Block Explorer is on 15250 and @elbereth's is on 15266.

I left 5 empty wallets running MNs on for last 8 hrs - all stayed on the longer chain. But just now I start the wallet containing collateral for those MNs and it forks to the shorter chain - even after deleting all except wallet.dat and masternode.conf.

Edit: Sorry, after a 2nd look, all wallets are on same (shorter) chain - hoping that is correct chain...
 
Last edited:
InstantSend Testing

Test 1 : Failed

Status: 0/confirmed (InstantSend verification in progress - 4 of 10 signatures ), broadcast through 14 nodes
Date: 1-6-2016 19:26
To: TestDash2 ySJmSKL7dw4RiSCUSmpKAk1zUpgP5nN2Ln
Debit: -10.00000000 tDASH
Transaction fee: -0.01000000 tDASH
Net amount: -10.01000000 tDASH
Transaction ID: f228e6ffef2dbebebaac3c441926080f68f64fac6ed8a9dda3988e4ee0bda945-000

Test 2 : Failed

Status: 0/confirmed (InstantSend verification in progress - 4 of 10 signatures ), broadcast through 14 nodes
Date: 1-6-2016 19:30
To: TestDash3 yRpRRQoy7FhY3sZVgQpdCPP6Vd31Vpp6qw
Debit: -10.00000000 tDASH
Transaction fee: -0.01000000 tDASH
Net amount: -10.01000000 tDASH
Transaction ID: a1557b98f51b9060fd6eaae007836091e64d93a13bd298fcdb7b6fc7d125e519-000

Test 3 : Failed

Status: 0/confirmed (InstantSend verification in progress - 4 of 10 signatures ), broadcast through 14 nodes
Date: 1-6-2016 19:32
To: TestDash4 ySQmPqJZ1ju1qV4ckJQhoiUHkTGo3pVm1J
Debit: -10.00000000 tDASH
Transaction fee: -0.01000000 tDASH
Net amount: -10.01000000 tDASH
Transaction ID: 0dfe36f83c9a82b322a6f6ca2d9005638c6d6881bc2417e6d05a1c917250001c-000

Test 4 : Failed

Status: 0/confirmed (InstantSend verification in progress - 4 of 10 signatures ), broadcast through 8 nodes
Date: 1-6-2016 19:33
To: TestDash5 yTv8Ni2NbAVkwESskx8YxzEUHdnqHz1amX
Debit: -10.00000000 tDASH
Transaction fee: -0.01000000 tDASH
Net amount: -10.01000000 tDASH
Transaction ID: 9fa21da73f101ffdbad04cc2647535cec377e3c2ef958854c8c7e11a0880d3bf-000

Test 5 : Failed

Status: 0/confirmed (InstantSend verification in progress - 2 of 10 signatures ), broadcast through 12 nodes
Date: 1-6-2016 19:41
To: TestDash6 yesY4Ka84aVzQ5RGwRwpJQfmfzfDCzZfhX
Debit: -25.00000000 tDASH
Transaction fee: -0.01000000 tDASH
Net amount: -25.01000000 tDASH
Transaction ID: 013366adffa6053c9fd1434d87c13898f4569b4d8b8b798ab31c1ce9933960c8-000

Number of connections : 5-7
Number of masternodes : 65

I will try this again when i have more connections and masternodes stay stable (they fluctuate a bit)
 
Last edited:
Currently @flare's Block Explorer is on 15250 and @elbereth's is on 15266.

I left 5 empty wallets running MNs on for last 8 hrs - all stayed on the longer chain. But just now I start the wallet containing collateral for those MNs and it forks to the shorter chain - even after deleting all except wallet.dat and masternode.conf.

Edit: Sorry, after a 2nd look, all wallets are on same (shorter) chain - hoping that is correct chain...

Establishing a network connection sometimes takes a very long time (ie. no block source)...

InstantSend Testing

Test 1 : Failed

Testnet has forked, i am compiling a new version to resolve this.
 
Latest build (git-9b9d105) of v0.12.1.x branch
kSAorsZ.jpg

Only Elbereth's explorer is synced correctly.... FYI
by the way, to check active chain and possible forks type 'getchaintips' in your console.
 
Last edited:
Status
Not open for further replies.
Back
Top