pull down to refresh

I've blocked out the memory of just how long I had one stuck for previously....but it was at least two months.....and I really think it was like 6 months about 8 or 9 months ago I think???? I was so "shitting my pants" and like "this is crazy, I did everything right so I wonder just how long this might take" and "wonder how I can speed this up?"
Which also coincided with mempool.space coming out with the testing of "boosting" your transaction....but I was willing to wait it out....it was a great learning experience to just pay the extra sats to ensure you don't get left out of a block for eternity???
Yea i think my last on chain fee was less than 200 sats.. if i had to wait months I'd lose my mind.
reply
0 sats \ 2 replies \ @senf 2 Feb
Why would it matter if it takes months if you're sending to cold storage where it will stay for years or decades? There are definitely cases where a transaction would need to be faster, like if you're sending it to someone else.
reply
Intellectually you are correct. As someone who has anxiety and is pretty new, it would make me terrified.
reply
0 sats \ 0 replies \ @senf 2 Feb
What can go wrong? Sats can't just disappear or get hijacked, they exist at the source or the destination always. If you're on both ends then they're always yours. There's no additional risk* with a transaction sitting in the mempool waiting to get into a block. Nothing bad can happen.
*Technically with most common address types your transaction exposes your public key, which makes a future quantum computer attack more feasible. We are a very, very long time from that being a legit concern. Taproot addresses have bare public keys that are exposed from the moment they receive sats, as an example of why that isn't a thing to worry about at the moment.
reply