Next scheduled rescrape ... never
Version 1
Last scraped
Scraped on 26/07/2025, 15:46:06 UTC
2. Use of One Address Per Transaction. Even with a quantum computer, a hacker will only target your funds if your public key is exposed, so by using one address per transaction, it'll limit the exposure of your public keys, thus making it impossible for your funds to be targeted.

I understand  your point but it's  not like it will limit the exposure  of your  public keys but prevents  you from losing your Sats  on a  compromisesd address. You see, there's  no way you can  prevent your public key from not beign exposed (atleast not with the current standard) so far you are going to spend the Sats.. Once spend, the public  key is exposed on-chain so receiving  on the same address again is still "address reusage"  which makes any Sats on that address vulnerable to loss if a QC can successfully  perform the attack.

In addition, your public key is also exposed when you receive (yes, you heard that right!). However, it's hashed and so far the threat cannot pose a risk /break  SHA-256 yet , it's safe to be exposed.
Original archived Re: Best Storage Method for Bitcoin in a Post-Quantum World.
Scraped on 26/07/2025, 15:41:39 UTC
2. Use of One Address Per Transaction. Even with a quantum computer, a hacker will only target your funds if your public key is exposed, so by using one address per transaction, it'll limit the exposure of your public keys, thus making it impossible for your funds to be targeted.

I understand  your point but it's  not like it will limit the exposure  of your  public keys but prevents  you from losing your Sats  on a  compromisesd address. You see, there's  no way you can  prevent your public key from not beign exposed (atleast not with the current standard) so far you are going to spend the Sats.. Once spend, the public  key is exposed on-chain so receiving  on the same address is still "address reusage"  which makes any Sats on that address vulnerable to loss if a QC can successfully  perform the attack.

In addition, your public key is also exposed when you receive (yes, you heard that right!). However, it's hashed and so far the threat cannot pose a risk /break  SHA-256 yet , it's safe to be exposed.