pull down to refresh

I mean there are no public keys exposed on the blockchain. Obviously this is not a threat now, but someday it might be, and once the attack starts, everyone is going to be rushing to move (plus the attackers attempting to out-bid).

104 sats \ 2 replies \ @Scoresby 16h

Not sure what sort of wallet you are using, but most wallets generate a new key for each address. So as long as you aren't refusing addresses, your public keys shouldn't be exposed (unless it is a taproot address because taproot addresses already have exposed pubkeys). You can still spend from the wallet without exposing the public keys of your coins at rest.

reply
103 sats \ 1 reply \ @teemupleb 8h

And whatever your signing device/multisig etc. setup is, it’s good to practice sending and broadcasting, so that if you have to move funds, you know what to do. A bit like a fire evacuation drill of sorts.

reply

you can always practice with another wallet/key (same signing device). Or sign messages or sign a transaction that you don't broadcast. The idea is to just not have any public key on the blockchain associated with your main/large stash.

Everyone should be in the habit of semi-regular signing (and recovery, tx validation, address checks, etc)

reply
85 sats \ 0 replies \ @Kruw 16h

Personally, I don't think about the quantum threat at all. P2WPKH doesn't protect your coins, it just delays when the attacker learns the public key.

reply