Update bitcoin.html
· 1 year ago
d59bdd2f734e0348596c350e2fb64e336bdc4154
Parent:
b2bf6cd19
1 file changed +525 −386
- bitcoin.html +525 −386
Diff
--- a/bitcoin.html +++ b/bitcoin.html @@ -3,33 +3,32 @@ <head> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> - <title>Bitcoin Wallet Cheatsheet - Cyberpunk Matrix Edition</title> - <meta name="description" content="Comprehensive Bitcoin wallet cheatsheet styled as a cyberpunk matrix. Covers fundamentals, types, security, operations, hardware comparisons (Trezor, Coldcard, Ledger), and advanced concepts for self-custody."> - <link rel="canonical" href="https://cheatsheets.davidveksler.com/bitcoin.html"> + <!-- Updated Metadata --> + <title>Bitcoin Wallet Cheatsheet: Secure Your Crypto (Self-Custody Guide)</title> + <meta name="description" content="Understand Bitcoin wallets, secure your keys with hardware & cold storage, and practice safe self-custody. Covers basics, security, operations, hardware comparisons (Trezor, Coldcard, Ledger), and advanced concepts."> + <link rel="canonical" href="https://cheatsheets.davidveksler.com/bitcoin.html"> <!-- Keep original if it's the authoritative source --> - <!-- Social Media Metadata (Example - Update image URL when available) --> - <meta property="og:title" content="Bitcoin Wallet Cheatsheet - Cyberpunk Matrix Edition"> - <meta property="og:description" content="Navigate Bitcoin self-custody with this cyberpunk-themed guide to wallets, security, operations, and hardware."> + <!-- Social Media Metadata (Update image URL if needed) --> + <meta property="og:title" content="Bitcoin Wallet Cheatsheet: Secure Your Crypto (Self-Custody Guide)"> + <meta property="og:description" content="Your guide to understanding Bitcoin wallets, securing your keys with hardware and cold storage, and practicing safe self-custody."> <meta property="og:type" content="article"> <meta property="og:url" content="https://cheatsheets.davidveksler.com/bitcoin.html"> - <meta property="og:image" content="https://cheatsheets.davidveksler.com/images/bitcoin-cyberpunk-og.png"> <!-- Placeholder OG image --> + <meta property="og:image" content="https://cheatsheets.davidveksler.com/images/bitcoin-og.png"> <meta property="og:image:alt" content="Cyberpunk styled diagram showing Bitcoin wallet concepts."> <meta name="twitter:card" content="summary_large_image"> - <meta name="twitter:title" content="Bitcoin Wallet Cheatsheet - Cyberpunk Matrix Edition"> - <meta name="twitter:description" content="Navigate Bitcoin self-custody with this cyberpunk-themed guide to wallets, security, operations, and hardware."> - <meta name="twitter:image" content="https://cheatsheets.davidveksler.com/images/bitcoin-cyberpunk-og.png"> <!-- Placeholder Twitter image --> + <meta name="twitter:title" content="Bitcoin Wallet Cheatsheet: Secure Your Crypto (Self-Custody Guide)"> + <meta name="twitter:description" content="Your guide to understanding Bitcoin wallets, securing your keys with hardware and cold storage, and practicing safe self-custody."> + <meta name="twitter:image" content="https://cheatsheets.davidveksler.com/images/bitcoin-og.png"> <meta name="twitter:image:alt" content="Cyberpunk styled diagram showing Bitcoin wallet concepts."> - <link href="https://cdn.jsdelivr.net/npm/[email protected]/dist/css/bootstrap.min.css" rel="stylesheet"> <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/[email protected]/font/bootstrap-icons.min.css"> - <!-- Link Fonts --> - <link rel="preconnect" href="https://fonts.googleapis.com"> - <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin> - <link href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;600&family=Fira+Code:wght@400;600&family=Orbitron:[email protected]&display=swap" rel="stylesheet"> - + <link rel="preconnect" href="https://fonts.googleapis.com"> + <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin> + <link href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;600&family=Fira+Code:wght@400;600&family=Orbitron:[email protected]&display=swap" rel="stylesheet"> <style> + /* --- CSS Styles remain unchanged as requested --- */ @keyframes subtleDataStream { 0% { background-position: 0 0; } 100% { background-position: 0 60px; } /* Vertical movement for stream */ @@ -144,6 +143,7 @@ font-size: 0.9em; vertical-align: -0.08em; margin-right: 0.4em; color: var(--btc-orange); filter: drop-shadow(0 0 8px var(--btc-orange-glow)); } + /* Updated Lead Text */ .page-header .lead { color: var(--text-secondary); font-size: 1.15rem; max-width: 800px; margin: 0.5rem auto 0 auto; text-shadow: 0 1px 2px rgba(0,0,0,0.5); @@ -184,6 +184,7 @@ /* Apply category color vars */ .info-card.btc-type-concept { --category-color: var(--btc-color-concept); --category-color-glow: var(--btc-glow-concept);} + .info-card.btc-type-intro { --category-color: var(--btc-orange); --category-color-glow: var(--btc-orange-glow);} /* Bitcoin Orange for Intro */ .info-card.btc-type-software { --category-color: var(--btc-color-hot); --category-color-glow: var(--btc-glow-hot);} .info-card.btc-type-web { --category-color: var(--btc-color-hot); --category-color-glow: var(--btc-glow-hot); filter: brightness(0.85); } .info-card.btc-type-hardware { --category-color: var(--btc-color-cold); --category-color-glow: var(--btc-glow-cold);} @@ -293,150 +294,246 @@ opacity: 0.4; animation: flowLineGradient 6s linear infinite; z-index: 1; border-radius: 1px; } - </style> </head> <body> <header class="page-header"> - <!-- Bitcoin Icon and Title --> + <!-- Updated Title --> <h1 class="display-5"> - <i class="bi bi-currency-bitcoin"></i> Bitcoin Wallet Matrix + <i class="bi bi-currency-bitcoin"></i> Bitcoin Wallet Cheatsheet </h1> - <p class="lead">Cyberpunk Protocols & Security Interfaces for Self-Custody.</p> + <!-- Updated Lead Text --> + <p class="lead">Your guide to understanding Bitcoin wallets, securing your keys with hardware & cold storage, and practicing safe self-custody.</p> </header> <div class="container" id="main-container"> <!-- ========================== --> - <!-- SECTION I: Introduction --> + <!-- NEW SECTION 0: What is Bitcoin? --> <!-- ========================== --> - <div class="schema-container cat-concept" data-section-id="section-intro"> - <h2 class="section-title" id="section-intro"><i class="bi bi-info-circle"></i> // I. System Initialization</h2> + <div class="schema-container cat-concept" data-section-id="section-what-is-bitcoin"> + <h2 class="section-title" id="section-what-is-bitcoin"><i class="bi bi-lightning-charge"></i> // 0. What is Bitcoin?</h2> <div class="row"> - <div class="col-12"> - <div class="info-card btc-type-concept" id="card-intro"> + <div class="col-md-8 offset-md-2"> + <div class="info-card btc-type-intro" id="card-what-is-btc"> <div class="card-body"> - <h5 class="text-center"><i class="bi bi-terminal-plus"></i> Purpose :: Scope :: Disclaimer</h5> + <h5 class="text-center"><i class="bi bi-info-circle-fill"></i> Bitcoin :: The Basics</h5> <div class="card-content-wrapper"> - <p class="summary">Fast-access datastream for Bitcoin wallet protocols, interfaces, OPSEC, and advanced configurations. Focus: Self-Custody.</p> - <button class="btn btn-sm details-toggle mx-auto" type="button" data-bs-toggle="collapse" data-bs-target="#collapseIntro" aria-expanded="false" aria-controls="collapseIntro"> - Access Subroutines <i class="bi bi-chevron-down"></i> + <p class="summary">Bitcoin is a <span class="term">decentralized digital currency</span> you can send directly to anyone (<span class="term">peer-to-peer</span>) without needing a bank. Transactions are recorded on a public digital ledger called the <span class="term">blockchain</span>.</p> + <button class="btn btn-sm details-toggle mx-auto" type="button" data-bs-toggle="collapse" data-bs-target="#collapseWhatIsBtc" aria-expanded="false" aria-controls="collapseWhatIsBtc"> + Core Concepts <i class="bi bi-chevron-down"></i> </button> </div> </div> - <div class="collapse collapse-content" id="collapseIntro"> - <h6>Directive: Self-Custody</h6> - <ul> - <li>Core Protocol: <strong class="critical">"Not your keys, not your coins."</strong> Third-party custodians = Counterparty Risk Vector.</li> - <li>Advantages: Sovereign control, censorship resistance.</li> - <li>Mandate: User assumes <strong class="critical">full responsibility</strong> for key/seed security.</li> - </ul> - <h6>System Scope</h6> - <p>Fundamentals (Keys, Addr, TXs), Interface Types (Hot/Cold, HW/SW), Core Operations, Security Protocols (OPSEC), Advanced Ops (Multisig, Nodes), Hardware Matrix, Threat Vectors.</p> - <h6>Legal Disclaimer</h6> - <p>Information for educational uplink only. No financial/security advisory transmitted. Protocol specifications evolve. <strong class="critical">DYOR: Verify All Data Independently.</strong></p> + <div class="collapse collapse-content" id="collapseWhatIsBtc"> + <h6>Key Characteristics:</h6> <ul> - <li><strong>Primary Node:</strong> <a href="https://bitcoin.org/en/getting-started" target="_blank" rel="noopener noreferrer">Bitcoin.org - Genesis Block</a></li> + <li><strong>Decentralized:</strong> No single company, country, or person controls it. Run by a global network of computers.</li> + <li><strong>Peer-to-Peer:</strong> Transactions happen directly between users.</li> + <li><strong>Blockchain:</strong> A transparent, shared, and immutable (unchangeable) record of all transactions.</li> + <li><strong>Limited Supply:</strong> Only 21 million bitcoin will ever exist, making it scarce.</li> + <li><strong>Requires Keys:</strong> To own and control Bitcoin, you need special digital keys (explained next).</li> </ul> + <h6>Learn More:</h6> + <ul> + <li><strong>Official Starting Point:</strong> <a href="https://bitcoin.org/en/getting-started" target="_blank" rel="noopener noreferrer">Bitcoin.org - Getting Started</a></li> + </ul> </div> </div> </div> </div> <!-- /.row --> </div> <!-- /.schema-container --> - - <!-- ================================= --> - <!-- SECTION II: Wallet Fundamentals --> - <!-- ================================= --> - <div class="schema-container cat-concept" data-section-id="section-fundamentals"> - <h2 class="section-title" id="section-fundamentals"><i class="bi bi-braces-asterisk"></i> // II. Core Protocols</h2> + <!-- ========================== --> + <!-- UPDATED SECTION I: Introduction --> + <!-- ========================== --> + <div class="schema-container cat-concept" data-section-id="section-intro"> + <h2 class="section-title" id="section-intro"><i class="bi bi-terminal-plus"></i> // I. Understanding Bitcoin Wallets</h2> <div class="row"> - <div class="col-lg-4 col-md-6"> + <div class="col-lg-6 col-md-6"> <div class="info-card btc-type-concept" id="card-what-is-wallet"> <div class="card-body"> - <h5><i class="bi bi-bounding-box-circles"></i> Interface Definition</h5> + <h5><i class="bi bi-bounding-box-circles"></i> What is a Bitcoin Wallet?</h5> + <div class="card-content-wrapper"> + <p class="summary">It's software or hardware that manages your secret <span class="term">private keys</span>. These keys are needed to access and spend your Bitcoin. <strong class="critical">The wallet itself doesn't store Bitcoin</strong>; it stores the keys that control your funds on the blockchain.</p> + <!-- Simple concept, less need for collapse --> + </div> + </div> + </div> + </div> + <div class="col-lg-6 col-md-6"> + <div class="info-card btc-type-concept" id="card-self-custody"> + <div class="card-body"> + <h5 class="text-center"><i class="bi bi-shield-check"></i> Self-Custody :: Your Keys, Your Bitcoin</h5> <div class="card-content-wrapper"> - <p class="summary">Software/Hardware <span class="term">interface</span> managing cryptographic <span class="term">keys</span>. Enables TX signing & balance lookup. Keys, not coins, are stored.</p> + <p class="summary">The core principle: <strong class="critical">"Not your keys, not your coins."</strong> This cheatsheet focuses on <span class="term">self-custody</span>, where YOU control your private keys, not a third-party exchange or service. This gives you full control but also full responsibility.</p> + <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSelfCustody" aria-expanded="false" aria-controls="collapseSelfCustody"> + Why Self-Custody? <i class="bi bi-chevron-down"></i> + </button> </div> </div> + <div class="collapse collapse-content" id="collapseSelfCustody"> + <h6>Why Control Your Own Keys?</h6> + <ul> + <li><strong class="pros">Sovereign Control:</strong> Only you can access or move your funds. No third party can freeze or lose them.</li> + <li><strong class="pros">Censorship Resistance:</strong> No one can stop you from sending or receiving transactions.</li> + <li><strong class="cons">Full Responsibility:</strong> If you lose your keys (or seed phrase), your Bitcoin is <strong class="critical">permanently lost</strong>. You are your own bank.</li> + </ul> + <h6>Cheatsheet Scope:</h6> + <p>This guide covers wallet basics, types (Hot/Cold), secure operations, and advanced topics, focusing on tools and practices for effective self-custody.</p> + <h6>Legal Disclaimer:</h6> + <p>Educational information only. Not financial or security advice. Bitcoin technology evolves. <strong class="critical">Do Your Own Research (DYOR) and verify all information independently.</strong></p> + </div> </div> </div> + </div> <!-- /.row --> + </div> <!-- /.schema-container --> + + <!-- ================================================== --> + <!-- NEW SECTION II: Protecting Your Bitcoin (Cold Storage / HW) --> + <!-- ================================================== --> + <div class="schema-container cat-cold" data-section-id="section-protection"> + <h2 class="section-title" id="section-protection"><i class="bi bi-snow3"></i> // II. Protecting Your Bitcoin: Cold Storage & Hardware Wallets</h2> + <div class="row"> + <div class="col-lg-6 col-md-6"> + <div class="info-card btc-type-hardware" id="card-cold-storage-intro"> + <div class="card-body"> + <h5><i class="bi bi-shield-shaded"></i> Cold Storage :: Keeping Keys Offline</h5> + <div class="card-content-wrapper"> + <p class="summary"><span class="term">Cold Storage</span> means keeping your critical private keys completely offline, isolated from the internet. This dramatically reduces the risk of online theft (hacking, malware).</p> + <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseColdStorageIntro" aria-expanded="false" aria-controls="collapseColdStorageIntro"> + Why Offline? <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseColdStorageIntro"> + <h6>The Security Advantage:</h6> + <ul> + <li><strong class="pros">Online Threat Immunity:</strong> Hackers cannot access keys that are never connected to the internet.</li> + <li><strong class="pros">Malware Resistance:</strong> Viruses on your computer or phone cannot steal offline keys.</li> + <li><strong class="term">Best Practice:</strong> Considered the most secure way to store significant amounts of Bitcoin.</li> + </ul> + </div> + </div> + </div> + <div class="col-lg-6 col-md-6"> + <div class="info-card btc-type-hardware" id="card-hardware-intro"> + <div class="card-body"> + <h5><i class="bi bi-memory"></i> Hardware Wallets :: The Key to Cold Storage</h5> + <div class="card-content-wrapper"> + <p class="summary"><span class="term">Hardware Wallets</span> are small, specialized physical devices designed to keep your private keys secure and offline (<span class="term">cold storage</span>). They sign transactions internally, never exposing keys to your connected computer/phone.</p> + <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseHardwareIntro" aria-expanded="false" aria-controls="collapseHardwareIntro"> + How They Work <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseHardwareIntro"> + <h6>Core Functionality:</h6> + <ul> + <li><strong class="pros">Key Isolation:</strong> Private keys are generated and stored on the device, never leaving it.</li> + <li><strong class="pros">Secure Signing:</strong> Transactions are confirmed on the device's trusted screen and signed internally. Only the signed transaction (safe to share) is sent back to the computer/phone.</li> + <li><strong class="pros">Physical Security:</strong> Protected by PIN codes and often tamper-evident features.</li> + <li><strong class="term">Standard Recommendation:</strong> The most popular and recommended method for achieving secure cold storage for most users.</li> + </ul> + <h6>Common Examples:</h6> + <ul> + <li><a href="#card-compare-trezor">Trezor</a>, <a href="#card-compare-coldcard">Coldcard</a>, <a href="#card-compare-ledger">Ledger</a>, <a href="#card-compare-bitbox">BitBox02</a> (More details in Section VIII).</li> + </ul> + </div> + </div> + </div> + </div> <!-- /.row --> + </div> <!-- /.schema-container --> + + + <!-- ================================= --> + <!-- UPDATED SECTION III: Wallet Fundamentals --> + <!-- ================================= --> + <div class="schema-container cat-concept" data-section-id="section-fundamentals"> + <h2 class="section-title" id="section-fundamentals"><i class="bi bi-braces-asterisk"></i> // III. Wallet Fundamentals</h2> + <div class="row"> + <!-- Keys --> <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-concept" id="card-keys"> <div class="card-body"> - <h5><i class="bi bi-key-fill"></i> Key Pairs :: Asymmetric Crypto</h5> + <h5><i class="bi bi-key-fill"></i> Private & Public Keys</h5> <div class="card-content-wrapper"> - <p class="summary"><span class="term">Private Key:</span> Secret. Signs TXs. <strong class="critical">[GUARD]</strong>. <span class="term">Public Key:</span> Derives Addr. Shareable.</p> + <p class="summary"><span class="term">Private Key:</span> Your secret password. Used to sign (authorize) transactions. <strong class="critical">Guard it like gold.</strong> <span class="term">Public Key:</span> Derived from the private key. Used to create receiving addresses. Safe to share.</p> + <!-- Simple enough, no collapse needed --> </div> </div> </div> </div> + <!-- Addresses --> <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-concept" id="card-addresses"> <div class="card-body"> - <h5><i class="bi bi-geo-alt-fill"></i> Addresses :: Receiving Nodes</h5> + <h5><i class="bi bi-geo-alt-fill"></i> Bitcoin Addresses</h5> <div class="card-content-wrapper"> - <p class="summary">Receiving Identifiers. Formats: Legacy(<code>1</code>), Nested SegWit(<code>3</code>), <span class="term">Native SegWit</span>(<code>bc1q</code>), <span class="term">Taproot</span>(<code>bc1p</code>).</p> + <p class="summary">Identifiers used to receive Bitcoin, derived from your public key. Think of them like email addresses for money. Best practice: use a new address for each transaction.</p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseAddresses" aria-expanded="false" aria-controls="collapseAddresses"> - Format Specs <i class="bi bi-chevron-down"></i> + Address Formats <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseAddresses"> - <h6>Address Type Analysis</h6> + <h6>Common Address Formats (Look at the starting characters):</h6> <ul> - <li><code>Legacy (P2PKH)</code>: Max compatibility, highest fees.</li> - <li><code>Nested SegWit (P2SH)</code>: Wrapped SegWit, better fees. Bridge format.</li> - <li><code>Native SegWit (Bech32)</code>: <strong class="term">Lowest fees</strong>, best error check. Current standard.</li> - <li><code>Taproot (Bech32m)</code>: Latest upgrade. Privacy/scripting benefits. Future standard.</li> + <li><code>Legacy (starts with '1')</code>: Oldest type, highest transaction fees, maximum compatibility.</li> + <li><code>Nested SegWit (starts with '3')</code>: Better fees than Legacy, good compatibility.</li> + <li><code>Native SegWit (starts with 'bc1q')</code>: <strong class="term">Current standard. Lowest fees</strong>, good error detection. Recommended.</li> + <li><code>Taproot (starts with 'bc1p')</code>: Newest type. Offers potential future privacy and efficiency benefits.</li> </ul> - <p><strong class="term">OPSEC: Generate new address per TX</strong> for privacy enhancement.</p> + <p><strong class="term">Privacy Tip: Generate and use a fresh address for every payment you receive.</strong> Most wallets do this automatically.</p> </div> </div> </div> - <div class="col-lg-6 col-md-6"> + <!-- Seed Phrase --> + <div class="col-lg-4 col-md-12"> {/* Made wider for emphasis */} <div class="info-card btc-type-concept" id="card-seed-phrase"> <div class="card-body"> - <h5><i class="bi bi-journal-code"></i> Seed Phrase :: Genesis Code (BIP-39)</h5> + <h5><i class="bi bi-journal-code"></i> Seed Phrase :: Master Backup</h5> <div class="card-content-wrapper"> - <p class="summary">12/24 word <span class="term">mnemonic</span> -> Master Key. <strong class="critical">[ULTIMATE BACKUP PROTOCOL]</strong>. (<a href="https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki" target="_blank" rel="noopener noreferrer">BIP-39 Spec</a>).</p> + <p class="summary">A list of 12 or 24 words that acts as the <strong class="critical">master backup</strong> for your entire wallet. If your device is lost or broken, the seed phrase lets you recover <span class="term">all</span> your keys and funds.</p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSeed" aria-expanded="false" aria-controls="collapseSeed"> - Decode & Derive <i class="bi bi-chevron-down"></i> + Critical Details <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseSeed"> - <h6>Critical Function & Derivation</h6> + <h6>Understanding Your Seed Phrase (BIP-39):</h6> <ul> - <li><strong class="critical">Function:</strong> Sole recovery vector post-device failure/loss.</li> - <li><strong>Origin:</strong> Secure generation via wallet RNG (offline preferred).</li> - <li><strong>Derivation Path:</strong> Uses <span class="term">BIP-32</span> + <span class="term">BIP-44/84/86</span> standards to generate key hierarchy.</li> - <li><code>Seed -> Master Key -> Tree of Keys -> Addresses</code></li> - <li><strong>Tool (Offline ONLY):</strong> <a href="https://iancoleman.io/bip39/" target="_blank" rel="noopener noreferrer">Ian Coleman BIP39</a> <strong class="critical">[WARNING: Extreme caution required if used]</strong></li> + <li><strong class="critical">Function:</strong> The ONLY way to restore your wallet if your device fails or is lost. It IS your Bitcoin if the device is gone.</li> + <li><strong>Generation:</strong> Created securely by your wallet (ideally offline by a hardware wallet).</li> + <li><strong>Derivation:</strong> The seed phrase mathematically generates your master private key, which then generates all your individual private keys and addresses (<span class="term">BIP-32</span>).</li> + <li><code>Seed -> Master Key -> All Private Keys -> All Addresses</code></li> + <li><strong class="critical">Security: Treat your seed phrase with EXTREME care. Anyone who sees it can steal ALL your funds. See Section VI for security rules.</strong></li> + <li><strong>Standard:</strong> Based on the <a href="https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki" target="_blank" rel="noopener noreferrer">BIP-39</a> standard.</li> </ul> </div> </div> </div> - <div class="col-lg-6 col-md-6"> + <!-- Transactions --> + <div class="col-lg-6 col-md-6"> {/* Took remaining space */} <div class="info-card btc-type-concept" id="card-transactions"> <div class="card-body"> - <h5><i class="bi bi-arrows-fullscreen"></i> TX Flow :: Network Propagation</h5> + <h5><i class="bi bi-arrows-fullscreen"></i> How Transactions Work</h5> <div class="card-content-wrapper"> - <p class="summary">Consume <span class="term">UTXOs</span> -> Create Outputs. Attach <span class="term">fee (sat/vB)</span>. Broadcast to <span class="term">Mempool</span> -> Await Mining Confirmation.</p> + <p class="summary">Sending Bitcoin involves using your private key to sign a message that transfers ownership of specific Bitcoin amounts (<span class="term">UTXOs</span>) to a recipient's address. You include a <span class="term">fee</span> to incentivize miners to include it in the blockchain.</p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseTx" aria-expanded="false" aria-controls="collapseTx"> - Lifecycle Analysis <i class="bi bi-chevron-down"></i> + Transaction Lifecycle <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseTx"> - <h6>Transaction Lifecycle:</h6> + <h6>Transaction Flow:</h6> <ul> - <li><span class="term">UTXOs:</span> Unspent outputs; represent ownable BTC units.</li> - <li><span class="term">Inputs/Outputs:</span> TX consumes UTXOs, creates new ones (recipient + change).</li> - <li><span class="term">Fees (sat/vB):</span> Market-based incentive for miners; size-dependent.</li> - <li><span class="term">Mempool:</span> P2P queue for unconfirmed TXs.</li> - <li><span class="term">Confirmations:</span> Block inclusion = finality increases. (6+ = standard security).</li> - <li><strong>Monitor Node:</strong> <a href="https://mempool.space/" target="_blank" rel="noopener noreferrer">mempool.space</a></li> + <li><span class="term">UTXOs (Unspent Transaction Outputs):</span> Think of these as individual "coins" or "notes" of Bitcoin in your wallet. A transaction spends one or more UTXOs.</li> + <li><span class="term">Inputs & Outputs:</span> Your transaction uses your UTXOs as inputs and creates new UTXOs as outputs (one for the recipient, possibly one back to you as change).</li> + <li><span class="term">Transaction Fee (sat/vB):</span> A small amount paid to miners, based on the data size of your transaction (in virtual Bytes) and network congestion. Higher fees usually mean faster confirmation. Measured in <span class="term">satoshis</span> per virtual byte.</li> + <li><span class="term">Mempool:</span> A waiting area where transactions sit before being picked up by miners.</li> + <li><span class="term">Confirmations:</span> When a miner includes your transaction in a block added to the blockchain, it gets one confirmation. More confirmations increase security (6+ is often considered very secure).</li> + <li><strong>Track Transactions:</strong> Use a <span class="term">Block Explorer</span> like <a href="https://mempool.space/" target="_blank" rel="noopener noreferrer">mempool.space</a></li> </ul> </div> </div> @@ -445,37 +542,33 @@ </div> <!-- /.schema-container --> <!-- ================================ --> - <!-- SECTION III: Types of Wallets --> + <!-- UPDATED SECTION IV: Types of Wallets --> <!-- ================================ --> <div class="schema-container" data-section-id="section-types"> <!-- Hot Wallets Sub-section --> - <h2 class="section-title cat-hot" id="section-hot-wallets"><i class="bi bi-fire"></i> // III.A Hot Interfaces :: ONLINE/NETWORKED</h2> + <h2 class="section-title cat-hot" id="section-hot-wallets"><i class="bi bi-fire"></i> // IV.A Hot Wallets :: ONLINE / CONNECTED</h2> <div class="row"> <div class="col-lg-6 col-md-6"> <div class="info-card btc-type-software" id="card-software"> <div class="card-body"> - <h5><i class="bi bi-display"></i> Software Terminals</h5> + <h5><i class="bi bi-display"></i> Software Wallets (Desktop/Mobile)</h5> <div class="card-content-wrapper"> - <p class="summary">Applications (Desktop/Mobile). Keys reside on networked device = <strong class="cons">High Attack Surface</strong>. Suitable for operational funds only.</p> + <p class="summary">Apps installed on your computer or phone. <strong class="term">Hot Wallets</strong> because your private keys reside on a device connected to the internet. Convenient for frequent use, but <strong class="cons">higher risk</strong> due to online exposure.</p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSoftware" aria-expanded="false" aria-controls="collapseSoftware"> - Variants & Protocols <i class="bi bi-chevron-down"></i> + Types & Risks <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseSoftware"> - <h6>Custody Protocol Distinction:</h6> - <ul> - <li><strong class="pros">Non-Custodial:</strong> User controls keys/seed. <strong class="term">[Self-Sovereign]</strong></li> - <li><strong class="cons">Custodial:</strong> Third-party controls keys. <strong class="term">[Counterparty Risk]</strong></li> - </ul> - <h6>Non-Custodial Access Nodes:</h6> + <h6>Custody Type Matters:</h6> <ul> - <li>Desktop: <code>Electrum</code>, <code>Sparrow</code>, <code>Specter</code></li> - <li>Mobile: <code>BlueWallet</code>, <code>Muun</code>, <code>Samourai</code>(*Note Legal Status*)</li> + <li><strong class="pros">Non-Custodial:</strong> YOU control the keys/seed phrase. Examples: <a href="https://electrum.org/" target="_blank" rel="noopener noreferrer">Electrum</a>, <a href="https://sparrowwallet.com/" target="_blank" rel="noopener noreferrer">Sparrow</a> (Desktop); <a href="https://bluewallet.io/" target="_blank" rel="noopener noreferrer">BlueWallet</a>, <a href="https://muun.com/" target="_blank" rel="noopener noreferrer">Muun</a> (Mobile). <strong class="term">[Recommended Hot Wallet Type]</strong></li> + <li><strong class="cons">Custodial:</strong> A third party (like an exchange app) holds the keys for you. Easier to start, but you don't truly own the Bitcoin (<span class="term">Counterparty Risk</span>). Not covered in detail here.</li> </ul> - <h6>Threat Assessment:</h6> + <h6>Threats to Hot Wallets:</h6> <ul> - <li><strong class="cons">Vulnerable to:</strong> Malware, Phishing, OS Exploits, Physical Device Compromise.</li> + <li><strong class="cons">Vulnerable to:</strong> Malware (viruses, keyloggers), Phishing attacks, OS security holes, physical theft of the device.</li> + <li><strong class="term">Best Use:</strong> Small amounts for daily spending, like cash in your physical wallet. Not for large savings.</li> </ul> </div> </div> @@ -483,9 +576,10 @@ <div class="col-lg-6 col-md-6"> <div class="info-card btc-type-web" id="card-web"> <div class="card-body"> - <h5><i class="bi bi-globe2"></i> Web Interfaces</h5> + <h5><i class="bi bi-globe2"></i> Web Wallets</h5> <div class="card-content-wrapper"> - <p class="summary">Browser-based access nodes. Often custodial. <strong class="cons">EXTREME RISK PROFILE</strong> via XSS, Phishing, Browser Malware.</p> + <p class="summary">Accessed through your web browser. Often custodial (run by a website). <strong class="cons">Generally Considered VERY RISKY</strong> due to phishing, malicious browser extensions, and website hacks. Mostly avoided for self-custody.</p> + <!-- Generally discouraged, simple explanation sufficient --> </div> </div> </div> @@ -493,32 +587,31 @@ </div> <!-- /.row --> <!-- Cold Wallets Sub-section --> - <h2 class="section-title cat-cold" id="section-cold-wallets" style="margin-top: 2.5rem;"><i class="bi bi-shield-shaded"></i> // III.B Cold Storage :: OFFLINE/ISOLATED</h2> + <h2 class="section-title cat-cold" id="section-cold-wallets" style="margin-top: 2.5rem;"><i class="bi bi-shield-shaded"></i> // IV.B Cold Wallets :: OFFLINE / ISOLATED</h2> <div class="row"> <div class="col-lg-4 col-md-6"> - <div class="info-card btc-type-hardware" id="card-hardware"> + <div class="info-card btc-type-hardware" id="card-hardware-detail"> {/* Changed ID to avoid conflict */} <div class="card-body"> - <h5><i class="bi bi-memory"></i> Hardware Modules</h5> + <h5><i class="bi bi-memory"></i> Hardware Wallets (Recap)</h5> <div class="card-content-wrapper"> - <p class="summary">Dedicated crypto-processors. Key isolation from network. <strong class="pros">Maximum Online Threat Resistance.</strong></p> - <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseHardware" aria-expanded="false" aria-controls="collapseHardware"> - Specs & Examples <i class="bi bi-chevron-down"></i> + <p class="summary">Dedicated physical devices keeping keys offline. <strong class="pros">The gold standard for secure cold storage.</strong> Sign transactions securely without exposing keys. (See Section II for intro).</p> + <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseHardwareDetail" aria-expanded="false" aria-controls="collapseHardwareDetail"> + Benefits & Tradeoffs <i class="bi bi-chevron-down"></i> </button> </div> </div> - <div class="collapse collapse-content" id="collapseHardware"> - <h6>Core Functionality:</h6> + <div class="collapse collapse-content" id="collapseHardwareDetail"> + <h6>Key Advantages:</h6> <ul> - <li><strong class="pros">Advantage:</strong> Private keys never exposed to connected (potentially compromised) host.</li> - <li><strong class="pros">Physical Security:</strong> PIN protection, tamper-evidence features.</li> - <li><strong class="cons">Considerations:</strong> Initial cost, physical security needs.</li> + <li><strong class="pros">Maximum Security:</strong> Private keys never touch your internet-connected computer/phone.</li> + <li><strong class="pros">Malware/Virus Immune:</strong> Designed to resist threats that affect software wallets.</li> + <li><strong class="pros">Secure Confirmation:</strong> Lets you physically verify transaction details on its screen before approving.</li> </ul> - <h6>Example Modules:</h6> - <ul> - <li><a href="https://trezor.io/" target="_blank" rel="noopener noreferrer">Trezor</a> (T/Safe 3)</li> - <li><a href="https://coldcard.com/" target="_blank" rel="noopener noreferrer">Coldcard</a> (Mk4/Q1)</li> - <li><a href="https://www.ledger.com/" target="_blank" rel="noopener noreferrer">Ledger</a> (Nano/Stax)</li> - <li>... (See Section VII for Matrix)</li> + <h6>Considerations:</h6> + <ul> + <li><strong class="cons">Cost:</strong> They are physical devices you need to purchase.</li> + <li><strong class="cons">Physical Security:</strong> Needs to be kept safe from physical theft or damage (though the PIN protects it, and the seed phrase is the ultimate backup).</li> + <li><strong class="term">Examples:</strong> <a href="#card-compare-trezor">Trezor</a>, <a href="#card-compare-coldcard">Coldcard</a>, <a href="#card-compare-ledger">Ledger</a>. (Comparison in Section VIII).</li> </ul> </div> </div> @@ -526,52 +619,52 @@ <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-paper" id="card-paper"> <div class="card-body"> - <h5><i class="bi bi-journal"></i> Paper Storage Unit</h5> + <h5><i class="bi bi-journal"></i> Paper Wallets</h5> <div class="card-content-wrapper"> - <p class="summary">Physical key printout. <strong class="cons">Obsolete / High Risk Profile.</strong> Complex spending, fragile medium.</p> + <p class="summary">Printing your private and public keys directly onto paper. <strong class="cons">Largely Obsolete & High Risk.</strong> Difficult to use safely, easy to damage or lose.</p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapsePaper" aria-expanded="false" aria-controls="collapsePaper"> - Threat Analysis <i class="bi bi-chevron-down"></i> + Why Avoid Them? <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapsePaper"> - <h6>Inherent Vulnerabilities:</h6> + <h6>Major Drawbacks:</h6> <ul> - <li><strong class="cons">Spending Complexity:</strong> Partial spends difficult/unsafe (key exposure).</li> - <li><strong class="cons">Physical Fragility:</strong> Susceptible to fire, water, decay, accidental damage.</li> - <li><strong class="cons">Generation Risk:</strong> Requires secure, air-gapped generation environment.</li> - <li><strong class="cons">Discovery Risk:</strong> Easily lost, stolen, or viewed accidentally.</li> + <li><strong class="cons">Spending is Hard & Risky:</strong> Importing the private key into a software wallet exposes it online, defeating the "cold" purpose. Spending partial amounts is complex.</li> + <li><strong class="cons">Fragile:</strong> Easily destroyed by fire, water, tearing, or fading ink.</li> + <li><strong class="cons">Difficult to Generate Securely:</strong> Requires specialized offline procedures to avoid malware during creation.</li> + <li><strong class="cons">Easily Compromised:</strong> If someone sees or copies the paper, funds can be stolen.</li> </ul> - <p>Modern hardware wallets offer superior security and usability.</p> + <p><strong class="critical">Recommendation: Use a hardware wallet instead for much better security and usability.</strong></p> </div> </div> </div> <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-airgap" id="card-airgap"> <div class="card-body"> - <h5><i class="bi bi-exclude"></i> Air-Gapped Systems</h5> + <h5><i class="bi bi-exclude"></i> Air-Gapped Setups</h5> <div class="card-content-wrapper"> - <p class="summary">Network-isolated signer + Online watch-interface. Data relay via SD/QR (<span class="term">PSBT</span>). <strong class="pros">Extreme Network Isolation.</strong></p> + <p class="summary">Using a completely offline device (like a dedicated computer or certain hardware wallets) to sign transactions. Data is transferred via mediums like SD cards or QR codes (<span class="term">PSBT</span> standard). <strong class="pros">Maximum network isolation.</strong></p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseAirgap" aria-expanded="false" aria-controls="collapseAirgap"> - Protocol & Tradeoffs <i class="bi bi-chevron-down"></i> + Process & Tradeoffs <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseAirgap"> - <h6>Operational Protocol:</h6> + <h6>How it Works (Simplified):</h6> <ol> - <li>Generate unsigned TX (<span class="term">PSBT</span>) on online interface.</li> - <li>Transfer PSBT (SD/QR) to offline signing module.</li> - <li>Authorize/Sign PSBT on secure offline module.</li> - <li>Transfer signed PSBT back to online interface.</li> - <li>Broadcast TX to network.</li> + <li>Create an unsigned transaction (<span class="term">PSBT</span>) on an online "watch-only" wallet.</li> + <li>Transfer the PSBT file/QR code to the offline signing device.</li> + <li>Sign the transaction securely on the offline device.</li> + <li>Transfer the signed PSBT back to the online device.</li> + <li>Broadcast the signed transaction to the Bitcoin network.</li> </ol> - <h6>Tradeoffs:</h6> + <h6>Pros & Cons:</h6> <ul> - <li><strong class="pros">Advantage:</strong> Maximum immunity to online malware/network attacks.</li> - <li><strong class="cons">Disadvantage:</strong> Increased operational complexity, potential risks via transfer medium (SD card malware - less common for PSBTs).</li> + <li><strong class="pros">Benefit:</strong> Eliminates almost all risk from online malware or network attacks on the signing keys.</li> + <li><strong class="cons">Drawback:</strong> More complex workflow than standard hardware wallets. Potential (low) risk if the transfer medium (e.g., SD card) is compromised, though PSBTs mitigate this somewhat.</li> </ul> - <p>Examples: <code>Coldcard</code>, <code>Seedsigner</code>.</p> + <p>Often used for very high security needs. Hardware wallets like <a href="#card-compare-coldcard">Coldcard</a> or DIY options like <a href="#card-compare-seedsigner">Seedsigner</a> specialize in this.</p> </div> </div> </div> @@ -580,31 +673,37 @@ <!-- ============================== --> - <!-- SECTION IV: Core Operations --> + <!-- UPDATED SECTION V: Core Operations --> <!-- ============================== --> <div class="schema-container cat-operations" data-section-id="section-operations"> - <h2 class="section-title" id="section-operations"><i class="bi bi-gear-wide-connected"></i> // IV. Core Operations</h2> + <h2 class="section-title" id="section-operations"><i class="bi bi-gear-wide-connected"></i> // V. Core Wallet Operations</h2> <div class="row"> <div class="col-lg-6 col-md-6"> <div class="info-card btc-type-operation" id="card-op-setup"> <div class="card-body"> - <h5><i class="bi bi-motherboard-fill"></i> Initialization Sequence</h5> + <h5><i class="bi bi-motherboard-fill"></i> Wallet Setup & Backup</h5> <div class="card-content-wrapper"> - <p class="summary">Secure seed generation *on device*. <strong class="critical">Backup seed (offline, steel). VERIFY BACKUP.</strong> Set strong credentials.</p> + <p class="summary">Generate your seed phrase securely (<strong class="term">best done on a hardware wallet</strong>). <strong class="critical">Write down the seed phrase accurately. Store it offline & safely. VERIFY your backup.</strong> Set a strong device PIN.</p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseOpSetup" aria-expanded="false" aria-controls="collapseOpSetup"> - Protocol Steps <i class="bi bi-chevron-down"></i> + Setup Checklist <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseOpSetup"> - <h6>Initialization Protocol:</h6> + <h6>Initialization Checklist:</h6> <ol> - <li>Firmware Verification/Installation (HW wallets).</li> - <li>Secure Seed Phrase Generation (Device RNG).</li> - <li><strong class="critical">Seed Phrase Backup:</strong> Accurate transcription, secure offline storage (e.g., <a href="https://seedplate.com/" target="_blank" rel="noopener noreferrer">SeedPlate</a>, <a href="https://cryptosteel.com/" target="_blank" rel="noopener noreferrer">Cryptosteel</a>).</li> - <li><strong class="critical">Backup Verification:</strong> Mandatory re-entry or check routine *before* receiving funds.</li> - <li>Set Strong PIN / Password.</li> - <li>Optional: Configure BIP-39 Passphrase (Advanced).</li> + <li><strong>Hardware Wallet Prep:</strong> Verify device integrity (tamper seals), install official firmware if needed.</li> + <li><strong>Seed Generation:</strong> Let the wallet generate a new seed phrase for you.</li> + <li><strong class="critical">Seed Phrase Backup:</strong> + <ul> + <li>Write words down CLEARLY and IN ORDER. Double-check spelling.</li> + <li>Store OFFLINE ONLY. <strong class="term">Metal backups (steel plates)</strong> resist fire/water. See Section VI.</li> + <li><strong class="critical">NEVER store digitally (photo, file, password manager).</strong></li> + </ul> + </li> + <li><strong class="critical">Backup Verification:</strong> Use the wallet's function to confirm your written backup is correct *before sending any funds to the wallet*.</li> + <li><strong>Set Strong PIN/Password:</strong> Protects the device itself.</li> + <li><strong>(Advanced) Passphrase:</strong> Consider adding a BIP-39 Passphrase later for extra security (see Section VII).</li> </ol> </div> </div> @@ -612,9 +711,9 @@ <div class="col-lg-6 col-md-6"> <div class="info-card btc-type-operation" id="card-op-receive"> <div class="card-body"> - <h5><i class="bi bi-download"></i> Receive Operation</h5> + <h5><i class="bi bi-download"></i> Receiving Bitcoin</h5> <div class="card-content-wrapper"> - <p class="summary">Generate fresh address. <strong class="critical">VERIFY address on HW Trusted Display</strong> vs. host screen. Share Addr/QR.</p> + <p class="summary">Generate a fresh receiving address in your wallet. <strong class="critical">If using a hardware wallet, ALWAYS verify the address shown on your computer/phone matches the address shown on the hardware wallet's trusted screen.</strong> Share the verified address/QR code.</p> <!-- Simple operation, less need for collapse --> </div> </div> @@ -623,23 +722,23 @@ <div class="col-lg-6 col-md-6"> <div class="info-card btc-type-operation" id="card-op-send"> <div class="card-body"> - <h5><i class="bi bi-upload"></i> Send Operation</h5> + <h5><i class="bi bi-upload"></i> Sending Bitcoin</h5> <div class="card-content-wrapper"> - <p class="summary">Input recipient Addr (<strong class="critical">TRIPLE CHECK</strong>). Set Amount. Set <span class="term">Fee (sat/vB)</span>. Review. <strong class="critical">Confirm Addr/Amount on HW Screen.</strong></p> + <p class="summary">Enter the recipient's address (<strong class="critical">DOUBLE/TRIPLE CHECK IT CAREFULLY</strong>). Enter the amount. Set an appropriate transaction <span class="term">fee (sat/vB)</span>. <strong class="critical">Confirm the address and amount on your HARDWARE WALLET SCREEN before approving.</strong></p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseOpSend" aria-expanded="false" aria-controls="collapseOpSend"> - Execution Flow <i class="bi bi-chevron-down"></i> + Sending Checklist <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseOpSend"> - <h6>Execution Flow:</h6> + <h6>Sending Checklist:</h6> <ol> - <li>Recipient Address Input: Paste/Scan. <strong class="critical">Visually verify first/last chars vs. source.</strong></li> - <li>Amount Input.</li> - <li>Fee Setting: Consult <a href="https://mempool.space/" target="_blank" rel="noopener noreferrer">mempool.space</a>. Balance urgency/cost.</li> - <li>Software Review: Check all details on host screen.</li> - <li><strong class="critical">Hardware Confirmation:</strong> Verify address & amount match ON THE DEVICE'S SCREEN before authorizing signature.</li> - <li>Broadcast Signed Transaction.</li> + <li><strong>Recipient Address:</strong> Paste or scan the address. <strong class="critical">Visually verify the first few and last few characters match the intended address.</strong> Beware of clipboard malware!</li> + <li><strong>Amount:</strong> Enter the correct amount of Bitcoin to send.</li> + <li><strong>Fee Setting:</strong> Check current network conditions (e.g., on <a href="https://mempool.space/" target="_blank" rel="noopener noreferrer">mempool.space</a>) to choose a fee rate (<span class="term">sat/vB</span>) that matches your urgency. Higher fee = faster confirmation.</li> + <li><strong>Review on Software:</strong> Check all details on your computer/phone screen.</li> + <li><strong class="critical">Hardware Wallet Confirmation:</strong> This is vital! Carefully check that the recipient address and amount shown ON THE HARDWARE WALLET'S SCREEN are correct before pressing the button(s) to sign/approve. This defeats clipboard hijacking malware.</li> + <li><strong>Authorize & Broadcast:</strong> Approve the signing on the hardware wallet. The software wallet will then broadcast the signed transaction.</li> </ol> </div> </div> @@ -647,9 +746,9 @@ <div class="col-lg-6 col-md-6"> <div class="info-card btc-type-operation" id="card-op-check"> <div class="card-body"> - <h5><i class="bi bi-search"></i> Balance/History Query</h5> + <h5><i class="bi bi-search"></i> Checking Balance & History</h5> <div class="card-content-wrapper"> - <p class="summary">Use wallet interface. Optional: Public block explorer (<a href="https://mempool.space/" target="_blank" rel="noopener noreferrer">mempool.space</a>) - Input <span class="term">addresses only</span> (privacy leak).</p> + <p class="summary">Your wallet software shows your balance and transaction history. You can also use a public <span class="term">block explorer</span> (like <a href="https://mempool.space/" target="_blank" rel="noopener noreferrer">mempool.space</a>) by entering your <span class="term">addresses</span> (not keys!) but be aware this links your addresses publicly.</p> <!-- Simple operation, less need for collapse --> </div> </div> @@ -660,31 +759,31 @@ <!-- ================================== --> - <!-- SECTION V: Security & Custody --> + <!-- UPDATED SECTION VI: Security Best Practices (OPSEC) --> <!-- ================================== --> <div class="schema-container cat-security" data-section-id="section-security"> - <h2 class="section-title" id="section-security"><i class="bi bi-fingerprint"></i> // V. Security Protocols :: OPSEC</h2> + <h2 class="section-title" id="section-security"><i class="bi bi-fingerprint"></i> // VI. Security Best Practices (OPSEC)</h2> <div class="row"> <div class="col-lg-6 col-md-12"> <div class="info-card btc-type-security" id="card-sec-seed"> <div class="card-body"> - <h5><i class="bi bi-shield-lock-fill"></i> Seed Phrase :: OPSEC Level MAX</h5> + <h5><i class="bi bi-shield-lock-fill"></i> Seed Phrase Security :: Rule #1</h5> <div class="card-content-wrapper"> - <p class="summary"><strong class="critical">[最重要 - CRITICAL]</strong> Your 12/24 words ARE your Bitcoin. Treat accordingly. Physical/Digital contamination = Total Loss.</p> + <p class="summary"><strong class="critical">[MOST IMPORTANT RULE] Your 12/24 words ARE your Bitcoin backup. Protect them above all else.</strong> Any compromise (digital or physical) means likely TOTAL LOSS.</p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSecSeed" aria-expanded="false" aria-controls="collapseSecSeed"> - Security Directives <i class="bi bi-chevron-down"></i> + Unbreakable Rules <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseSecSeed"> - <strong class="rule">Directive Alpha: ABSOLUTELY NO DIGITAL INPUT/STORAGE (No photos, typing, cloud, pwd mgrs). Assume ALL networked devices compromised.</strong> - <strong class="rule">Directive Bravo: ZERO TRUST POLICY. NEVER SHARE SEED. "Support" requesting seed = IMMEDIATE SCAM DETECTED.</strong> - <strong class="rule">Directive Charlie: BACKUP PHYSICALLY (STEEL RECOMMENDED), VERIFY ACCURACY, SECURE OFFLINE STORAGE (Redundant/Distributed Recommended).</strong> - <h6>Storage Strategy:</h6> + <strong class="rule">Rule 1: NEVER Store Digitally. No photos, no typing into computers/phones, no cloud storage, no password managers, no emails/chats. Assume ALL online devices can be compromised.</strong> + <strong class="rule">Rule 2: NEVER Share Your Seed. No website, app, or "support agent" ever needs your seed phrase. Anyone asking is a <strong class="critical">SCAMMER</strong> trying to steal your funds.</strong> + <strong class="rule">Rule 3: BACKUP Physically & Securely. Use durable materials (steel recommended), verify accuracy, store securely offline (hidden, safe), consider redundancy (multiple locations).</strong> + <h6>Secure Storage Strategies:</h6> <ul> - <li><span class="pros">Recommended:</span> Verified accurate transcription, Fire/Water/Corrosion proof steel plates, Multiple secure physical locations (consider geographic distribution), Obscurity.</li> - <li><span class="cons">Avoid:</span> Plain paper (fragile), easily discoverable locations, single point of failure for backup.</li> - <li><span class="term">Test Recovery Plan Periodically.</span></li> + <li><span class="pros">Recommended:</span> Verified accurate copy on <strong class="term">metal plates</strong> (fire/water/corrosion resistant like <a href="https://seedplate.com/" target="_blank" rel="noopener noreferrer">SeedPlate</a>, <a href="https://cryptosteel.com/" target="_blank" rel="noopener noreferrer">Cryptosteel</a>). Store in multiple secure, non-obvious physical locations (e.g., home safe, trusted relative's safe, bank deposit box - weigh risks of each).</li> + <li><span class="cons">Avoid:</span> Plain paper (easily damaged/destroyed), easy-to-find locations, storing all backups in one place (single point of failure).</li> + <li><span class="term">Consider:</span> Test your backup/recovery plan periodically with a small amount or on Testnet (See Section VII).</li> </ul> </div> </div> @@ -692,46 +791,46 @@ <div class="col-lg-6 col-md-12"> <div class="info-card btc-type-security" id="card-sec-device"> <div class="card-body"> - <h5><i class="bi bi-cpu-fill"></i> Hardware Module :: OPSEC</h5> + <h5><i class="bi bi-cpu-fill"></i> Hardware Wallet Security</h5> <div class="card-content-wrapper"> - <p class="summary">Source directly. Strong Credentials. <strong class="critical">VERIFY ALL TX DATA ON TRUSTED DISPLAY.</strong> Firmware Hygiene.</p> + <p class="summary">Buy hardware wallets <strong class="term">directly from the manufacturer</strong> or authorized resellers. Use a strong PIN. <strong class="critical">ALWAYS verify transaction details (address, amount) on the device's trusted screen before confirming.</strong> Keep firmware updated cautiously.</p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSecDevice" aria-expanded="false" aria-controls="collapseSecDevice"> - Operational Procedures <i class="bi bi-chevron-down"></i> + Device Procedures <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseSecDevice"> - <h6>Standard Operating Procedures:</h6> + <h6>Hardware Wallet Best Practices:</h6> <ul> - <li><strong>Acquisition Protocol:</strong> Source <strong class="term">Direct from Manufacturer</strong> / Authorized Reseller ONLY. Verify tamper-evident seals.</li> - <li><strong>Access Control:</strong> Implement strong, unique <span class="term">PIN</span>. Understand and secure optional <span class="term">Passphrase</span> if used (becomes part of seed).</li> - <li><strong class="critical">Trusted Display Verification:</strong> MANDATORY check for every TX/Address generation. Confirms data against host malware (e.g., clipboard hijacks).</li> - <li><strong>Firmware Integrity:</strong> Update only from official sources. Verify release notes. Have seed backup accessible *before* starting update. Consider delaying non-critical updates slightly.</li> - <li><strong>Physical Security:</strong> Protect device from theft and unauthorized access ("Evil Maid Attack").</li> + <li><strong>Source Securely:</strong> Buy <strong class="term">directly from the vendor</strong> to avoid tampering during shipping (supply chain attack). Check tamper-evident seals upon arrival.</li> + <li><strong>Strong PIN:</strong> Use a non-obvious PIN (more than 4 digits if possible). This protects against casual physical access.</li> + <li><strong>(Optional) Passphrase:</strong> Understand how the BIP-39 Passphrase works (Section VII) before using it. It adds security but also risk if forgotten.</li> + <li><strong class="critical">Trusted Display Verification:</strong> MANDATORY for every Send/Receive operation. It's your defense against malware on your computer/phone trying to trick you into sending funds to the wrong address.</li> + <li><strong>Firmware Updates:</strong> Update only when necessary, using official instructions. Ensure your seed phrase backup is accessible *before* updating. Verify update authenticity.</li> + <li><strong>Physical Protection:</strong> Keep the device safe from theft or prolonged unauthorized access ("Evil Maid Attack" where someone tampers with it).</li> </ul> </div> </div> </div> - <!-- Add SW/Network, Physical, Backup Cards similarly --> <div class="col-lg-6 col-md-12"> <div class="info-card btc-type-security" id="card-sec-sw-network"> <div class="card-body"> - <h5><i class="bi bi-broadcast-pin"></i> Host System & Network Hygiene</h5> + <h5><i class="bi bi-broadcast-pin"></i> Computer & Network Security</h5> <div class="card-content-wrapper"> - <p class="summary">Use reputable wallet software (official sources). Keep OS/Security updated. Vigilant against Phishing. Avoid untrusted Networks.</p> + <p class="summary">Use reputable wallet software from official sources. Keep your OS and security software updated. Be extremely vigilant against <span class="term">phishing</span> scams. Avoid using public/untrusted Wi-Fi for sensitive operations.</p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSecSw" aria-expanded="false" aria-controls="collapseSecSw"> - Defense Layers <i class="bi bi-chevron-down"></i> + Digital Hygiene <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseSecSw"> - <h6>Defense Layers:</h6> + <h6>Protecting Your Digital Environment:</h6> <ul> - <li><strong>Software Source:</strong> Download ONLY from official developer/manufacturer websites. Verify signatures if possible. Prefer open-source & well-audited.</li> - <li><strong>System Updates:</strong> Keep Operating System and Anti-Malware definitions current.</li> - <li><strong>Phishing Defense:</strong> Extreme skepticism towards unsolicited emails, DMs, popups requesting wallet interaction or credentials. Verify via known official channels.</li> - <li><strong>Network Security:</strong> Avoid sensitive operations (seed recovery) on public/untrusted Wi-Fi. Consider VPN.</li> - <li><strong class="critical">Clipboard Malware Awareness:</strong> Always re-verify pasted addresses visually. Use HW trusted display confirmation.</li> + <li><strong>Software Source:</strong> Download wallet software ONLY from official developer websites. Verify digital signatures if possible. Prefer well-known, open-source options when using software wallets.</li> + <li><strong>System Health:</strong> Keep your operating system (Windows, macOS, Linux) and anti-malware software up-to-date.</li> + <li><strong>Phishing Awareness:</strong> Be skeptical of emails, messages, links, or apps asking for wallet details, seed phrases, or urging you to connect your wallet. Verify requests through official channels. <strong class="critical">Never enter your seed phrase online or into any software except during wallet recovery.</strong></li> + <li><strong>Network Safety:</strong> Avoid connecting hardware wallets or performing sensitive actions (like seed recovery) on public Wi-Fi networks. Consider using a VPN.</li> + <li><strong class="critical">Clipboard Malware:</strong> Malware can secretly change copied Bitcoin addresses. ALWAYS double-check pasted addresses visually AND confirm on your hardware wallet's screen.</li> </ul> </div> </div> @@ -739,26 +838,26 @@ <div class="col-lg-6 col-md-12"> <div class="info-card btc-type-security" id="card-sec-backup"> <div class="card-body"> - <h5><i class="bi bi-server"></i> Backup, Recovery & Succession</h5> + <h5><i class="bi bi-server"></i> Backup, Recovery & Inheritance</h5> <div class="card-content-wrapper"> - <p class="summary"><span class="term">Seed phrase IS the master key.</span> Device is disposable. Have a <strong class="term">tested</strong> recovery protocol. Plan for inheritance/incapacity.</p> + <p class="summary">Your <span class="term">seed phrase IS the ultimate backup</span>. The hardware device is replaceable. Have a <strong class="term">tested</strong> recovery plan. Consider how your family could access funds if needed (<span class="term">inheritance planning</span>).</p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSecBackup" aria-expanded="false" aria-controls="collapseSecBackup"> - Contingency Planning <i class="bi bi-chevron-down"></i> + Contingency Plans <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseSecBackup"> - <h6>Contingency Protocols:</h6> + <h6>Planning for the Unexpected:</h6> <ul> - <li><strong>Recovery Drill:</strong> Know the exact steps to restore wallet from seed on a compatible interface. Practice with testnet or small amounts *before* needed.</li> - <li><strong>Estate / Succession Planning:</strong> CRITICAL to avoid permanent loss. + <li><strong>Recovery Practice:</strong> Know the exact steps to restore your wallet using your seed phrase on a new/reset device or compatible software. Practice this (ideally on testnet or with a tiny amount) *before* you actually need it in an emergency.</li> + <li><strong>Inheritance Planning:</strong> CRITICAL step often overlooked. If only you know how to access the funds, they could be lost forever upon your death or incapacitation. <ul> - <li>Securely documented instructions with trusted executor/lawyer.</li> - <li><span class="term">Multisignature</span> setups distributing control.</li> - <li>Specialized inheritance platforms (Vet carefully!). Examples: <a href="https://keys.casa/bitcoin-inheritance-planning" target="_blank" rel="noopener noreferrer">Casa</a>, <a href="https://unchained.com/inheritance/" target="_blank" rel="noopener noreferrer">Unchained Capital</a>.</li> + <li>Provide clear, secure instructions to a trusted person/executor (without revealing the seed itself prematurely).</li> + <li>Consider using <span class="term">Multisignature</span> setups (Section VII) to distribute control.</li> + <li>Explore specialized services (vet carefully!): e.g., <a href="https://keys.casa/bitcoin-inheritance-planning" target="_blank" rel="noopener noreferrer">Casa</a>, <a href="https://unchained.com/inheritance/" target="_blank" rel="noopener noreferrer">Unchained Capital</a>.</li> </ul> </li> - <li><strong>Redundancy:</strong> Multiple secure backups mitigate single point of failure risk (theft, disaster).</li> + <li><strong>Backup Redundancy:</strong> Having multiple secure backups (e.g., two steel plates in different secure locations) protects against loss from a single event (fire, flood, theft).</li> </ul> </div> </div> @@ -769,32 +868,34 @@ <!-- ==================================== --> - <!-- SECTION VI: Advanced Operations --> + <!-- UPDATED SECTION VII: Advanced Features & Techniques --> <!-- ==================================== --> <div class="schema-container cat-advanced" data-section-id="section-advanced"> - <h2 class="section-title" id="section-advanced"><i class="bi bi-motherboard"></i> // VI. Advanced Configurations</h2> + <h2 class="section-title" id="section-advanced"><i class="bi bi-motherboard"></i> // VII. Advanced Features & Techniques</h2> <div class="row"> - <!-- Populate with cards for Passphrase, Multisig, Node Connect, Coin Control, PSBTs, Fee Bumping, Shamir, Testnet --> <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-advanced" id="card-adv-passphrase"> <div class="card-body"> - <h5><i class="bi bi-mask"></i> BIP-39 Passphrase</h5> + <h5><i class="bi bi-mask"></i> BIP-39 Passphrase ("Hidden Wallet")</h5> <div class="card-content-wrapper"> - <p class="summary">Optional "25th word" added to seed -> Creates separate hidden wallet instance. Security through obscurity/deniability.</p> + <p class="summary">An optional, user-chosen word or phrase added to your 12/24 word seed. Creates a completely separate, hidden set of keys/addresses. Use with extreme caution.</p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseAdvPassphrase" aria-expanded="false" aria-controls="collapseAdvPassphrase"> - Risks & Use Case <i class="bi bi-chevron-down"></i> + Use Cases & Risks <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseAdvPassphrase"> - <h6>Functionality:</h6> + <h6>How it Works:</h6> <ul> - <li><code>Seed + Passphrase = Unique Wallet</code>. Passphrase is never stored on device.</li> - <li>Use Case: Plausible deniability under duress (reveal non-passphrase wallet); extra security layer (requires seed + passphrase).</li> + <li><code>Seed Phrase ONLY = Wallet A</code></li> + <li><code>Seed Phrase + Passphrase 'X' = Wallet B (Hidden)</code></li> + <li><code>Seed Phrase + Passphrase 'Y' = Wallet C (Hidden)</code></li> + <li>The passphrase is never stored on the device.</li> + <li><strong>Use Case:</strong> Plausible deniability (reveal the non-passphrase wallet under duress). Adds security if BOTH seed and passphrase are required.</li> </ul> <h6><strong class="critical">CRITICAL RISK:</strong></h6> <ul> - <li><strong class="cons">Forgetting exact passphrase = PERMANENT FUND LOSS. NO RECOVERY.</strong> Must be backed up separately/memorized perfectly (risky). Case/space sensitive.</li> + <li><strong class="cons">If you forget the EXACT passphrase (case-sensitive, spaces count), the funds in that hidden wallet are PERMANENTLY LOST. There is NO recovery.</strong> You MUST back up the passphrase separately and securely from the seed, or memorize it perfectly (very risky).</li> </ul> </div> </div> @@ -804,116 +905,143 @@ <div class="card-body"> <h5><i class="bi bi-diagram-3-fill"></i> Multisignature (Multisig)</h5> <div class="card-content-wrapper"> - <p class="summary">M-of-N key scheme (e.g., 2-of-3 signatures required). Distributes control & eliminates single points of failure.</p> + <p class="summary">Requires multiple keys (held on different devices/locations) to approve a transaction (e.g., 2-of-3 keys needed). Greatly enhances security and enables shared control.</p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseAdvMultisig" aria-expanded="false" aria-controls="collapseAdvMultisig"> - Applications <i class="bi bi-chevron-down"></i> + Benefits & Setup <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseAdvMultisig"> - <h6>Applications:</h6> + <h6>Why Use Multisig?</h6> <ul> - <li><strong>Enhanced Security:</strong> Requires compromise of multiple keys/devices/locations.</li> - <li><strong>Shared Custody:</strong> Joint accounts, corporate treasury.</li> - <li><strong>Robust Backup/Inheritance:</strong> Distribute keys among user, vault, lawyer, family.</li> + <li><strong class="pros">Enhanced Security:</strong> An attacker needs to compromise multiple keys/devices/locations, not just one.</li> + <li><strong class="pros">Shared Control:</strong> Good for business funds (multiple partners need to sign) or joint accounts.</li> + <li><strong class="pros">Robust Backup/Inheritance:</strong> Distribute keys among yourself, a safe deposit box, a lawyer, family members, etc., so losing one key doesn't mean losing funds.</li> + </ul> + <h6>Setup:</h6> + <ul> + <li>Requires specialized software (like <a href="https://sparrowwallet.com/" target="_blank" rel="noopener noreferrer">Sparrow Wallet</a>, <a href="https://specter.solutions/" target="_blank" rel="noopener noreferrer">Specter Desktop</a>, <a href="https://nunchuk.io/" target="_blank" rel="noopener noreferrer">Nunchuk</a>) to coordinate multiple hardware wallets.</li> + <li>Uses <span class="term">PSBTs</span> (Partially Signed Bitcoin Transactions) to pass the transaction between signers.</li> + <li>More complex than single-signature wallets.</li> + <li>Resource: <a href="https://sparrowwallet.com/docs/multisig-wallet.html" target="_blank" rel="noopener noreferrer">Sparrow Multisig Guide</a></li> </ul> - <p>Setup requires coordinator software (<code>Sparrow</code>, <code>Specter</code>, <code>Nunchuk</code>) using <span class="term">PSBTs</span>.</p> - <ul><li>Resource: <a href="https://sparrowwallet.com/docs/multisig-wallet.html" target="_blank" rel="noopener noreferrer">Sparrow Multisig Guide</a></li></ul> </div> </div> </div> <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-advanced" id="card-adv-node"> <div class="card-body"> - <h5><i class="bi bi-hdd-network-fill"></i> Connect to Full Node</h5> + <h5><i class="bi bi-hdd-network-fill"></i> Using Your Own Full Node</h5> <div class="card-content-wrapper"> - <p class="summary">Interface wallet with own <a href="https://bitcoincore.org/" target="_blank" rel="noopener noreferrer">Bitcoin Core</a> node. <strong class="pros">Maximum Privacy & Trust Minimization.</strong></p> + <p class="summary">Connect your wallet software (like Sparrow or Specter) directly to your own <a href="https://bitcoincore.org/" target="_blank" rel="noopener noreferrer">Bitcoin Core</a> full node instead of relying on third-party servers. <strong class="pros">Maximizes privacy and trustlessness.</strong></p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseAdvNode" aria-expanded="false" aria-controls="collapseAdvNode"> - Rationale <i class="bi bi-chevron-down"></i> + Why Run a Node? <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseAdvNode"> - <h6>Rationale:</h6> + <h6>Benefits:</h6> + <ul> + <li><strong>Privacy:</strong> Your wallet doesn't broadcast your addresses and transaction history to company servers.</li> + <li><strong>Verification:</strong> Your node independently validates all Bitcoin rules and transactions; you don't trust someone else's node.</li> + <li><strong>Network Support:</strong> Helps strengthen the decentralized Bitcoin network.</li> + </ul> + <h6>Requirements:</h6> <ul> - <li><strong>Privacy:</strong> Avoids leaking address/transaction data to third-party servers.</li> - <li><strong>Verification:</strong> Independently validate all network rules and transactions. No need to trust external providers.</li> - <li><strong>Network Health:</strong> Contributes to decentralization.</li> + <li>Requires dedicated hardware (like a Raspberry Pi or old computer), sufficient internet bandwidth, and storage space.</li> + <li>Easier setup options exist (e.g., <a href="https://umbrel.com/" target="_blank" rel="noopener noreferrer">Umbrel</a>, <a href="https://start9.com/" target="_blank" rel="noopener noreferrer">Start9</a>).</li> + <li>Requires compatible wallet software.</li> + <li>Resource: <a href="https://bitcoin.org/en/full-node#choose-your-node" target="_blank" rel="noopener noreferrer">Node Implementation Options</a></li> </ul> - <p>Requires running node software (e.g., Bitcoin Core, Umbrel, Start9) and compatible wallet (<code>Sparrow</code>, <code>Specter</code>, <code>Electrum</code> + Server).</p> - <ul><li>Resource: <a href="https://bitcoin.org/en/full-node#choose-your-node" target="_blank" rel="noopener noreferrer">Node Implementation Options</a></li></ul> </div> </div> </div> <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-advanced" id="card-adv-coincontrol"> <div class="card-body"> - <h5><i class="bi bi-vinyl-fill"></i> Coin Control :: UTXO Selection</h5> + <h5><i class="bi bi-vinyl-fill"></i> Coin Control (UTXO Management)</h5> <div class="card-content-wrapper"> - <p class="summary">Manually select input <span class="term">UTXOs</span> for spending. Advanced privacy & fee management technique.</p> + <p class="summary">Manually selecting which specific "chunks" of Bitcoin (<span class="term">UTXOs</span>) are used as inputs when creating a transaction. Useful for advanced privacy and fee management.</p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseAdvCoinControl" aria-expanded="false" aria-controls="collapseAdvCoinControl"> - Benefits <i class="bi bi-chevron-down"></i> + Why Use It? <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseAdvCoinControl"> <h6>Benefits:</h6> <ul> - <li><strong>Privacy:</strong> Avoids linking potentially unrelated UTXOs; breaks address reuse heuristics. Can segregate UTXO sources (e.g., KYC vs non-KYC - *note chain analysis limitations*).</li> - <li><strong>Fee Optimization:</strong> Select UTXOs to minimize transaction size/cost.</li> - <li><strong>Labeling:</strong> Track origin/purpose of specific UTXOs.</li> + <li><strong>Privacy:</strong> Avoids linking UTXOs from different sources together in one transaction, which can reveal information about your holdings. Allows separating funds (e.g., KYC vs non-KYC - *note: advanced topic with limits*).</li> + <li><strong>Fee Management:</strong> Can sometimes help optimize transaction size and cost by choosing specific UTXOs.</li> + <li><strong>Labeling:</strong> Allows you to label UTXOs with their source or purpose for better tracking.</li> </ul> - <p>Requires wallet support (e.g., <code>Electrum</code>, <code>Sparrow</code>, <code>Specter</code>).</p> + <p>Requires wallet software that supports this feature (e.g., <a href="https://electrum.org/#features" target="_blank" rel="noopener noreferrer">Electrum</a>, <a href="https://sparrowwallet.com/docs/transaction-inputs-outputs.html" target="_blank" rel="noopener noreferrer">Sparrow</a>, <a href="https://specter.solutions/" target="_blank" rel="noopener noreferrer">Specter</a>).</p> </div> </div> </div> <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-advanced" id="card-adv-psbt"> <div class="card-body"> - <h5><i class="bi bi-file-binary-fill"></i> PSBTs :: Transaction Fragments</h5> + <h5><i class="bi bi-file-binary-fill"></i> PSBT (Partially Signed Bitcoin Tx)</h5> <div class="card-content-wrapper"> - <p class="summary">Partially Signed Bitcoin TX format (<a href="https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki" target="_blank" rel="noopener noreferrer">BIP-174</a>). Standard for offline/multisig workflows.</p> + <p class="summary">A standard format (<a href="https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki" target="_blank" rel="noopener noreferrer">BIP-174</a>) for transactions that are not yet fully signed. Essential for <span class="term">air-gapped</span> and <span class="term">multisig</span> workflows.</p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseAdvPsbt" aria-expanded="false" aria-controls="collapseAdvPsbt"> - Workflow Examples <i class="bi bi-chevron-down"></i> + How It's Used <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseAdvPsbt"> - <h6>Workflow Examples:</h6> + <h6>Common Workflows:</h6> <ul> - <li><strong>Air-Gap:</strong> Create unsigned PSBT online -> Transfer (SD/QR) -> Sign offline -> Transfer signed PSBT back -> Broadcast.</li> - <li><strong>Multisig:</strong> Create PSBT -> Pass to signer 1 -> Sign -> Pass to signer 2 -> Sign -> ... -> Broadcast fully signed TX.</li> + <li><strong>Air-Gap Signing:</strong> 1. Create unsigned PSBT online. 2. Move PSBT file/QR to offline signer. 3. Sign PSBT offline. 4. Move signed PSBT back online. 5. Broadcast.</li> + <li><strong>Multisignature Signing:</strong> 1. Create unsigned PSBT. 2. Pass to Signer 1 -> Signs -> Partially Signed PSBT. 3. Pass to Signer 2 -> Signs -> Fully Signed PSBT (if 2-of-2). 4. Broadcast.</li> </ul> + <p>Facilitates complex signing arrangements without exposing keys online.</p> </div> </div> </div> <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-advanced" id="card-adv-fee-bump"> <div class="card-body"> - <h5><i class="bi bi-graph-up-arrow"></i> Fee Bumping :: RBF & CPFP</h5> + <h5><i class="bi bi-graph-up-arrow"></i> Fee Bumping (RBF / CPFP)</h5> <div class="card-content-wrapper"> - <p class="summary"><span class="term">RBF (Replace-By-Fee):</span> Replace own stuck TX w/ higher fee (<a href="https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki" target="_blank" rel="noopener noreferrer">BIP-125</a>). <span class="term">CPFP:</span> Spend stuck *incoming* TX w/ high fee.</p> - <!-- Simple enough, maybe no collapse --> + <p class="summary">Techniques to speed up a stuck (unconfirmed) transaction by increasing the fee.</p> + <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseFeeBump" aria-expanded="false" aria-controls="collapseFeeBump"> + How It Works <i class="bi bi-chevron-down"></i> + </button> </div> </div> + <div class="collapse collapse-content" id="collapseFeeBump"> + <h6>Methods:</h6> + <ul> + <li><span class="term">RBF (Replace-By-Fee):</span> If your wallet enabled RBF (<a href="https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki" target="_blank" rel="noopener noreferrer">BIP-125</a>) when sending, you can broadcast a *new version* of the same transaction with a higher fee. Miners will prioritize the higher-fee version.</li> + <li><span class="term">CPFP (Child-Pays-For-Parent):</span> If you received a transaction that is stuck, you can spend *that* incoming UTXO (even before it confirms) in a *new* transaction with a very high fee. Miners are incentivized to mine the stuck parent transaction so they can also mine the high-fee child transaction.</li> + </ul> + <p>Requires wallet support for these features.</p> + </div> </div> </div> <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-advanced" id="card-adv-shamir"> <div class="card-body"> - <h5><i class="bi bi-intersect"></i> Shamir Backup :: Seed Sharding</h5> + <h5><i class="bi bi-intersect"></i> Shamir Backup (Seed Splitting)</h5> <div class="card-content-wrapper"> - <p class="summary">Split seed into M-of-N shares (<a href="https://github.com/satoshilabs/slips/blob/master/slip-0039.md" target="_blank" rel="noopener noreferrer">SLIP-39</a>). Requires threshold for recovery. Enhanced redundancy/security.</p> + <p class="summary">Splits your seed phrase backup into multiple unique 'shares' (e.g., 3-of-5). You need a certain threshold of shares (e.g., 3 out of the 5) to recover the wallet. Increases redundancy.</p> <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseAdvShamir" aria-expanded="false" aria-controls="collapseAdvShamir"> - Tradeoffs <i class="bi bi-chevron-down"></i> + Pros & Cons <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseAdvShamir"> - <h6>Tradeoffs:</h6> + <h6>How it Helps:</h6> <ul> - <li><strong class="pros">Pros:</strong> Tolerate loss of some shares; attacker needs multiple shares.</li> - <li><strong class="cons">Cons:</strong> Complex setup/recovery; less wallet support than BIP-39 (Trezor T primarily).</li> + <li><strong class="pros">Redundancy:</strong> You can lose some shares (less than the threshold) and still recover your funds.</li> + <li><strong class="pros">Security:</strong> An attacker needs to find multiple shares (the threshold number) to steal funds, not just one backup.</li> + </ul> + <h6>Considerations:</h6> + <ul> + <li><strong class="cons">Complexity:</strong> More complex to set up and recover than a standard BIP-39 seed phrase.</li> + <li><strong class="cons">Compatibility:</strong> Less widely supported by wallets. Primarily associated with Trezor hardware wallets (<a href="https://github.com/satoshilabs/slips/blob/master/slip-0039.md" target="_blank" rel="noopener noreferrer">SLIP-39 standard</a>).</li> + <li>Still requires careful management of the individual shares.</li> </ul> </div> </div> @@ -921,9 +1049,10 @@ <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-advanced" id="card-adv-testnet"> <div class="card-body"> - <h5><i class="bi bi-joystick"></i> Testnet :: Simulation Grid</h5> + <h5><i class="bi bi-joystick"></i> Testnet (Practice Network)</h5> <div class="card-content-wrapper"> - <p class="summary">Parallel Bitcoin network using valueless coins. Safely test features, practice recovery, learn protocols.</p> + <p class="summary">A parallel Bitcoin network where the coins have no real-world value. Excellent for safely testing wallet features, practicing recovery procedures, or learning without risking real money.</p> + <!-- Simple concept, less need for collapse --> </div> </div> </div> @@ -933,45 +1062,46 @@ <!-- ========================================= --> - <!-- SECTION VII: Hardware Wallet Comparison --> + <!-- UPDATED SECTION VIII: Hardware Wallet Comparison --> <!-- ========================================= --> <div class="schema-container cat-comparison" data-section-id="section-comparison"> - <h2 class="section-title" id="section-comparison"><i class="bi bi-motherboard-fill"></i> // VII. Hardware Module Matrix</h2> + <h2 class="section-title" id="section-comparison"><i class="bi bi-motherboard-fill"></i> // VIII. Hardware Wallet Comparison</h2> <div class="row"> <div class="col-12"> <div class="info-card btc-type-comparison" id="card-compare-factors"> <div class="card-body"> - <h5 class="text-center"><i class="bi bi-sliders"></i> Comparison Vectors</h5> + <h5 class="text-center"><i class="bi bi-sliders"></i> How to Choose a Hardware Wallet</h5> <div class="card-content-wrapper"> - <p class="summary text-center">Evaluate modules based on: Security Arch (SE/MCU), Source Code Auditability, Bitcoin Focus, Air-Gap Protocol, UX/UI, Advanced Feature Set, Cost, Vendor Trust.</p> + <p class="summary text-center">Consider: Security Model (Chip Type, Code Audits), Bitcoin Focus vs Multi-Coin, Air-Gap Capability, User Experience, Advanced Features (Multisig, Passphrase), Price, Vendor Reputation.</p> <button class="btn btn-sm details-toggle mx-auto" type="button" data-bs-toggle="collapse" data-bs-target="#collapseCompareFactors" aria-expanded="false" aria-controls="collapseCompareFactors"> - Vector Details <i class="bi bi-chevron-down"></i> + Factors Explained <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseCompareFactors"> - <h6>Vector Analysis:</h6> + <h6>Key Comparison Factors:</h6> <ul> - <li><strong>Security Arch:</strong> Secure Element (Dedicated, often closed) vs. Generic MCU (Open potential, relies on SW hardening).</li> - <li><strong>Source Code:</strong> Open (Verifiable) vs. Closed (Trust-based). Firmware & Hardware.</li> - <li><strong>Coin Support:</strong> Bitcoin-Only (Reduced attack surface) vs. Multi-Coin (Convenience, increased complexity).</li> - <li><strong>Air-Gap:</strong> True air-gap (SD/QR/NFC) vs. USB/Bluetooth dependent.</li> - <li><strong>UX/UI:</strong> Interface simplicity, screen quality, input method.</li> - <li><strong>Features:</strong> Passphrase, Multisig (PSBT), Coin Control, Shamir etc. support level.</li> - <li><strong>Cost.</strong></li> - <li><strong>Vendor Reputation:</strong> History, security posture, community trust.</li> + <li><strong>Security Chip:</strong> <span class="term">Secure Element (SE)</span> is a dedicated, tamper-resistant chip (often closed-source) vs. a <span class="term">General Purpose Microcontroller (MCU)</span> which relies more on software hardening (can be more open). Both have pros/cons.</li> + <li><strong>Source Code:</strong> Is the firmware (<span class="term">Open Source</span>) verifiable by the public, or (<span class="term">Closed Source</span>) requiring trust in the vendor? Hardware design openness also varies.</li> + <li><strong>Coin Support:</strong> <span class="term">Bitcoin-Only</span> devices have a reduced attack surface (less code complexity). <span class="term">Multi-Coin</span> devices offer convenience if you hold other assets but add complexity.</li> + <li><strong>Air-Gap Features:</strong> Does it support true air-gapped operation (via SD card/QR codes like <a href="#card-compare-coldcard">Coldcard</a>) or does it require USB/Bluetooth?</li> + <li><strong>User Experience (UX):</strong> Ease of setup, screen quality, button usability, companion software quality.</li> + <li><strong>Advanced Features:</strong> Support for Passphrases, Multisig (PSBT), Coin Control, Shamir Backup (SLIP-39), etc.</li> + <li><strong>Price Point.</strong></li> + <li><strong>Vendor Reputation & Trust:</strong> Company history, security track record, community perception, responsiveness to issues.</li> </ul> + <p><strong class="term">No single "best" wallet exists. Choose based on your technical comfort, security needs, budget, and desired features.</strong></p> </div> </div> </div> - <!-- Specific Wallet Cards --> + <!-- Specific Wallet Cards (Content remains similar, summaries slightly tweaked for clarity) --> <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-comparison comparison-item" id="card-compare-trezor"> <div class="card-body"> - <h5><i class="bi bi-unlock-fill"></i> Trezor (T/Safe 3)</h5> + <h5><i class="bi bi-unlock-fill"></i> Trezor (Model T / Safe 3)</h5> <div class="card-content-wrapper"> - <p class="summary"><span class="pros">[+] Open Source History, User-Friendly Suite, Passphrase/SLIP-39 (T), Safe 3 adds SE.</span> <span class="cons">[-] Model T=MCU, Safe 3 SE=closed, No Air-Gap.</span></p> + <p class="summary"><span class="pros">[+] Long history, Open Source FW, User-friendly Suite, Passphrase/Shamir (T), Safe 3 adds SE Option.</span> <span class="cons">[-] Model T=MCU (past vulnerability info public), Safe 3 SE=closed component, No built-in Air-Gap.</span></p> <p><a href="https://trezor.io/" target="_blank" rel="noopener noreferrer">trezor.io</a></p> </div> </div> @@ -980,9 +1110,9 @@ <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-comparison comparison-item" id="card-compare-coldcard"> <div class="card-body"> - <h5><i class="bi bi-calculator-fill"></i> Coldcard (Mk4/Q1)</h5> + <h5><i class="bi bi-calculator-fill"></i> Coldcard (Mk4 / Q1)</h5> <div class="card-content-wrapper"> - <p class="summary"><span class="pros">[+] Bitcoin-Only, High Security Rep, True Air-Gap (SD/NFC), Top PSBT/Multisig, Open FW, Physical Security++.</span> <span class="cons">[-] Steep Learning Curve, Needs Coordinator SW, Basic UI, Mk4=MCU.</span></p> + <p class="summary"><span class="pros">[+] Bitcoin-Only (focus!), Top security rep, True Air-Gap (SD/NFC/USB), Excellent PSBT/Multisig, Open Source FW, Strong physical security features.</span> <span class="cons">[-] Steeper learning curve (less beginner-friendly), Needs coordinator SW (Sparrow/Specter), Basic UI.</span></p> <p><a href="https://coldcard.com/" target="_blank" rel="noopener noreferrer">coldcard.com</a></p> </div> </div> @@ -991,9 +1121,9 @@ <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-comparison comparison-item" id="card-compare-ledger"> <div class="card-body"> - <h5><i class="bi bi-usb-fill"></i> Ledger (Nano/Stax)</h5> + <h5><i class="bi bi-usb-fill"></i> Ledger (Nano S+/X / Stax)</h5> <div class="card-content-wrapper"> - <p class="summary"><span class="pros">[+] Uses SE, Wide Coin Support, Popular, Ledger Live UI.</span> <span class="cons">[-] Closed Source FW/SE, "Recover" Controversy, Past Data Breach, Relies on Ledger Live.</span></p> + <p class="summary"><span class="pros">[+] Uses Secure Element chip, Wide Coin Support, Popular/Well-known, Polished Ledger Live app.</span> <span class="cons">[-] Closed Source Firmware/SE, Controversial "Recover" service (opt-in cloud backup), Past customer data breach, Relies heavily on Ledger Live.</span></p> <p><a href="https://www.ledger.com/" target="_blank" rel="noopener noreferrer">ledger.com</a></p> </div> </div> @@ -1002,9 +1132,9 @@ <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-comparison comparison-item" id="card-compare-bitbox"> <div class="card-body"> - <h5><i class="bi bi-box-fill"></i> BitBox02 (BTC-Only)</h5> + <h5><i class="bi bi-box-fill"></i> BitBox02 (Bitcoin-Only Ed.)</h5> <div class="card-content-wrapper"> - <p class="summary"><span class="pros">[+] Good Security/UX (SE + Open FW parts), Minimalist, BTC-Only Option, Good App Integration.</span> <span class="cons">[-] Requires BitBoxApp, Limited Air-Gap.</span></p> + <p class="summary"><span class="pros">[+] Strong security focus (SE + Open FW parts), Minimalist design, BTC-Only version available, Good companion app.</span> <span class="cons">[-] Requires BitBoxApp, USB connection (no true air-gap).</span></p> <p><a href="https://bitbox.swiss/" target="_blank" rel="noopener noreferrer">bitbox.swiss</a></p> </div> </div> @@ -1015,7 +1145,7 @@ <div class="card-body"> <h5><i class="bi bi-qr-code-scan"></i> Seedsigner (DIY)</h5> <div class="card-content-wrapper"> - <p class="summary"><span class="pros">[+] Low Cost, DIY/Edu, Fully Air-Gapped (QR), Stateless Option, Fully Open Source HW/SW.</span> <span class="cons">[-] Requires Assembly/Setup, UX Depends on Parts, Slower QR.</span></p> + <p class="summary"><span class="pros">[+] Very Low Cost, DIY/Educational, Fully Air-Gapped via QR codes (stateless option), Fully Open Source HW & SW.</span> <span class="cons">[-] Requires assembly & setup, UX depends on components used, QR scanning can be slower.</span></p> <p><a href="https://seedsigner.com/" target="_blank" rel="noopener noreferrer">seedsigner.com</a></p> </div> </div> @@ -1026,7 +1156,7 @@ <div class="card-body"> <h5><i class="bi bi-camera-fill"></i> Blockstream Jade</h5> <div class="card-content-wrapper"> - <p class="summary"><span class="pros">[+] Affordable, BTC-Focused, Stateless/Blind Oracle option, QR Air-Gap, Open Source HW/FW.</span> <span class="cons">[-] Oracle requires trust (optional), Basic UI.</span></p> + <p class="summary"><span class="pros">[+] Affordable, Bitcoin-focused, Optional QR Air-Gap mode, Open Source HW/FW, Stateless/Server-assisted security model option.</span> <span class="cons">[-] Server assistance ("Blind Oracle") requires trust (optional unlock), Basic UI.</span></p> <p><a href="https://blockstream.com/jade/" target="_blank" rel="noopener noreferrer">blockstream.com/jade/</a></p> </div> </div> @@ -1035,20 +1165,20 @@ <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-comparison comparison-item" id="card-compare-passport"> <div class="card-body"> - <h5><i class="bi bi-passport-fill"></i> Foundation Passport</h5> + <h5><i class="bi bi-passport-fill"></i> Foundation Passport (Batch 2)</h5> <div class="card-content-wrapper"> - <p class="summary"><span class="pros">[+] Premium Design, BTC-Focused, Air-Gapped (QR/SD), Security Focus, Open Source FW.</span> <span class="cons">[-] Higher Price, Relies on App/Coordinator.</span></p> + <p class="summary"><span class="pros">[+] Premium build quality, Bitcoin-focused, Air-Gapped via QR/SD card, Strong security emphasis, Open Source FW.</span> <span class="cons">[-] Higher price point, Relies on companion app/coordinator SW.</span></p> <p><a href="https://foundationdevices.com/" target="_blank" rel="noopener noreferrer">foundationdevices.com</a></p> </div> </div> </div> </div> - <div class="col-lg-4 col-md-6"> + <div class="col-lg-4 col-md-6"> {/* Placeholder/Summary Card */} <div class="info-card btc-type-comparison comparison-item" id="card-compare-choice"> <div class="card-body"> - <h5 class="text-center"><i class="bi bi-check2-square"></i> Optimal Module Selection</h5> + <h5 class="text-center"><i class="bi bi-check2-square"></i> Making Your Choice</h5> <div class="card-content-wrapper"> - <p class="summary text-center">Selection Matrix: Factor in Tech Skill, Budget, Altcoin Need, Air-Gap Requirement, Open Source Preference, Feature Needs (Multisig), Vendor Trust. <strong class="term">Analyze tradeoffs for your threat model.</strong></p> + <p class="summary text-center">Factor in your technical skills, budget, need for other coins, desire for air-gap, open source preferences, advanced feature needs (like multisig), and trust in the vendor. <strong class="term">Analyze the tradeoffs based on your personal threat model and use case.</strong></p> </div> </div> </div> @@ -1058,17 +1188,17 @@ <!-- =============================================== --> - <!-- SECTION VIII: Common Issues & How People Lose --> + <!-- UPDATED SECTION IX: Common Mistakes & Pitfalls --> <!-- =============================================== --> <div class="schema-container cat-pitfalls" data-section-id="section-pitfalls"> - <h2 class="section-title" id="section-pitfalls"><i class="bi bi-exclamation-diamond-fill"></i> // VIII. Threat Vectors & Failure Modes</h2> + <h2 class="section-title" id="section-pitfalls"><i class="bi bi-exclamation-diamond-fill"></i> // IX. How People Lose Bitcoin (Avoid These!)</h2> <div class="row"> <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-pitfall" id="card-pitfall-seed"> <div class="card-body"> - <h5><i class="bi bi-journal-x"></i> Seed Phrase Compromise/Loss</h5> + <h5><i class="bi bi-journal-x"></i> Seed Phrase Loss / Compromise</h5> <div class="card-content-wrapper"> - <p class="summary"><strong class="cons">FAILURE MODE #1:</strong> Physical loss/damage, incorrect backup transcription, backing up wrong initial seed, lost/forgotten passphrase.</p> + <p class="summary"><strong class="cons">#1 CAUSE OF LOSS:</strong> Losing the physical backup, damage (fire/water), incorrect transcription, storing it digitally (photo/file/cloud -> HACKED), forgetting passphrase.</p> </div> </div> </div> @@ -1076,133 +1206,138 @@ <div class="col-lg-4 col-md-6"> <div class="info-card btc-type-pitfall" id="card-pitfall-phishing"> <div class="card-body"> - <h5><i class="bi bi-broadcast"></i> Phishing / Social Engineering</h5> + <h5><i class="bi bi-broadcast"></i> Phishing / Scams</h5> <div class="card-content-wrapper"> - <p class="summary"><strong class="cons">FAILURE MODE #2:</strong> User Deception -> Seed revealed to fake site/app/support. Results in immediate, total loss.</p> + <p class="summary"><strong class="cons">#2 CAUSE OF LOSS:</strong> Being tricked into revealing your seed phrase or private keys to fake websites, fake apps, fake support agents, or malicious software.</p> </div> </div> </div> </div> <div class="col-lg-4 col-md-6"> - <div class="info-card btc-type-pitfall" id="card-pitfall-device"> + <div class="info-card btc-type-pitfall" id="card-pitfall-malware"> <div class="card-body"> - <h5><i class="bi bi-hdd-rack-fill"></i> Device/Software Failure</h5> + <h5><i class="bi bi-virus"></i> Malware on Computer/Phone</h5> <div class="card-content-wrapper"> - <p class="summary">Forgotten PIN (requires seed), accidental wipe <span class="term">without verified backup</span>, rare critical software bugs.</p> + <p class="summary">Viruses stealing keys from software wallets, clipboard hijackers changing pasted addresses, fake wallet apps, keyloggers capturing passwords.</p> </div> </div> </div> </div> <div class="col-lg-4 col-md-6"> - <div class="info-card btc-type-pitfall" id="card-pitfall-malware"> + <div class="info-card btc-type-pitfall" id="card-pitfall-physical"> <div class="card-body"> - <h5><i class="bi bi-virus"></i> Host System Malware</h5> + <h5><i class="bi bi-person-fill-x"></i> Physical Theft / Coercion</h5> <div class="card-content-wrapper"> - <p class="summary">Clipboard hijacker (verify HW screen!), keyloggers (risk SW), fake wallet apps.</p> + <p class="summary">Theft of poorly secured seed phrase backups, theft of hardware wallet (PIN/Passphrase is defense), being forced to reveal keys ("$5 wrench attack").</p> </div> </div> </div> </div> - <div class="col-lg-4 col-md-6"> - <div class="info-card btc-type-pitfall" id="card-pitfall-physical"> + <div class="col-lg-4 col-md-6"> + <div class="info-card btc-type-pitfall" id="card-pitfall-device"> <div class="card-body"> - <h5><i class="bi bi-person-fill-x"></i> Physical Compromise</h5> + <h5><i class="bi bi-hdd-rack-fill"></i> Device Issues (Without Backup)</h5> <div class="card-content-wrapper"> - <p class="summary">Seed backup theft/discovery, unsecured HW theft (PIN/Passphrase=defense), coercion, insider theft.</p> + <p class="summary">Forgetting PIN after too many tries (requires seed restore), device failure/damage <span class="term">without having a verified seed backup</span>, accidental factory reset.</p> </div> </div> </div> </div> <div class="col-lg-4 col-md-6"> - <div class="info-card btc-type-pitfall" id="card-pitfall-supply"> + <div class="info-card btc-type-pitfall" id="card-pitfall-estate"> <div class="card-body"> - <h5><i class="bi bi-truck"></i> Supply Chain / Bad Vendor</h5> + <h5><i class="bi bi-person-slash"></i> Lack of Inheritance Plan</h5> <div class="card-content-wrapper"> - <p class="summary">Tampered device (buy direct!), using flawed/malicious/unknown wallet interfaces.</p> + <p class="summary">Owner passes away or becomes incapacitated without leaving clear, secure instructions for heirs to access the funds. Bitcoin becomes permanently lost.</p> </div> </div> </div> </div> <div class="col-lg-4 col-md-6"> - <div class="info-card btc-type-pitfall" id="card-pitfall-estate"> + <div class="info-card btc-type-pitfall" id="card-pitfall-supply"> <div class="card-body"> - <h5><i class="bi bi-person-slash"></i> Succession Failure</h5> + <h5><i class="bi bi-truck"></i> Supply Chain / Bad Vendor</h5> <div class="card-content-wrapper"> - <p class="summary">Lack of estate planning -> Funds permanently inaccessible after owner death/incapacity.</p> + <p class="summary">Receiving a tampered hardware wallet (always buy direct!), using insecure or malicious wallet software from unknown sources.</p> </div> </div> </div> </div> + <div class="col-lg-4 col-md-6"> {/* Placeholder/Summary Card */} + <div class="info-card btc-type-pitfall" id="card-pitfall-summary"> + <div class="card-body"> + <h5><i class="bi bi-shield-exclamation"></i> Prevention is Key</h5> + <div class="card-content-wrapper"> + <p class="summary">Most losses are preventable through careful seed phrase management, vigilance against scams, using reputable hardware, and having robust backup plans.</p> + </div> + </div> + </div> + </div> </div> <!-- /.row --> </div> <!-- /.schema-container --> <!-- ======================= --> - <!-- SECTION IX: Glossary --> + <!-- UPDATED SECTION X: Glossary --> <!-- ======================= --> <div class="schema-container cat-glossary" data-section-id="section-glossary"> - <h2 class="section-title" id="section-glossary"><i class="bi bi-book-half"></i> // IX. Terminology Lexicon</h2> + <h2 class="section-title" id="section-glossary"><i class="bi bi-book-half"></i> // X. Terminology Glossary</h2> <div class="row"> <div class="col-12"> <div class="info-card btc-type-glossary" id="card-glossary"> <div class="card-body"> - <h5 class="text-center"><i class="bi bi-translate"></i> Protocol Glossary</h5> + <h5 class="text-center"><i class="bi bi-translate"></i> Key Terms Defined</h5> <div class="card-content-wrapper"> - <p class="summary text-center">Definitions for core Bitcoin & Wallet terminology.</p> + <p class="summary text-center">Quick definitions for common Bitcoin and wallet terms used in this guide.</p> <button class="btn btn-sm details-toggle mx-auto" type="button" data-bs-toggle="collapse" data-bs-target="#collapseGlossary" aria-expanded="false" aria-controls="collapseGlossary"> - Access Lexicon <i class="bi bi-chevron-down"></i> + View Glossary <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseGlossary"> <dl> - <!-- Populate DL with terms from outline --> - <dt>Address</dt><dd>Identifier used to receive Bitcoin (e.g., starts with 1, 3, bc1q, bc1p).</dd> - <dt>Air Gap</dt><dd>Keeping a device (signer) physically isolated from network connections.</dd> - <dt>BIP-32</dt><dd>Standard for Hierarchical Deterministic (HD) wallets, deriving keys from a master seed.</dd> - <dt>BIP-39</dt><dd>Standard for mnemonic seed phrases (12/24 words) representing the master seed.</dd> - <dt>BIP-44/84/86</dt><dd>Standards defining derivation paths for different address types (Legacy, SegWit, Taproot).</dd> - <dt>BIP-125</dt><dd>Replace-By-Fee (RBF) standard.</dd> - <dt>BIP-174</dt><dd>Partially Signed Bitcoin Transaction (PSBT) format standard.</dd> + <!-- Added/Updated terms emphasized --> + <dt>Address</dt><dd>Identifier used to receive Bitcoin (e.g., starts with 1, 3, bc1q, bc1p). Generated from your public key.</dd> + <dt>Air Gap</dt><dd>Keeping a device (like a hardware wallet or dedicated signing computer) physically isolated from network connections (internet, Bluetooth).</dd> + <dt>BIP (Bitcoin Improvement Proposal)</dt><dd>Standards documents for the Bitcoin protocol (e.g., BIP-32, BIP-39).</dd> + <dt>BIP-32</dt><dd>Standard for Hierarchical Deterministic (HD) wallets, allowing many keys to be derived from a single master seed.</dd> + <dt>BIP-39</dt><dd>Standard for mnemonic seed phrases (12/24 words) used to back up and recover HD wallets.</dd> + <dt>BIP-44/84/86</dt><dd>Standards defining specific ways (derivation paths) to organize keys for different address types (Legacy, SegWit, Taproot) within a BIP-32 wallet.</dd> <dt>Bitcoin Core</dt><dd>The primary, reference implementation of the Bitcoin full node software.</dd> - <dt>Block Explorer</dt><dd>Website to view blockchain data (transactions, addresses, blocks).</dd> - <dt>Blockchain</dt><dd>The distributed, public ledger recording all Bitcoin transactions.</dd> - <dt>Cold Storage</dt><dd>Storing private keys offline.</dd> - <dt>Coin Control</dt><dd>Manually selecting specific UTXOs for spending.</dd> - <dt>Confirmation</dt><dd>Inclusion of a transaction in a block on the blockchain.</dd> - <dt>CPFP</dt><dd>Child-Pays-For-Parent. Spending an unconfirmed input with a high fee to accelerate parent confirmation.</dd> - <dt>Custodial</dt><dd>A third party holds your private keys (e.g., an exchange).</dd> - <dt>Derivation Path</dt><dd>Instructions for deriving specific keys/addresses from the master seed (e.g., m/84'/0'/0'/0/0).</dd> - <dt>Electrum</dt><dd>Popular, feature-rich software wallet.</dd> - <dt>Fee Rate (sat/vB)</dt><dd>Transaction fee measured in satoshis per virtual byte.</dd> - <dt>Full Node</dt><dd>Software that independently validates all Bitcoin transactions and blocks.</dd> - <dt>Hardware Wallet</dt><dd>Physical device securing private keys offline.</dd> - <dt>HD Wallet</dt><dd>Hierarchical Deterministic wallet, derives keys from a single seed (BIP-32).</dd> - <dt>Hot Wallet</dt><dd>Wallet where keys are stored on an internet-connected device.</dd> - <dt>Keys</dt><dd>Private Key (secret, for signing) and Public Key (sharable, for receiving).</dd> - <dt>Ledger</dt><dd>Popular hardware wallet manufacturer.</dd> - <dt>Lightning Network</dt><dd>Layer-2 protocol for fast, cheap Bitcoin transactions (uses different wallet types/concepts).</dd> - <dt>Mempool</dt><dd>Pool of unconfirmed transactions waiting for miners.</dd> - <dt>Multisignature (Multisig)</dt><dd>Requires multiple keys (M-of-N) to authorize a transaction.</dd> - <dt>Non-Custodial</dt><dd>You control your own private keys/seed phrase.</dd> - <dt>Passphrase (BIP-39)</dt><dd>Optional secret word/phrase added to seed, creating a hidden wallet ("25th word").</dd> - <dt>Private Key</dt><dd>The secret data allowing spending of Bitcoin.</dd> - <dt>PSBT</dt><dd>Partially Signed Bitcoin Transaction format.</dd> - <dt>Public Key</dt><dd>Cryptographic key derived from private key, used to generate addresses.</dd> - <dt>QR Code</dt><dd>Square barcode often used to represent addresses or transaction data.</dd> - <dt>RBF</dt><dd>Replace-By-Fee. Bumping the fee of an unconfirmed transaction.</dd> - <dt>Satoshis (Sats)</dt><dd>Smallest unit of Bitcoin (1 BTC = 100,000,000 sats).</dd> - <dt>Secure Element (SE)</dt><dd>Tamper-resistant chip designed to securely store cryptographic keys.</dd> - <dt>Seed Phrase</dt><dd>12/24 word mnemonic backup for the master private key (BIP-39).</dd> - <dt>Shamir Backup (SLIP-39)</dt><dd>Splits seed into multiple shares, requiring a threshold for recovery.</dd> - <dt>Signature</dt><dd>Cryptographic proof generated using a private key to authorize a transaction.</dd> - <dt>Software Wallet</dt><dd>Wallet application running on a computer or phone.</dd> - <dt>Sparrow Wallet</dt><dd>Desktop software wallet focused on security and privacy.</dd> - <dt>Specter Desktop</dt><dd>Desktop software wallet focused on multisig and hardware wallet interaction.</dd> - <dt>Taproot</dt><dd>Recent Bitcoin protocol upgrade enhancing privacy and scripting capabilities (P2TR addresses).</dd> - <dt>Testnet</dt><dd>Parallel Bitcoin network for testing with valueless coins.</dd> - <dt>Trezor</dt><dd>Pioneering hardware wallet manufacturer.</dd> - <dt>UTXO</dt><dd>Unspent Transaction Output. An individual "chunk" of bitcoin.</dd> - <dt>Watch-Only Wallet</dt><dd>Wallet loaded with public keys/addresses to monitor balance/transactions, but cannot spend.</dd> + <dt>Block Explorer</dt><dd>A website or tool used to view information on the public blockchain (transactions, addresses, blocks).</dd> + <dt>Blockchain</dt><dd>The distributed, public, and immutable ledger that records all Bitcoin transactions.</dd> + <dt>Cold Storage</dt><dd><strong class="term">Storing private keys completely offline, away from internet connections.</strong> Typically achieved using hardware wallets, paper wallets (risky), or air-gapped devices.</dd> + <dt>Coin Control</dt><dd>Manually selecting specific UTXOs (unspent chunks of Bitcoin) to use as inputs when creating a transaction.</dd> + <dt>Confirmation</dt><dd>The inclusion of a transaction in a block added to the blockchain. More confirmations increase transaction finality.</dd> + <dt>CPFP (Child-Pays-For-Parent)</dt><dd>A fee-bumping technique where you spend an unconfirmed incoming transaction (the 'child') with a high fee, incentivizing miners to confirm both the child and its stuck 'parent'.</dd> + <dt>Custodial</dt><dd>A service where a third party (like an exchange) holds your private keys for you. <strong class="critical">You don't truly control the Bitcoin.</strong></dd> + <dt>Derivation Path</dt><dd>A specific "route" defined by standards like BIP-44/84/86, telling the wallet how to find/generate specific keys/addresses from the master seed (e.g., m/84'/0'/0'/0/0).</dd> + <dt>Fee Rate (sat/vB)</dt><dd>The price paid for transaction inclusion, measured in satoshis per virtual byte of transaction data size.</dd> + <dt>Full Node</dt><dd>Software that downloads and independently validates the entire Bitcoin blockchain according to the network's consensus rules.</dd> + <dt>Hardware Wallet</dt><dd><strong class="term">A physical device designed to securely store private keys offline (cold storage) and sign transactions without exposing keys to a connected computer/phone.</strong></dd> + <dt>HD Wallet (Hierarchical Deterministic)</dt><dd>A wallet using BIP-32, where all keys and addresses are derived from a single master seed (backed up by the BIP-39 seed phrase).</dd> + <dt>Hot Wallet</dt><dd><strong class="term">A wallet where the private keys are stored on a device that is connected to the internet (e.g., software wallets on phones/computers).</strong> More convenient but less secure than cold storage.</dd> + <dt>Keys (Private/Public)</dt><dd>Cryptographic pair: Private Key (secret, signs transactions), Public Key (sharable, derives addresses).</dd> + <dt>Mempool</dt><dd>The "waiting room" for broadcasted transactions before they are confirmed in a block by miners.</dd> + <dt>Multisignature (Multisig)</dt><dd>A setup requiring signatures from multiple private keys (M out of N total keys, e.g., 2-of-3) to authorize a transaction.</dd> + <dt>Non-Custodial</dt><dd>A wallet where <strong class="term">YOU</strong> control your own private keys and seed phrase (<span class="term">Self-Custody</span>).</dd> + <dt>OPSEC (Operations Security)</dt><dd>Practices and procedures to protect sensitive information (like your seed phrase and keys) and reduce risks.</dd> + <dt>Passphrase (BIP-39)</dt><dd>An optional, user-defined "25th word" added to the seed phrase to create a hidden wallet. <strong class="critical">Lose the passphrase, lose the funds in that hidden wallet.</strong></dd> + <dt>Private Key</dt><dd>The secret data that proves ownership and allows spending of Bitcoin associated with specific addresses.</dd> + <dt>PSBT (Partially Signed Bitcoin Transaction)</dt><dd>A standard format (BIP-174) for passing transactions between signers or devices without revealing sensitive key information, used in multisig and air-gapped setups.</dd> + <dt>Public Key</dt><dd>Derived from the private key, used to generate receiving addresses. Safe to share.</dd> + <dt>QR Code</dt><dd>A square barcode often used to easily share Bitcoin addresses or transaction data.</dd> + <dt>RBF (Replace-By-Fee)</dt><dd>A fee-bumping technique (BIP-125) allowing you to replace your own unconfirmed transaction with a new one that includes a higher fee.</dd> + <dt>Satoshis (Sats)</dt><dd>The smallest divisible unit of Bitcoin. 1 BTC = 100,000,000 sats.</dd> + <dt>Secure Element (SE)</dt><dd>A specialized, tamper-resistant chip found in some hardware wallets, designed to securely store cryptographic keys.</dd> + <dt>Seed Phrase</dt><dd><strong class="term">The mnemonic backup (usually 12 or 24 words, BIP-39) for your HD wallet's master private key. Your ultimate recovery tool.</strong></dd> + <dt>Self-Custody</dt><dd><strong class="term">The practice of holding and controlling your own private keys, rather than relying on a third party.</strong></dd> + <dt>Shamir Backup (SLIP-39)</dt><dd>A standard for splitting a seed into multiple 'shares', requiring a certain threshold (e.g., 3-of-5) to recover the wallet. Offers redundancy.</dd> + <dt>Signature</dt><dd>A piece of cryptographic data created using a private key to prove ownership and authorize a transaction.</dd> + <dt>Software Wallet</dt><dd>A wallet application running on a general-purpose device like a computer or smartphone (typically a hot wallet).</dd> + <dt>Taproot</dt><dd>A recent Bitcoin protocol upgrade (P2TR addresses, starting bc1p) improving efficiency and privacy potential for complex transactions.</dd> + <dt>Testnet</dt><dd>A parallel Bitcoin network used for testing purposes, where coins have no real value.</dd> + <dt>UTXO (Unspent Transaction Output)</dt><dd>An individual "chunk" of bitcoin recorded on the blockchain that can be spent as an input in a new transaction.</dd> + <dt>Watch-Only Wallet</dt><dd>A wallet loaded only with public keys or addresses. It can track balances and transactions but cannot sign or spend funds.</dd> </dl> </div> </div> @@ -1211,55 +1346,53 @@ </div> <!-- /.schema-container --> <!-- ========================== --> - <!-- SECTION X: Further Resources --> + <!-- UPDATED SECTION XI: Further Resources --> <!-- ========================== --> <div class="schema-container cat-resources" data-section-id="section-resources"> - <h2 class="section-title" id="section-resources"><i class="bi bi-compass-fill"></i> // X. External Network Nodes</h2> + <h2 class="section-title" id="section-resources"><i class="bi bi-compass-fill"></i> // XI. Further Resources & Tools</h2> <div class="row"> <div class="col-12"> <div class="info-card btc-type-resource" id="card-resources"> <div class="card-body"> - <h5 class="text-center"><i class="bi bi-link-45deg"></i> Intelligence & Tools</h5> + <h5 class="text-center"><i class="bi bi-link-45deg"></i> Recommended Links</h5> <div class="card-content-wrapper"> - <p class="summary text-center">Links to essential wallet interfaces, block explorers, educational archives, and author's datasets.</p> + <p class="summary text-center">Links to reputable wallet software, hardware vendors, block explorers, educational sites, and related content.</p> <button class="btn btn-sm details-toggle mx-auto" type="button" data-bs-toggle="collapse" data-bs-target="#collapseResources" aria-expanded="false" aria-controls="collapseResources"> - Access Resource Index <i class="bi bi-chevron-down"></i> + Browse Links <i class="bi bi-chevron-down"></i> </button> </div> </div> <div class="collapse collapse-content" id="collapseResources"> - <h6>A. Wallet Interfaces (Software):</h6> + <h6>A. Recommended Software Wallets (Non-Custodial):</h6> <ul> - <li><a href="https://electrum.org/" target="_blank" rel="noopener noreferrer">Electrum</a></li> - <li><a href="https://sparrowwallet.com/" target="_blank" rel="noopener noreferrer">Sparrow Wallet</a></li> - <li><a href="https://specter.solutions/" target="_blank" rel="noopener noreferrer">Specter Desktop</a></li> - <li><a href="https://bluewallet.io/" target="_blank" rel="noopener noreferrer">BlueWallet</a></li> - <li><a href="https://nunchuk.io/" target="_blank" rel="noopener noreferrer">Nunchuk</a> (Multisig focus)</li> + <li>Desktop: <a href="https://sparrowwallet.com/" target="_blank" rel="noopener noreferrer">Sparrow Wallet</a> (Feature-rich, Privacy/Node focus), <a href="https://electrum.org/" target="_blank" rel="noopener noreferrer">Electrum</a> (Long-standing, Advanced), <a href="https://specter.solutions/" target="_blank" rel="noopener noreferrer">Specter Desktop</a> (Multisig/HW focus)</li> + <li>Mobile: <a href="https://bluewallet.io/" target="_blank" rel="noopener noreferrer">BlueWallet</a> (User-friendly, versatile), <a href="https://muun.com/" target="_blank" rel="noopener noreferrer">Muun Wallet</a> (Simple, Lightning focus), <a href="https://blockstream.com/green/" target="_blank" rel="noopener noreferrer">Blockstream Green</a> (Multisig options)</li> + <li>Multisig Coordinator: <a href="https://nunchuk.io/" target="_blank" rel="noopener noreferrer">Nunchuk</a> (Mobile/Desktop)</li> </ul> - <h6>B. Hardware Modules:</h6> + <h6>B. Reputable Hardware Wallet Vendors (Buy Direct!):</h6> <ul> <li><a href="https://trezor.io/" target="_blank" rel="noopener noreferrer">Trezor</a></li> - <li><a href="https://coldcard.com/" target="_blank" rel="noopener noreferrer">Coldcard</a></li> + <li><a href="https://coldcard.com/" target="_blank" rel="noopener noreferrer">Coldcard</a> (Coinkite)</li> <li><a href="https://www.ledger.com/" target="_blank" rel="noopener noreferrer">Ledger</a></li> - <li><a href="https://bitbox.swiss/" target="_blank" rel="noopener noreferrer">BitBox</a></li> - <li><a href="https://seedsigner.com/" target="_blank" rel="noopener noreferrer">Seedsigner</a></li> + <li><a href="https://bitbox.swiss/" target="_blank" rel="noopener noreferrer">BitBox</a> (Shift Crypto)</li> <li><a href="https://blockstream.com/jade/" target="_blank" rel="noopener noreferrer">Blockstream Jade</a></li> - <li><a href="https://foundationdevices.com/" target="_blank" rel="noopener noreferrer">Foundation Devices</a></li> + <li><a href="https://foundationdevices.com/" target="_blank" rel="noopener noreferrer">Foundation Devices</a> (Passport)</li> + <li><a href="https://seedsigner.com/" target="_blank" rel="noopener noreferrer">Seedsigner</a> (DIY Project)</li> </ul> - <h6>C. Network Explorers:</h6> + <h6>C. Block Explorers:</h6> <ul> - <li><a href="https://mempool.space/" target="_blank" rel="noopener noreferrer">mempool.space</a></li> + <li><a href="https://mempool.space/" target="_blank" rel="noopener noreferrer">mempool.space</a> (Popular, comprehensive)</li> <li><a href="https://blockstream.info/" target="_blank" rel="noopener noreferrer">Blockstream.info</a></li> </ul> - <h6>D. Knowledge Archives:</h6> + <h6>D. Educational Resources:</h6> <ul> - <li><a href="https://bitcoin.org/en/" target="_blank" rel="noopener noreferrer">Bitcoin.org</a></li> - <li><a href="https://bitcoin.page/" target="_blank" rel="noopener noreferrer">bitcoin.page</a></li> - <li><a href="https://www.lopp.net/bitcoin-information.html" target="_blank" rel="noopener noreferrer">Lopp.net Bitcoin Resources</a></li> - <li><a href="https://en.bitcoin.it/wiki/Main_Page" target="_blank" rel="noopener noreferrer">Bitcoin Wiki</a></li> - <li><a href="https://bitcoinops.org/" target="_blank" rel="noopener noreferrer">Bitcoin Optech</a> (Technical)</li> + <li><a href="https://bitcoin.org/en/" target="_blank" rel="noopener noreferrer">Bitcoin.org</a> (Official site, good starting point)</li> + <li><a href="https://bitcoin.page/" target="_blank" rel="noopener noreferrer">bitcoin.page</a> (Curated resources)</li> + <li><a href="https://www.lopp.net/bitcoin-information.html" target="_blank" rel="noopener noreferrer">Lopp.net Bitcoin Resources</a> (Very comprehensive list)</li> + <li><a href="https://en.bitcoin.it/wiki/Main_Page" target="_blank" rel="noopener noreferrer">Bitcoin Wiki</a> (Community-maintained)</li> + <li><a href="https://bitcoinops.org/" target="_blank" rel="noopener noreferrer">Bitcoin Optech</a> (Technical developments)</li> </ul> - <h6>E. Author's Datasets:</h6> + <h6>E. Related Content / Author Links (Original):</h6> <ul> <li><a href="https://walletrecovery.info/articles/" target="_blank" rel="noopener noreferrer">WalletRecovery.info Articles</a></li> <li><a href="https://davidveksler.substack.com/archive" target="_blank" rel="noopener noreferrer">David Veksler Substack Archive</a></li> @@ -1283,9 +1416,11 @@ document.addEventListener('DOMContentLoaded', () => { const footerYearEl = document.getElementById('footer-year'); if (footerYearEl) { - footerYearEl.textContent = `Cyberpunk Wallet Matrix v2.1 - © ${new Date().getFullYear()} David Veksler`; + // Updated Footer Text + footerYearEl.textContent = `Bitcoin Wallet Cheatsheet v2.2 - Secure Self-Custody Guide - © ${new Date().getFullYear()} David Veksler (Content Refined)`; } + // JS for collapse toggle icons remains unchanged const collapseElements = document.querySelectorAll('.collapse'); collapseElements.forEach(collapseEl => { const button = document.querySelector(`.details-toggle[data-bs-target="#${collapseEl.id}"]`); @@ -1295,7 +1430,11 @@ document.addEventListener('DOMContentLoaded', () => { icon.classList.toggle('bi-chevron-up', isShown); icon.classList.toggle('bi-chevron-down', !isShown); }; + // Set initial state based on whether the element is initially shown + // Check if the collapse element has the 'show' class on initial load updateIcon(collapseEl.classList.contains('show')); + + // Update icon when shown/hidden collapseEl.addEventListener('show.bs.collapse', () => updateIcon(true)); collapseEl.addEventListener('hide.bs.collapse', () => updateIcon(false)); }