V12 Testing Thread

[bertlebbert]

With this latest release, I'm still not able to combine Darksend and InstantX in same transaction. Darksend alone works - but only after I deleted fee_estimates.dat and restarted

 

[moli]

Please update -- v0.12.0.3

Changes:
- Proto bump

Windows 32bit version still shows the same protocol:
{
"version" : 120003,
"protocolversion" : 70079,
"walletversion" : 61000,

(This is a fresh wallet)

 

[bertlebbert]

Windows 32bit version still shows the same protocol:
{
"version" : 120003,
"protocolversion" : 70079,
"walletversion" : 61000,

(This is a fresh wallet)

Well... that likely explains my problem

 

[moocowmoo]

I've shutdown my .2 nodes for now -- will update to .3 within a few hours.

 

[TaoOfSatoshi]

It's fixed, my host rebooted the server with the reference node. I guess I should have it auto start on boot.

Or, you can cancel that server soon because you will no longer need it... :wink:

 

[moli]

Well... that likely explains my problem

According to this https://github.com/dashpay/dash/commit/b61f4761ffc9b9f0eaa42d231124abb6fecddda3
I guess we're still on protocol version 70079, not sure why eduffield said there's a protocol bump.
Right, UdjinM6 ?

 

[bertlebbert]

According to this https://github.com/dashpay/dash/commit/b61f4761ffc9b9f0eaa42d231124abb6fecddda3
I guess we're still on protocol version 70079, not sure why eduffield said there's a protocol bump.
Right, UdjinM6 ?

Right on, thanks for that :smile:

 

[moli]

Right on, thanks for that :smile:

Now I'm looking at it.. the protocol version bump is for InstantX.. Not sure how Instantx has to have a different protocol. Actually I don't quite understand this all.
I wish I could read code like reading a soft porn novel ... :tongue:

 

[bertlebbert]

Now I'm looking at it.. the protocol version bump is for InstantX.. Not sure how Instantx has to have a different protocol. Actually I don't quite understand this all.
I wish I could read code like reading a soft porn novel ... :tongue:

Ahaha, LOL

 

[UdjinM6]

According to this https://github.com/dashpay/dash/commit/b61f4761ffc9b9f0eaa42d231124abb6fecddda3
I guess we're still on protocol version 70079, not sure why eduffield said there's a protocol bump.
Right, UdjinM6 ?

yep, we are still on 70079, only min IX proto bumped to match min DS proto...
maybe he actually meant version bump?... well.. both should work now so no big deal

 

[moli]

yep, we are still on 70079, only min IX proto bumped to match min DS proto...
maybe he actually meant version bump?... well.. both should work now so no big deal

I actually thought when we had a protocol bump, everything -DS, MN, IX- all got the proto bump at the same time... No?

 

[TanteStefana]

I had same problem the other day, no payments to MN on Win32 wallet... I had previously added -server switch to my desktop shortcut when playing with mnbudget commands. It may be coincidence, but removing it seemed to help. Maybe you did the same when trying mnbudget?

Updating now, but no, I think somehow darksend broke my MN account, but why it showed as working all that time is the big mystery??

 

[TanteStefana]

OK, so I updated my wallet, and thinking I was late to the party, I went ahead and tried to IX 20 coins. So I did and got this:

Status: 1/unconfirmed, broadcast through 3 node(s)
Date: 6/22/2015 17:36
To: laptop testnet yDyznt52toe4SYicYLuY2JjieUvDmT53Rz
Debit: -20.00000000 tDASH
Transaction fee: -0.00020000 tDASH
Net amount: -20.00020000 tDASH
Transaction ID: b32fd087f1c2e134303f826d428d91e19cfc9d6232f865e18fa463b9ee55978e-000

after deleting fee-estimate thingy, it worked NP, but with only being broadcast through 3 nodes, I still got a full blue clock on my transactions tab, though it says I only have 1 confirmation and I still dont' have instantX confirmations

Using win32 version on win7 64bit

It's also been 10 minutes, and no progress. still only 1 confirmation

 

[TanteStefana]

Humm, this is also interesting. The following is being spammed in my debug log:

Can't set state to ERROR or SUCCESS as a Masternode.
2015-06-23 00:44:57 CDarksendPool::UpdateState() - Can't set state to ERROR or SUCCESS as a Masternode.
2015-06-23 00:45:27 CDarksendPool::UpdateState() - Can't set state to ERROR or SUCCESS as a Masternode.
2015-06-23 00:45:57 CDarksendPool::UpdateState() - Can't set state to ERROR or SUCCESS as a Masternode.
2015-06-23 00:46:27 CDarksendPool::UpdateState() - Can't set state to ERROR or SUCCESS as a Masternode.


I don't know if my masternode is actually running. It says it is, of course, but I don't know who those errors are directed to? My masternode or another one detected?

The masternodeprivkey: is in the dash.conf file under the dash folder, not the testnet3 folder. Is that correct? I do get confused sometimes ;P

 

[moli]

lol..

 

[moli]

 

[TaoOfSatoshi]

View attachment 1482

I'm so jealous, my IX still does not work....

 

[moli]

I'm so jealous, my IX still does not work....

Before installing the latest version I deleted everything in folder "testnet3" except "blocks" and "chainstate" to have a clean slate, just imo to see what's already fixed and what's to be fixed.

 

[bertlebbert]

With this release the following are still problems for me:

1. In order to Darksend coin, I must first delete fee_estimates.dat to avoid error warning about excessive fee and failed transaction.
2. Darksend and InstantX work fine separately, but combined result in error saying "Unable to locate enough denominated coin" and failed transaction.
3. My MN says started successfully and shows up under "masternode list addr" command, but doesn't get paid.

Edit: Scratch #3, MN just received 13.92857138 fee

 

[coingun]

It's fixed, my host rebooted the server with the reference node. I guess I should have it auto start on boot.

I believe there is many VPS providers that won't reboot nodes without consent. I know that some hosts are very bad for this... <i'm looking at your vultr....> and others have a policy to not automagically reboot vps' unless of course its a specific security related must patch type scenario.