v0.11.1.x InstantX Testing
- Thread starter eduffield
- Start date
- Status
qwizzie
Well-known member
hello 50 masternodes...
got a successfull Instant X transaction i think, just waiting on 1 more confirmation but amount from sender has been added to receiver's balance already. Very very fast :
Status: 5/confirmed (verified via instantx), has not been successfully broadcast yet
Date: 2-2-2015 22:20
To: Test 5 y5s7CghsxVgapQW2d7C7Xi5hmb4drWvyob
Debit: -25.00 tDRK
Transaction fee: -0.001
tDRKNet amount: -25.001
tDRKTransaction ID: ada73a14f4dc3c5a5caf37d8b5bfd142c5537b4920a22ebd55aee818e16d7243-000
i suspect once we hit block 102106 it gets totally confirmed in my transaction and broadcasted
edit : yep .. at block 102106 transaction got totally confirmed and shows :
Status: 7 confirmations (verified via instantx), broadcast through 1 node(s)
got a successfull Instant X transaction i think, just waiting on 1 more confirmation but amount from sender has been added to receiver's balance already. Very very fast :
Status: 5/confirmed (verified via instantx), has not been successfully broadcast yet
Date: 2-2-2015 22:20
To: Test 5 y5s7CghsxVgapQW2d7C7Xi5hmb4drWvyob
Debit: -25.00 tDRK
Transaction fee: -0.001
tDRKNet amount: -25.001
tDRKTransaction ID: ada73a14f4dc3c5a5caf37d8b5bfd142c5537b4920a22ebd55aee818e16d7243-000
i suspect once we hit block 102106 it gets totally confirmed in my transaction and broadcasted
edit : yep .. at block 102106 transaction got totally confirmed and shows :
Status: 7 confirmations (verified via instantx), broadcast through 1 node(s)
Last edited by a moderator:
crowning
Well-known member
Do we have this one already?
Code:
2015-02-02 21:20:18 InstantX::ProcessConsensusVote - Unknown Masternode
2015-02-02 21:20:18 ProcessMessages(txlvote, 337 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2015-02-02 21:20:18 ProcessMessage(txlvote, 337 bytes) FAILED
2015-02-02 21:20:18 ProcessMessages(txlvote, 337 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than
eduffield
Core Developer
I changed the format of the messaging, that's an old client from yesterday trying to talk to you.
qwizzie
Well-known member
anyways, i did another one and just like the previous one it works.. just waiting for next block (102113) to have it totally confirmed (6 confirmations)
Status: 5/confirmed (verified via instantx), has not been successfully broadcast yet
Date: 2-2-2015 22:36
To: Test 5 y5s7CghsxVgapQW2d7C7Xi5hmb4drWvyob
Debit: -35.00 tDRKTransaction fee: -0.001 tDRK
Net amount: -35.001
tDRKTransaction ID: 9d23a4d1ac8cb70b7ff564ec5d39109742a093221f62f9f1187d0ee6e1a84487-000
edit : yep .. at block 102113 it got totally confirmed
Status: 6 confirmations (verified via instantx), broadcast through 1 node(s)
Last edited by a moderator:
and also:
Code:
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:57 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:57 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:58 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:58 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:58 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:58 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:58 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:58 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:58 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:58 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:58 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:58 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:58 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:58 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:58 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:58 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:58 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:58 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:58 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:58 ProcessMessage(txlvote, 894 bytes) FAILED
2015-02-02 21:10:58 ProcessMessages(txlvote, 894 bytes) : Exception 'ReadCompactSize() : size too large' caught
2015-02-02 21:10:58 ProcessMessage(txlvote, 894 bytes) FAILEDI'm guessing its the same issue as Evan just replied to.
eduffield
Core Developer
Yeah, that's OK. It'll go away
qwizzie
Well-known member
observation (and i think its mentioned before) : if you happen to be doing an InstantX transaction which was confirmed through 5 MN's and through 1 broadcast (making it a complete confirmation transaction-wise) and you closed and reopened yr wallet it will fall back to just normal POW confirmation and you will have to wait till that transaction is POW confirmed 6x before being able to do another InstantX (you will get the message insufficient funds, transaction creation failed otherwise)
oblox
Well-known member
Can IX tx's be immediately sent to another party either via IX or without or is it still the case of locking it till it receives 6 standard confirms? Just wondering if masternodes are capable of following the coins and locking the appropriate amounts for something like this to work and scale appropriately for a large network.
qwizzie
Well-known member
right now it seems to need 5 MN's confirmations and 1 POW confirmation
DrkMiner
Active member
this transaction been 0/offline
Status: 0/offline, has not been successfully broadcast yetDate: 02/02/2015 16:55To: yAS9wHH4wGPRGfaASLXi1y9ddUWaTFxYn8Debit: -10.00 tDRKTransaction fee: -0.0003 tDRKNet amount: -10.0003 tDRKTransaction ID: 43f18285b9f66212897762910fe08ae3883b5cb9d5c7275ab4c882c38476df46-000
any idea why?
Status: 0/offline, has not been successfully broadcast yetDate: 02/02/2015 16:55To: yAS9wHH4wGPRGfaASLXi1y9ddUWaTFxYn8Debit: -10.00 tDRKTransaction fee: -0.0003 tDRKNet amount: -10.0003 tDRKTransaction ID: 43f18285b9f66212897762910fe08ae3883b5cb9d5c7275ab4c882c38476df46-000
any idea why?
qwizzie
Well-known member
has those 10 tDRK been added to yAS9wHH4wGPRGfaASLXi1y9ddUWaTFxYn8 total ?
if yes its just waiting for 1 POW confirmation i think
oblox
Well-known member
So after 1 POW confirm, the received funds can immediately be sent to another address where they would be locked and able to be used after 1 POW confirm on their end (assuming the masternode confirm before the POW confirm)? Rinse and repeat?
qwizzie
Well-known member
i havent tried to sent through to another address yet once received.. easy enough to test though..
DrkMiner
Active member
wow!!! that was fast!!
Status: 6 confirmations (verified via instantx)Date: 02/02/2015 17:17From: unknownTo: y2wLS8cqAkyjkSR3Cfiy1ezWbQzJkTmzmX (own address, label: test)Credit: 10.00 tDRKNet amount: +10.00 tDRKTransaction ID: b05b3a996cf39a7ceb9f94d24871ff9dbcafe75fda4f0d4f85a68af615bc1a34-000
Status: 6 confirmations (verified via instantx)Date: 02/02/2015 17:19From: unknownTo: y2wLS8cqAkyjkSR3Cfiy1ezWbQzJkTmzmX (own address, label: test)Credit: 10.00 tDRKNet amount: +10.00 tDRKTransaction ID: 609dd27c1ce43ea92e72dc7f3de3db704396f942f3d75d88ac1819e99a5014cc-000
IX works! I'm getting the transaction with 6 confirmatins!
Would like to see the question mark changed in the "Transactions" tab
qwizzie
Well-known member
Status: 5/confirmed (verified via instantx), has not been successfully broadcast yet
Date: 2-2-2015 23:17
To: y2wLS8cqAkyjkSR3Cfiy1ezWbQzJkTmzmX
Debit: -10.00 tDRK
Transaction fee: -0.001
tDRKNet amount: -10.001
tDRKTransaction ID: b05b3a996cf39a7ceb9f94d24871ff9dbcafe75fda4f0d4f85a68af615bc1a34-000
now just wait for next block (102120) to see it totally confirmed
Sub-Ether
Well-known member
Evan maybe meant the instantX data does not go straight into the blockchain yet and this is to be activated later on?
- Status