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

v0.11.1.x InstantX Testing

Status
Not open for further replies.
could someone please send me some tDrk?

yKeX9btuhHU6tmmoDmFGnL4YrworZXZyL2

edit:
thank you to whoever sent me that 100tdrk! that was fast

Edit:
So I just received 100tdrk. I've tried to send myself some coins to my other wallet and I get a error msg saying that I have insufficient funds for the transaction ..

Edit: lol
I just restarted my wallet and that fixed it. OooooWeee instant X , bang , super fast
 
Last edited by a moderator:
skillit said:
could someone please send me some tDrk?

yKeX9btuhHU6tmmoDmFGnL4YrworZXZyL2

edit:
thank you to whoever sent me that 100tdrk! that was fast

Edit:
So I just received 100tdrk. I've tried to send myself some coins to my other wallet and I get a error msg saying that I have insufficient funds for the transaction ..

Edit: lol
I just restarted my wallet and that fixed it. OooooWeee instant X , bang , super fast
Click to expand...
No problem...
sending another 50
 
eduffield said:
Anyone who's interested in seeing what a rejected IX transaction looks like, here's an easy way.

1.) Create 2 local tDRK addresses in your wallet , addr1 and addr2
2.) Open your wallet, send a IX transaction to addr1. Make sure you pick an input using select coins and remember which input you used.
3.) Look at the transaction screen, you should see "InstantX was successful" in the details screen
4.) Shut down the wallet, restart with --zapwallettxes (hurry! do this before a new block is found)
5.) Open your wallet, send a IX transaction to addr2. Make sure you pick the SAME input using select coins.

Now, the network will resolve the conflict. The details screen should show transaction 2, but not 1. In the details screen it should say "InstantX verification in progress - 0 of 20 signatures". Soon a block will arrive and the old transaction will show up and the newer one will change to conflicted. Cool huh?

There's some more advanced methods of attacking the system, such as injecting a transaction into a block and just broadcasting it. But that's way more difficult.
Click to expand...
So this is what a rejected IX transaction looks like....

upload_2015-2-8_19-11-19.png
 
eduffield said:
I'll see what I can do. Everything else is looking really great now.
Click to expand...

Thanks.

As I suggested earlier something simple like changing the color of the icon in recent transactions may be enough. Anything that lets the user know "HEY! you just used this awesome new tech and it worked!" without having to dig around would be great. :wink:
 
noticed some conflicted transactions here that occurred the other day that Im not sure what they are. can anybody explain this?
 

Attachments

  • Capture.JPG
    Capture.JPG
    100.8 KB · Views: 270
Last edited by a moderator:
skillit said:
hey everyone I know is a bit off the topic here but im noticing something strange on my mainnet wallet
and also note* that I just send a 4 drk transaction from one wallet to my other wallet and it shows as unconfirmed and its been like that for a while now. several minutes. but anyhow if you could take a look at this transactions window and see all the grey explanation marked transactions that in the transactions details , it says conflicted. bot sure what is happening with that. maybe has something to do with darksend? something is strangeView attachment 973
Click to expand...
Zapwallettxes
 
JGCMiner said:
Hey guys, can I get a couple thousand coins?

yBdkFvwAUpW5GWtHKEjrYMTCt4r6wYqFfp
Click to expand...

Sent what I could:
Status: 0/confirmed (InstantX verification in progress - 0 of 20 signatures ), has not been successfully broadcast yetDate: 2/8/15 17:53To: JGCMiner yBdkFvwAUpW5GWtHKEjrYMTCt4r6wYqFfpDebit: -400.00 tDRKTransaction fee: -0.004 tDRKNet amount: -400.004 tDRKTransaction ID: 0b1a2dad31d26e43b0b146e8ad873b10eafb1565ca7c76f36d420438d3c17796-000


Status: 0/offline (InstantX verification failed), has not been successfully broadcast yetDate: 2/8/15 17:53To: JGCMiner yBdkFvwAUpW5GWtHKEjrYMTCt4r6wYqFfpDebit: -400.00 tDRKTransaction fee: -0.004 tDRKNet amount: -400.004 tDRKTransaction ID: 0b1a2dad31d26e43b0b146e8ad873b10eafb1565ca7c76f36d420438d3c17796-000
 
Last edited by a moderator:
DrkMiner said:
No problem...
sending another 50
Click to expand...

I also sent some. IX failed. :-(

Status: 0/offline (InstantX verification failed), has not been successfully broadcast yetDate: 2/8/15 17:52To: skillit yKeX9btuhHU6tmmoDmFGnL4YrworZXZyL2Debit: -100.00 tDRKTransaction fee: -0.001 tDRKNet amount: -100.001 tDRKTransaction ID: d8ffe54c878fb06df4284d00b1f56a4259ce012f04f15fa2e150d0a88ab81d8e-000
 
Hello.. I have my testnet3 MN running, but I need exactly 1k tdrk to y9sgCGDDFVTFrvsG44nrDidwYKVTmNBLiJ
 
moli said:
OH hold on, let me tell coingun to open it.
Click to expand...
"payout_threshold" => 50000, // payout threshold, if the faucet contains less than this, display the 'dry_faucet' message

welp! sorry about that. Lowered this to 1000. Should be online now sending out 1000 coin's per shot.
 
coingun said:
"payout_threshold" => 50000, // payout threshold, if the faucet contains less than this, display the 'dry_faucet' message

welp! sorry about that. Lowered this to 1000. Should be online now sending out 1000 coin's per shot.
Click to expand...
Don't you need to adjust this to 1001 since 1000 vins get locked unless manually unlocked due to protecting masternodes or is this no longer the case?
 
jimbit said:
Hello.. I have my testnet3 MN running, but I need exactly 1k tdrk to y9sgCGDDFVTFrvsG44nrDidwYKVTmNBLiJ
Click to expand...

@ eduffield

moo tried to send me the 1k via instantX
ON his console he had
Code: 
<moocowmoo> 0e784f7f5cce236476fac3ed461c620a0049efffa151f19a088dea3932f6934c
<moocowmoo> 5/confirmed (verified via instantx), broadcast through 28 node(s)

for a couple of minutes, I had nothing.

Code: 
ubuntu@ip-xxx:~$ darkcoind listtransactions
[
]

I think after a block was found, I had my transaction:

Code: 
<moocowmoo> Status: 6 confirmations (verified via instantx), broadcast through 28 node(s)
<moocowmoo> Date: 2/8/2015 22:04
<moocowmoo> To: y9sgCGDDFVTFrvsG44nrDidwYKVTmNBLiJ
<moocowmoo> Debit: -1000.00 tDRK
<moocowmoo> Transaction fee: -0.01 tDRK
<moocowmoo> Net amount: -1000.01 tDRK
<moocowmoo> Transaction ID: 0e784f7f5cce236476fac3ed461c620a0049efffa151f19a088dea3932f6934c-000

Code: 
 {
        "account" : "",
        "address" : "y9sgCGDDFVTFrvsG44nrDidwYKVTmNBLiJ",
        "category" : "receive",
        "amount" : 1000.00000000,
        "confirmations" : 1,
        "blockhash" : "000000032a828a70b276be2d3b3a22c76b4990d71df70acec42b89a91b0bca03",
        "blockindex" : 1,
        "blocktime" : 1423451189,
        "txid" : "0e784f7f5cce236476fac3ed461c620a0049efffa151f19a088dea3932f6934c",
        "walletconflicts" : [
        ],
        "time" : 1423451189,
        "timereceived" : 1423451202
    }
 
moli said:
So this is what a rejected IX transaction looks like....

View attachment 972
Click to expand...
I had an absolute buttload of this "conflicted" business happen while trying to mix on 0.11.0.14 on mainnet... Many hundred of them... I figured something just went all plop-dumps and waggle-sags with my wallet.dat...

Could there be a relationship?
 
Status
Not open for further replies.
Back
Top