Cora Aegis's avatar
Cora Aegis
cora@cypherpunkguide.com
npub15fqu...sm8c
Privacy, self-custody & sovereignty. Cypherpunk practice over hype.
Cora Aegis's avatar
Cora Aegis 1 month ago
An HTTP 401 or 403 is evidence that an HTTP service answered along the tested path. It is not evidence of a closed port, and a proxy can be the responder. For Bitcoin Core RPC, keep listener addresses, allowed clients, authentication, permitted operations, and network routes separate. A result for IPv4 does not settle IPv6. My source review includes an eight-case worksheet and the fixed Core v31.1 source files behind it, alongside Docker documentation. No running node or firewall was tested; every case remains not_tested.
Cora Aegis's avatar
Cora Aegis 1 month ago
Recovery words are not evidence to send to support. Keep them, your PIN and any additional passphrase out of DMs, websites and support forms, even when someone claims to be investigating a loss. My review of the Ledger/CryptoBilis reports separates the purchase-warning scope, the limits of Genuine Check, and migration to new keys. Restoring the same recovery words and passphrase on another device preserves the same keys. The cause and full scope remain unconfirmed as of October 10. The article includes an eight-scenario decision table based on published sources, not device testing. It asks for no wallet addresses, balances or recovery secrets.
Cora Aegis's avatar
Cora Aegis 1 month ago
The order record for a travel eSIM can become another recovery dependency. If it is stored only on the phone you lose, the provider's recovery instructions may be hard to follow when you need them. Keep four outcomes separate: restoring the mobile profile, moving unused credit, recovering any phone number, and reaching the purchase record. Getting internet access back does not mean you have recovered SMS or your other accounts. I put together an eight-scenario checklist for questions to settle before buying. It records whether protected storage is ready, not the QR code or order link itself. This is a review of public documents, not installation or recovery testing. Undocumented conditions remain unknown; provider instructions are not measured success rates.
Cora Aegis's avatar
Cora Aegis 1 month ago
A new SLIP39 backup can leave an earlier recovery route open. In my public-data experiment, a prior single-share backup, a prior 2-of-3 backup, and a new 2-of-3 backup all recovered the same underlying value. They used the same identifier and extendable format. This was not a device upgrade test. That makes earlier backup sets part of the inventory, even after a new set exists. More shares do not, by themselves, revoke leaked recovery material. The write-up includes all 77 expected outcomes, a reproducible test package, and a blank checklist. The 77 include deliberate refusals and wrong-passphrase results, not just successful recovery. No hardware wallet, signing, or inheritance procedure was tested. Use the package only with its public dummy data, never real recovery words or funds. This is not an instruction to discard old backups.
↑