pull down to refresh

tldr; double spending
  1. send tx1 with low fee at busy time (stays unconfirmed)
  2. tx1 appears in the mempool, receive decryption keys
  3. send tx2 with higher fee - tx1 gets invalidated
lulz
reply
That's why we say that a 0-conf transactions doesn't exist.
reply