Topic: I Double Spent In Trezor (Read 231 times)

what you have done with your unconfirmed coin is what we called as Child Pays For Parent (CPFP) transaction
they will be confirmed eventually at the same block if your average fee rate higher than current minimum network fee rate

I have seen transactions stay in blockchain.com mempool and confirmed 3 months later (back in 2017)
like HCP said, it depends on each node's policy/setting on its own mempool
so I suggest OP to try do RBF (if enabled) or push a "double spend attempt" tx to a node that has dropped them

BTCs do not vanish just like that. You only lose your bitcoins when you send them to the wrong address or lose your private key.
If your transaction does not confirm, you will get your bitcoin back.

Usually, an unconfirmed transaction takes from 3 to 7 days to be dropped from the mempool, then the transaction will be as it never existed.

The default "expiry" time for a transaction, that is the time at which an individual node will "drop" a transaction from it's mempool, is set to 14 days for Bitcoin Core nodes. Note that this is just a default setting, and is customisable... Node owners can set whatever they like, so there is no guarantee that any given node will even drop the transaction after this time.

Now, let's assume ALL nodes use 14 days. If your transaction was "stuck" for 14 days and was then dropped by every single node... then it would be like the transaction never happened, there would be no record of it and you could simply create a new transaction spending those UTXOs and it wouldn't be rejected as being a double spend attempt as there would be no record of the original transaction.

However, it's possible that your original transaction could be rebroadcast... either by your wallet or by another node... so that it is never dropped by any nodes and remains in node mempools forever. Attempting to then send a new transaction spending those same coins would likely be rejected as a "double spend" attempt (unless using Replace-By-Fee aka "RBF" to increase the fee).

There are also situations between those two extremes where some nodes will drop it... and some won't... In this case, it's possible to attempt to create a new transaction to replace the old. The nodes that dropped your original will accept it, the ones that still have your original will not. Either one of your 2 transactions could get confirmed at this point... most likely decided by which one has the higher fee, but not guaranteed.

As a user, there is nothing you can do to influence whether any given node drops your transaction or not... there is no "cancel transaction" option with Bitcoin.

Lets assume the mempool doesn't empty and for some reason my transaction fee is not enough, will my transactions be dropped and returned to their original addresses I sent from eventually?  If that make sense.

Thank you so much I was quite worried I would lose the Bitcoin somehow with all the confusion.  I set the fee to 5 sats per byte originally so hopefully a miner finds my transaction worthy of being mined

Firstly... you didn't "double spend" in Trezor. Simply spending an unconfirmed UTXO(s) in a new transaction is NOT "double spending". Also, spending UTXOs from unconfirmed transactions is not prohibited... it just means that the 2nd transaction cannot be confirmed until the first one is confirmed. Note that this could actually occur in the same block.

For the record, I've seen "chains" of unconfirmed transactions 25 transactions long!

As for what is likely to happen to your transactions... eventually the network congestion will ease as the price has dropped a little and stabilised, so there won't be quite the number of transactions taking place as during the big pump. You can see the visualisation of the memory pool here: https://jochen-hoenicke.de/queue/#0,24h

See how the unconfirmed transactions has dropped from 70,000+ to under 20,000?

Likewise, the fee levels have dropped back down to the point where a "1 sat/vbyte" fee is enough to get into a block... so I would expect your transactions to both confirm sometime in the next 6-12 hours (if they haven't already).

I have had a problem with a set of unconfirmed transactions because I had set the fee too low.  I sent all my transactions from multiple accounts legacy and segwit on the trezor to one new account address (segwit) I had made so I can consolidate everything.  I set the fee to low and trezor estimated 20 hours for all 7 transactions on the low setting.  Well 3 days now and nothing, I tried free bitcoin accelerators but I think they are all BS. I read today in reddit somewhere that I could just send from the account that had the money in it as unconfirmed to a new address to myself on the trezor.  So I sent the funds that were unconfirmed in the account that I originally sent to, to a new account on my trezor with a high fee hoping that would work. Well it didn't and now I don't know what is going to happen. Trezor allowed me to spend unconfirmed transactions from my balance which in itself is kinda weird.  Does anyone know what is going to happen to all the original unconfirmed transactions and also the new unconfirmed transaction that I sent to myself?  Thanks in advance guys