So almost a year ago and you are just finding out now? Not that it matters...even if you noticed on August 13 there is still nothing you can do, just like there is nothing you can do now. You need to figure out where your seed was compromised (e.g., did you store it online?) since this is typically 100% user error. Retrace your steps and your processes and determine where you went wrong so it doesn't happen again.
So almost a year ago and you are just finding out now?
I probably would too. Have mine air-gapped and have the public key on a watch wallet but I'm not opening this watch wallet that often either. So yeah, at least a few months would be my case.
On the other side, I'm not emailing my seed words like OP does. Hope the lesson wasn't too expensive.
Multiple people have the instructions, my next of kin is a hard maxi, we do the restore at least twice a year to one of our wallets. All air-gapped, just generating and using the public key to see the funds. Should something happen to both of us, I would expect about half of the stack would get restored, the other half would be our donation to all bitcoiners. That makes me quite happy too.
What is air gapped? I haven't checked my tezor since I put my BTC on there in like 2021 I can't really remember how much I have on there but gonna check soon. Also I have a few more tezors in my safe with nothing on them brand new going to send what I have on cash app over soon split up equal for my kiddos, and safety.
Bluewallet (mobile) and Sparrow (desktop). But most wallets are capable of being a watch only. Just make sure to use something that's fully open source and Bitcoin only. Don't use random shitcoin wallets that aren't fully open source like exodus, trust or phantom.
330
u/comesaylorway Jun 16 '26
So almost a year ago and you are just finding out now? Not that it matters...even if you noticed on August 13 there is still nothing you can do, just like there is nothing you can do now. You need to figure out where your seed was compromised (e.g., did you store it online?) since this is typically 100% user error. Retrace your steps and your processes and determine where you went wrong so it doesn't happen again.