Quote
if i send bitcoins when the database is updating its sending transactions as normal
i can't do this with a "official" version of Bitcoin Core ... 
Topic: Bug in Bitcoin Core 0.9.0? - "conflicted" transactions ? (Read 6182 times)
i can't do this with a "official" version of Bitcoin Core ... 
If you send a transaction with the same sending address as the change address, then send from the output of the first transaction back to the sending address, it triggers the error as well.
iv noticed a problem with this too, if i send bitcoins when the database is updating its sending transactions as normal but setting it as conflicted and still going out of my wallet, also the dates are messed up with a transaction i sent today showing up as sent last year. losing a lot of bitcoins at the moment 
From release notes:
RPC:
- New notion of 'conflicted' transactions, reported as confirmations: -1
I would stick your address into blockchain.info and verify the balance. Then try to do a "-rescan" in the debug console of the client.
RPC:
- New notion of 'conflicted' transactions, reported as confirmations: -1
I would stick your address into blockchain.info and verify the balance. Then try to do a "-rescan" in the debug console of the client.
that is good idea and we hope that will work.
If blockchain.info is showing right ballance - you can not to worry about it - rescan should do the trick - it might take a while.
From release notes:
RPC:
- New notion of 'conflicted' transactions, reported as confirmations: -1
I would stick your address into blockchain.info and verify the balance. Then try to do a "-rescan" in the debug console of the client.
RPC:
- New notion of 'conflicted' transactions, reported as confirmations: -1
I would stick your address into blockchain.info and verify the balance. Then try to do a "-rescan" in the debug console of the client.
Today I opened Bitcoin Core to find a 0.00 BTC balance.
After initially slightly freaking out, I click the Transactions tab, and find that my transactions are there, but the status had changed to "conflicted".
This wallet has been "handed down" through the differing versions of the reference client since 2011.
The transactions are well past "confirmed", so why the "conflicted" status now?
After initially slightly freaking out, I click the Transactions tab, and find that my transactions are there, but the status had changed to "conflicted".
This wallet has been "handed down" through the differing versions of the reference client since 2011.
The transactions are well past "confirmed", so why the "conflicted" status now?
Jump to: