the change from your transaction was sent to a Native SegWit address that Trezor Suite doesn’t monitor by default. Mycelium recognized the address, but Trezor Suite didn't since it only watches specific derivation paths ( m/44'/0'/0'/0 1... SegWit P2SH-P2WPKH m/49'/0'/0'/0 3... Native SegWit P2WPKH m/84'/0'/0'/0 bc1q... ..Taproot P2TR m/86'/0'/0'/0 bc1p... ..

biggest mistake??? you being sarcastic lol... anyways, before you are done, when zaps πŸ˜„

Reply to this note

Please Login to reply.

Discussion

yes i know trezor doesnt monitor it by default.

so i activated the legacy derivation path, as I have done many times before. still nothing. then when i sent it to "myself" it became a coin join transaction some how and took 6 hours to confirm, probably because stupid fucking mycelium sets the default tx fee to 1 fucking satoshi so a new user im instructing overlooked that and freaked out causing more problems.

zaps coming, even though this is still a mystery, please hold.

no sarcasm, full honesty.

smashed my dinner plate and sent the food flying all over the kitchen this evening.

im done with everyone

sorry about the experience and for feeling that way. πŸ«‚

πŸ‘€πŸ‘€πŸ‘€πŸ‘€πŸ‘€πŸ‘€πŸ‘€πŸ˜­πŸ˜­πŸ˜­πŸ˜­πŸ˜­πŸ˜­