To dev... concerning deposit made to Xnigma, I deposited 18101.42 octo reported as unconfirmed for 3 months. The transaction appears in both old/new wallet at first as unconfirmed/0 of 6 confirmations. Now it appears, after I emailed Xnigma, as "conflicted". Regardless my coin is in the cloud floating around or gone?
Both old/new wallets say I have 18447.66902801 coin, but try to move any and no, no, no. Again, attempted on old/new wallets and separate PCs, rebuilding data, etc.
Transaction details from wallet...
Status: conflicted
Date: 3/27/2014 23:58
To: xnigma 8TEWs43LdTt3Tvjk8kf2azE2DtKuvuj9ve
Debit: -18100.00 888
Transaction fee: -1.42 888
Net amount: -18101.42 888
Transaction ID: 9f9cab6b9878225410686bc415f0d80b8b083890dbaa2c64fc0bffd4dd27f34e-000
Xnigma never received.
Both old/new wallets say I have 18447.66902801 coin, but try to move any and no, no, no. Again, attempted on old/new wallets and separate PCs, rebuilding data, etc.
Transaction details from wallet...
Status: conflicted
Date: 3/27/2014 23:58
To: xnigma 8TEWs43LdTt3Tvjk8kf2azE2DtKuvuj9ve
Debit: -18100.00 888
Transaction fee: -1.42 888
Net amount: -18101.42 888
Transaction ID: 9f9cab6b9878225410686bc415f0d80b8b083890dbaa2c64fc0bffd4dd27f34e-000
Xnigma never received.
The Xnigma sysop may need to do the same thing.. Rebuild and reindex. There's a command in the new wallet, something like zapwallettxes or something like that. Have him try that out, surely your transaction will be found!
How about a new thought for altcoin. Me... customer. Developer... manufacturer. Exchange... vendor. Customer complains, manufacturer and vendor fix. Not fix, customer finds another product. Appreciate your advice but not looking to solve this problem myself.
But you were just told what needs to be done. You and the Xnigma admin need to reindex your wallets. You'd be surprised how often this happens with all coins - there is a reason Litecoin increased max block size in their latest release. I believe OctoCoin has an even larger max block size. Reindexing is there because sometimes your transaction isn't accepted into the block chain due to too low of fees or whatnot. The zapwallettxes thing sounds interesting. I don't know how to use it but I'd look into that. If you zap the transaction, the coins come back into your wallet and you can resend them if you like. The coins are not lost as they never even hit the main blockchain. Your wallet stored on your computer is just "confused." You can point your finger all day long but one thing I've learned is the best way to resolve an issue is to take matters into my own hands. I've had this same issue before with Doge, Litecoin, Feathercoin, and even bitcoin. The difference is that now there are more tools built into the OctoCoin wallet that will probably make it much easier. It was a freak incident and it sucks but it's not Xnigma's fault and unless you want to send the OctoCoin dev your wallet.dat file there isn't much they can do most likely. Your wallet is the only place that transaction exists.
The zapwallettxes doesn't actually work that way, but still very useful in rebuilding the tx database.. I was looking at the bitcoin changelog and looks like Octo has alot of the same functionality. Here's the most interesting snippet, for transaction-related issues:
Transaction malleability-related fixes
--------------------------------------
This release contains a few fixes for transaction ID (TXID) malleability
issues:
- -nospendzeroconfchange command-line option, to avoid spending
zero-confirmation change
- IsStandard() transaction rules tightened to prevent relaying and mining of
mutated transactions
- Additional information in listtransactions/gettransaction output to
report wallet transactions that conflict with each other because
they spend the same outputs.
- Bug fixes to the getbalance/listaccounts RPC commands, which would report
incorrect balances for double-spent (or mutated) transactions.
- New option: -zapwallettxes to rebuild the wallet's transaction information
I can confirm that it does help out. I had a couple of things stuck that I didn't know about, I ran pretty much every recovery option when I updated the pool, to be on the safe side. Hope it works out for ya!
If you're on windows, make a shortcut of octocoin-qt.exe, Right click it, choose properties, and in the "Target" box, after the file path and octocoin-qt.exe add -zapwallettxes -rescan -reindex
Save that and try once more. Hope you get your coins back!
