I did a reindex+zapwallettxes, del peers.dat and after six confirmations I felt like didn't do the things right till now(IX+DS, 1000 tDRKs IX only looked fine), but when I tried to send from the receiving address got "Insufficient funds" msg. Transactions were already confirmed 7 times. I decided to close the wallet and open it again, but when I did it, transactions were under confirmation (2/6) ..
I guess I'm just going to mix the coins I have so that tomorrow I can practice sending with DS and IX enabled. G'nite!
Yep, we did - the coinbase maturity had some sideeffects and we decided that going to 100 would be unproblematic.
Ok, the 1 input bug seems better now, but not entirely gone. bug #1 - When trying to IX, if you don't have 6 confirms on any give input, the QT will complain about "unmatching" fees. Here it is again, but with the 1001 input from the faucet, though setting amount to 1000.99 did send IX successfully And here again with another input, again conflicting change value and fees, but did send IX successfully.
I second/third that ^^^ Also, I'd still like to see something graphical or message saying a sent transaction was approved via IX on the SEND tab...
InstantX on mainnet is spectacular guys and almost everything seems to work so far and I know I'm repeating myself (from user Talon) but the crash bug system hang activated by choosing =>.1 in fee payments in the windows version is still active and does this:-- and this on in problem details when ending the program:- Problem signature: Problem Event Name: AppHangB1 Application Name: darkcoin.exe Application Version: 0.11.1.19 Application Timestamp: 52cf3800 Hang Signature: bfdf Hang Type: 0 Locale ID: 2057 Additional Hang Signature 1: bfdfa224e37d2743f3f9b1a7662b1cc4 Additional Hang Signature 2: 0b2e Additional Hang Signature 3: 0b2e164a5e80e4e27181c3a755313bdc Additional Hang Signature 4: bfdf Additional Hang Signature 5: bfdfa224e37d2743f3f9b1a7662b1cc4 Additional Hang Signature 6: 0b2e Additional Hang Signature 7: 0b2e164a5e80e4e27181c3a755313bdc Hope this helps.
This is just a record for the history of testing Darkcoin InstantX (before this thread is closed).... That I mined 3000 tDRKs on the new Testnet after Evan broke the old one!
Just for the record part 2. On the new testnet, I was up to 12000 test darkcoin on 8 heavily overclocked cores when 'somebody' (wink,wink) attacked the blockchain, forked it and caused my wallet to have random numbers and crash, on reset I had nothing, starting again, I only got upto 4,000 but they stayed in the wallet, must have been on the correct fork with no stealth attacker in the shade this time, lol.
Did that happen yesterday? I must have missed the fork because I wasn't on most of the day! lol.. You should put up a screenshot for the record... I don't think we'll walk this path again... It's been an insanely fun time!
eduffield Just wanted to share my first InstantX mainnet experience with you. I InstantX'd some coins to another account, and I thought it went well (InstantX verified). Then I booted up the receiving wallet, and the transaction was not there. I rebooted the sending wallet, and the transaction had reverted to POW transaction with no confirms. I don't know if that's a known issue or not, I will send you debug logs on request.
At least this part works as designed, when you restart your wallet InstantX transactions are reverted to POW.
OK. But the transaction should've been in the receiving wallet though, right? Or does it have to be running when the InstantX transaction is sent?
TaoOfSatoshi, I think Evan said the lock would dissappear if the wallet was reset or after 1 hour goes back to POW.
It doesn't work absolutely 100% of the time. I have had most of mine go through, but a couple fail as well. Just try it again later. Also don't forget that all of the network is not yet updated...
I just tried to InstantX a transaction on Mainnet and it failed also: At first: Status: 0/confirmed (InstantX verification in progress - 12 of 20 signatures ) Date: 2/11/2015 00:58 From: unknown To: XoNGxnL9wqgbJpQQncqtyMGaKhtJMjBZz4 (own address, label: Wallet 2) Credit: 1.00 DRK Net amount: +1.00 DRK Transaction ID: ce2cdc78932f56c06a1d919eec8fed532a979f6b7110bcc8321b25b6c14af018-000 Later: Status: 3/confirmed (InstantX verification failed) Date: 2/11/2015 00:58 From: unknown To: XoNGxnL9wqgbJpQQncqtyMGaKhtJMjBZz4 (own address, label: Wallet 2) Credit: 1.00 DRK Net amount: +1.00 DRK Transaction ID: ce2cdc78932f56c06a1d919eec8fed532a979f6b7110bcc8321b25b6c14af018-000 https://drk.mn/blocks.html shows about 37.77% Masternodes have updated to v.11.1.19. I guess we have to wait for most of them updated to have a better grasp at InstantX on Mainnet?
Yeah we are only at 46% Masternodes being updated - gotta wait until everyone updates for the network to properly service all transactions.
Yer agree it's icky, I had more success on testnet than on main net, wait until people have their masternodes updated, but its working most of the time and that pretty alrighty impressive already
Right now on Mainnet, 58.2 % of MN are at 11.1.19. I sent an InstantX transaction to myself between wallets. The trans got to 14 of 20 of IX verification and then failed. Yesterday, I tried one and it failed at 9 of 20, so getting better. Status: 2/confirmed (InstantX verification failed)Date: 2/11/2015 06:41From: unknownTo: Xccis83MLP4ijwSpP4MMTWzDYAfgBBv5UD (own address, label: MN1)Credit: 1.7310714 DRKNet amount: +1.7310714 DRKTransaction ID: 8f7db82f2473685bb2788951c952e0c4f77058197bc2b8e9a990b743b103c465-000
