Bitcoin Forum

ok, so I got this tiny transaction stuck in limbo. its only 8 cents... i think it was a faucet (i click them occasionally, its not vital income by any means) but now its stuck and i have this unconfirmed (3 days now) transaction sitting in my wallet. this is the message ; Transaction rejected by our node. Reason: Transaction was previously accepted but has been pruned from our database. here---> https://blockchain.info/tx-index/68d5e07aed16334a7b6fb22d70fdbc62c42b5e3891e55bf0752d8e0b912f782e (https://blockchain.info/tx-index/68d5e07aed16334a7b6fb22d70fdbc62c42b5e3891e55bf0752d8e0b912f782e)

i understand its a dust tx and the stress test has jammed it up, its not really life or death if it ever goes through, but will it eventually? will it go back to the sender and maybe be sent again, or is it gone forever? AND will it ever disappear from my transaction history? (I'm kinda OCD and I dont like how it looks in my wallets tx history)

like i say, I'm not going to die if it never resolves, but can someone explain what happens to this tx now that it has been rejected? are the devs doing anything to clean this stuff up? does it even matter in the bigger scheme of things? just wondering (its stuff like this that reminds me of how little i understand about how bitcoin works)

Yes, bc.i cranked up the filters a notch. Shows fine on others[1].


Depends.


Its certainly not gone. Bitcoin cant just disappear.


Depends on your wallet, if you are using bitcoin core (assumption based on the section you post in) you can manually remove the TX from the wallets data with pywallet.


It mainly depends on the wallet of the sender. If they keep rebroadcasting it, it will eventually get picked up by a miner and get a confirmation. The fee is a bit low for the amount of outputs, but under "not spam" circumstances it would have confirmed after a few days. Now, if they dont rebroadcast it, the rest of the network will eventually forget about the TX and the sender is free to create a new one with the same input.


[1] e.g. here: https://www.blocktrail.com/BTC/tx/68d5e07aed16334a7b6fb22d70fdbc62c42b5e3891e55bf0752d8e0b912f782e

Ok thanks. Very helpful.
I'm assuming this is happening due to the stress test/network spam attack because I've received smaller tx than this before with no problems.
Would an increased block size prevent this type of rejected tx or would it just minimize the occurance ?

I mean, one of the things BTC boasts it is ideal for is micro transactions, but if this stuff continues (there are dozens of threads complaining of it right now) micro transactions over the block chain don't look so good.

An increased blocksize could not prevent an attack like this, but it could make it more expensive or less effective. If current blocks can clean 2000 TX at a time, 8MB blocks would be able to clean 16000 TX. Considering there are currently ~64000 TX waiting, it would be a matter of ~40 minutes to clean that up. I would also assume that bc.i would not have filtered that many TX if bigger block would be more common.

Microtransactions are indeed "endangered" by this and might become a thing of the past. The backlog requires a fee that is too high for most micro TX.

So what should happen to prevent this issue ? New version of bitcoin wallet ?

Don't create transactions which have really small, dust outputs.

Actually I dont do it, but get sometimes on my transactions this "Transaction was previously accepted but has been pruned from our database."

I think the op problem is successfully fix the issue... but the problem is the tress test or the double transaction from blockchain thats why we still getting this issue...