Claim
Claim risk, not a procedure
A legacy P2PKH spend publishes the public key in the scriptSig as soon as the transaction is relayed. That is the low-range race surface. This page names that channel and what the confirmed chain actually shows for #66 and #69.
What this page is
Risk education. It names the publication channel and what the confirmed chain shows for #66 and #69. It does not tell you how to construct, sign, or submit a transaction.
This atlas does not accept private keys, WIF, or seed phrases, and will not ask for them. Browser tools may take public addresses or public keys only.
A private relay, miner-direct channel, or out-of-band submission is not a privacy guarantee. It is also not an inclusion or relay guarantee. This page does not name operators and does not claim any channel will succeed.
Why a public P2PKH spend is dangerous
In a legacy P2PKH spend, the unlocking script contains the signature and the public key as separate items. Observers can read that public key from the scriptSig as soon as the transaction is visible. On low ranges, a bounded discrete log against that public key can be practical. An observer who recovers the key in time can issue a conflicting spend.
What the confirmed chain shows
A public P2PKH spend publishes P in the scriptSig when it is relayed. That race surface is real. Confirmed same-day spends can still be different UTXOs. A 12-sat receive is not a conflict. Replaced competitors are not both in the best chain. The cases page keeps dated explorer facts and community stories apart.
#66
Address 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so. Multiple transactions on 12–13 September 2024. Confirmed spends that day move different UTXOs; block 861166 is a 12-sat receive, not a double-spend of the reward outpoint. Stories that a bot recovered the key after a mempool broadcast are community interpretation, plausible given scriptSig leakage, not assigned as fact here.
#69
Address 19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG. Two close confirmed spends on 2025-04-30 in blocks 894620 and 894621. Ownership of either spend is not confirmed here. The published scalar sitting 0.72 percent into the interval is not a law for other ranges.
Usual mistakes
Patterns that show up next to lost coins. None of these is a step-by-step fix.
Public mempool first
Making a P2PKH spend visible to the public network before confirmation publishes the public key in the scriptSig.
Remote key handling
Entering a live private key into a website, a rented disk, or any machine you do not control.
Residual value
Leaving value on an already-exposed key.
Repeated exposure
Repeating spends from the same exposed key and leaking more information.
Faith in a private channel
Treating any out-of-band submission as private, exclusive, or certain to confirm. It is not a privacy guarantee.