Ok, to me its bed time, good hunting all.I think so. According to Evan's video, he'll fix it later.
Ok, to me its bed time, good hunting all.I think so. According to Evan's video, he'll fix it later.
Ok, to me its bed time, good hunting all.
Status: 5/confirmed (verified via instantx), broadcast through 31 node(s)Ahhh... Why am I always away when the party starts?... :sad: Can I have some coins pls?
yGKU26vEFQmG35yeLHfEvJ5e8apPsc2hHX
Thanks!Darksend
Status: 5/confirmed (verified via instantx), broadcast through 31 node(s)
Date: 2/8/2015 17:43
To: UdjinM6 yGKU26vEFQmG35yeLHfEvJ5e8apPsc2hHX
Debit: -100.00 tDRK
Transaction fee: -0.01 tDRK
Net amount: -100.01 tDRK
Transaction ID: 91ddd9786b09f509de00f1c86c717518783eb1a0b5b0fa7dfd04b5f22e1b7d75-000
Please tell us what you see on your end. Is it in your available balance right away?
So I guess it's still in pending and a failed IX?Thanks!
Status: 0/confirmed (InstantX verification in progress - 11 of 20 signatures )
Date: 09.02.15 01:43
From: unknownTo: yGKU26vEFQmG35yeLHfEvJ5e8apPsc2hHX (own address, label: getixhere)
Credit: 100.00 tDRK
Net amount: +100.00 tDRK
Transaction ID: 91ddd9786b09f509de00f1c86c717518783eb1a0b5b0fa7dfd04b5f22e1b7d75-000
Would the travel from one IP to another IP have a different result though?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.
Thanks!
Status: 0/confirmed (InstantX verification in progress - 11 of 20 signatures )
Date: 09.02.15 01:43
From: unknownTo: yGKU26vEFQmG35yeLHfEvJ5e8apPsc2hHX (own address, label: getixhere)
Credit: 100.00 tDRK
Net amount: +100.00 tDRK
Transaction ID: 91ddd9786b09f509de00f1c86c717518783eb1a0b5b0fa7dfd04b5f22e1b7d75-000
Very cool!!! If you have any filled wallets from this new blockchain the faucet would love some: http://test.faucet.masternode.io address: yGANXSSKNnSGScRfA82wmXQHzwy8185rNNAnyone 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.
Would the travel from one IP to another IP have a different result though?
Status: 5/confirmed (verified via instantx), broadcast through 32 node(s)Coins please: y8h6bov6q5vsXra2Ua4eDVkoEC7tCTYTW8
Very cool!!! If you have any filled wallets from this new blockchain the faucet would love some: http://test.faucet.masternode.io address: yGANXSSKNnSGScRfA82wmXQHzwy8185rNN
yepWeird. Did you delete peers.dat and start with --reindex?
Thanks! I think all the normal utilities are now back online on the new chain. Just waiting for some mined coins to mature and I'll send those along to the faucet as well.Sent!
Stav: 5/confirmed (verified via instantx), broadcast through 26 node(s)Datum: 8. 2. 2015 23:47Pro: yGKU26vEFQmG35yeLHfEvJ5e8apPsc2hHXVýdaj: -123.456789 tDRKTransakční poplatek: -0.01 tDRKČistá částka: -123.466789 tDRKID transakce: 9bf8c4478573190bb1ac00bc254ec34aa0facd552bedce7c2efd600ddcdf6369-000yep
first one now
2/confirmed (InstantX verification failed)
another one:
Status: 0/confirmed (InstantX verification in progress - 11 of 20 signatures )
Date: 09.02.15 01:47
From: unknown
To: yGKU26vEFQmG35yeLHfEvJ5e8apPsc2hHX (own address, label: getixhere)
Credit: 123.456789 tDRK
Net amount: +123.456789 tDRK
Transaction ID: 9bf8c4478573190bb1ac00bc254ec34aa0facd552bedce7c2efd600ddcdf6369-000
EDIT: will try to delete peers.dat and -reindex again now