v0.11.1.x InstantX Testing

Status
Not open for further replies.
Hmm, sent 5 tDRKs (IX+DS) to the other wallet, but didn't receive the tx.

ix.jpg
 
eduffield - I restarted the wallet twice, it shows the Darksend-InstantX transaction which was sent first is still not confirmed. Does this have anything to do with Darksend?

upload_2015-2-5_13-4-18.png
 
UdjinM6 said:
Everyone who have their wallets crashing on start/reindex please check this link https://darkcointalk.org/threads/v0-11-0-darkcoin-core-release.3601/page-37#post-39944
Click to expand...
My wallet:

{
"version" : 110109,
"protocolversion" : 70059,
"walletversion" : 61000,
"balance" : 639.41195211,
"darksend_balance" : 537.30537300,
"blocks" : 103659,
"timeoffset" : 7,
"connections" : 10,
"proxy" : "",
"difficulty" : 0.16066950,
"testnet" : true,
"keypoololdest" : 1423142446,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
Click to expand...
It crashed while syncing with -reindex at around "5 weeks behind". I restarted with no -reindex and it caught up fine.
 
************************************** 11.1.10 ***************************************

One more upgrade, then I'm going to try breaking the network again.

- Version / Protocol bump
- Lower signature requirements for IX
- Two complete locks that have the same inputs will now cancel each other out
- Much improved code to detect and resolve forks

Compiling: If you get a 404 please try again in a bit

Source: https://github.com/darkcoin/darkcoin/tree/v0.11.1.x

Windows 32bit:
http://bamboo.darkcoin.qa/artifact/...07/gitian-win-darkcoin-bin/32/darkcoin-qt.exe

Mac OS X:
http://bamboo.darkcoin.qa/browse/DR...-osx-darkcoin-dist/darkcoin-0.11.1.10-osx.dmg

Linux 32bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/32/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/...12/gitian-linux-darkcoin-bin/bin/32/darkcoind

Linux 64bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/...12/gitian-linux-darkcoin-bin/bin/64/darkcoind
 
Last edited by a moderator:
My wallets are also on the right version :) .

I tried to send both IX+DS and IX txs only and received the IX transaction.
Closed the other wallet, started it again and the second tx appeared, but as regular, not IX+DS.

ix2.jpg
 
getting this on v.10 link

HTTP request sent, awaiting response... 500 Internal Server Error
2015-02-05 18:54:27 ERROR 500: Internal Server Error.

EDIT: working now
 
Last edited by a moderator:
tMN says;

"errors" : "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."
Click to expand...

Seems to be 1h behind

root@install:~# ./darkcoind getinfo
{
"version" : 110110,
"protocolversion" : 70060,
"walletversion" : 61000,
"balance" : 1278.69208820,
"darksend_balance" : 0.00000000,
"blocks" : 103563,
"timeoffset" : -1,
"connections" : 9,
"proxy" : "",
"difficulty" : 0.06863827,
"testnet" : true,
"keypoololdest" : 1422877191,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."
}
Click to expand...
 
oblox said:
Did you reindex on your update to the latest?
Click to expand...

No. Will try reindexing.
The QT seemed stuck, but got up to height no problem.

EDIT: -reindex fixed the MN

.
 
Last edited by a moderator:
is DS limited to 2000? I cannot get my qt to accept a higher number in the setting for amount and rounds
 
Crazy amounts of dns requests on testnet to the dnsseeds....

Starting 4 DNS threads for test.dnsseed.masternode.io on klaus.masternode.io (port 5353).......done
[15-02-05 20:33:25] 0/14 available (4 tried in 949s, 0 new, 10 active), 0 banned; 598003 DNS requests, 3013 db queries
 
coingun said:
Crazy amounts of dns requests on testnet to the dnsseeds....
Starting 4 DNS threads for test.dnsseed.masternode.io on klaus.masternode.io (port 5353).......done

[15-02-05 20:33:25] 0/14 available (4 tried in 949s, 0 new, 10 active), 0 banned; 598003 DNS requests, 3013 db queries
Click to expand...

Maybe...

eduffield said:
************************************** 11.1.10 ***************************************
One more upgrade, then I'm going to try breaking the network again.
Click to expand...
 
did two InstantX transactions with v.0.11.1.10

From B to A : 1000 .. got succesfully Instantx'ed, it got 7 MN verifications and 4 nodes broadcasted right away, transaction fully confirmed in wallet

Status: 7 confirmations (verified via instantx), broadcast through 4 node(s)
Date: 5-2-2015 22:51
To: Test 1 yAS9wHH4wGPRGfaASLXi1y9ddUWaTFxYn8
Debit: -1000.00 tDRK
Transaction fee: -0.01 tDRK
Net amount: -1000.01 tDRK
Transaction ID: 9e5864b75f809a6aa7d2fc4156c594cf3e074af80ac8c4aafacf859f45fa19e1-000

From A to B : 859.756 through coin control, specifically not selected the 1000 input but what was left in that wallet .. got 5 succesfull MN verifications but transaction
doesnt get broadcast. It ends up getting stuck.

Status: 5/offline (verified via instantx), has not been successfully broadcast yet
Date: 5-2-2015 22:56
To: Test Darkcoin 2 y3DUP7joBEXH9Cimh4JM3D9thMebDnRwH5
Debit: -859.755 tDRK
Transaction fee: -0.001 tDRK
Net amount: -859.756 tDRK
Transaction ID: 21f3a5ad570a6cd159be80b69ca0da3a1745348014fa8267d200d2be3f6368fc-000

Conclusion : doing an outgoing InstantX transaction on a wallet that has an incoming InstantX transaction which has not been fully confirmed POW (6x)
will get you a stuck outgoing InstantX transaction.
 
Last edited by a moderator:
qwizzie said:
From A to B : 859.756 through coin control, specifically not selected the 1000 input but what was left in that wallet .. got 5 succesfull MN verifications but transaction
doesnt get broadcast. It ends up getting stuck.

Status: 5/offline (verified via instantx), has not been successfully broadcast yet
Click to expand...

Happened to me twice in a row, without using coin control. Waited 15 minutes, still no broadcast.
After restart they are listed as normal transaction (as it should be) but never get a confirmation.

-zapwallettxes removes them, but they shouldn't be in this state at all.
 
Status
Not open for further replies.
Back
Top