add Bitkey
· 1 year ago
c8e3ddc9c7b0a683241f0ac49e42ec3e44211291
Parent:
4450d6ff7
1 file changed +3976 −1502
- bitcoin-wallet.html +3976 −1502
Diff
--- a/bitcoin-wallet.html +++ b/bitcoin-wallet.html @@ -1,1628 +1,4102 @@ <!DOCTYPE html> <html lang="en"> -<head> - <meta charset="UTF-8"> - <meta name="viewport" content="width=device-width, initial-scale=1.0"> + <head> + <meta charset="UTF-8" /> + <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <!-- 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."> + <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." + /> <!-- CORRECTED Canonical URL --> - <link rel="canonical" href="https://cheatsheets.davidveksler.com/bitcoin-wallet.html"> + <link + rel="canonical" + href="https://cheatsheets.davidveksler.com/bitcoin-wallet.html" + /> <!-- Social Media Metadata (Updated URL) --> - <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-wallet.html"> - <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: 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."> + <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-wallet.html" + /> + <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: 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 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 + 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 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 */ + /* --- CSS Styles remain unchanged as requested --- */ + @keyframes subtleDataStream { + 0% { + background-position: 0 0; } + 100% { + background-position: 0 60px; + } /* Vertical movement for stream */ + } - @keyframes pulseGlowIntense { - 0% { box-shadow: 0 0 8px 1px var(--category-color-glow), 0 4px 10px rgba(0,0,0, 0.4), inset 0 0 5px rgba(0,0,0,0.2); } - 50% { box-shadow: 0 0 20px 5px var(--category-color-glow), 0 6px 15px rgba(0,0,0, 0.5), inset 0 0 10px rgba(0,0,0,0.3); } - 100% { box-shadow: 0 0 8px 1px var(--category-color-glow), 0 4px 10px rgba(0,0,0, 0.4), inset 0 0 5px rgba(0,0,0,0.2); } + @keyframes pulseGlowIntense { + 0% { + box-shadow: 0 0 8px 1px var(--category-color-glow), + 0 4px 10px rgba(0, 0, 0, 0.4), inset 0 0 5px rgba(0, 0, 0, 0.2); } + 50% { + box-shadow: 0 0 20px 5px var(--category-color-glow), + 0 6px 15px rgba(0, 0, 0, 0.5), inset 0 0 10px rgba(0, 0, 0, 0.3); + } + 100% { + box-shadow: 0 0 8px 1px var(--category-color-glow), + 0 4px 10px rgba(0, 0, 0, 0.4), inset 0 0 5px rgba(0, 0, 0, 0.2); + } + } - @keyframes flowLineGradient { - 0% { background-position: -100% 0; } - 100% { background-position: 100% 0; } + @keyframes flowLineGradient { + 0% { + background-position: -100% 0; } + 100% { + background-position: 100% 0; + } + } - :root { - /* Core Palette - Deeper Cyberpunk Dark */ - --bg-main: #0a0c10; /* Even darker */ - --bg-container: #11151c; /* Darker gray/blue */ - --bg-card: #1c2128; /* Dark slate gray */ - --bg-card-content: #22272e; /* Slightly lighter slate */ - --text-primary: #d1d5db; /* Light gray for readability */ - --text-secondary: #9ca3af; /* Mid gray */ - --text-heading: #f0f6fc; /* Brighter off-white */ - --border-color: #373e47; /* Subtle border color */ - --accent-primary: #6cb6ff; /* Lighter Vibrant Blue */ - --accent-primary-dark: #58a6ff; - --accent-primary-glow: rgba(108, 182, 255, 0.6); - --critical-color: #ff7b72; /* Brighter Neon Red */ - --rule-border-color: var(--critical-color); - --rule-bg-color: rgba(255, 123, 114, 0.15); /* Slightly stronger bg */ - --btc-orange: #f7931a; - --btc-orange-glow: rgba(247, 147, 26, 0.7); - --btc-orange-subtle-glow: rgba(247, 147, 26, 0.4); + :root { + /* Core Palette - Deeper Cyberpunk Dark */ + --bg-main: #0a0c10; /* Even darker */ + --bg-container: #11151c; /* Darker gray/blue */ + --bg-card: #1c2128; /* Dark slate gray */ + --bg-card-content: #22272e; /* Slightly lighter slate */ + --text-primary: #d1d5db; /* Light gray for readability */ + --text-secondary: #9ca3af; /* Mid gray */ + --text-heading: #f0f6fc; /* Brighter off-white */ + --border-color: #373e47; /* Subtle border color */ + --accent-primary: #6cb6ff; /* Lighter Vibrant Blue */ + --accent-primary-dark: #58a6ff; + --accent-primary-glow: rgba(108, 182, 255, 0.6); + --critical-color: #ff7b72; /* Brighter Neon Red */ + --rule-border-color: var(--critical-color); + --rule-bg-color: rgba(255, 123, 114, 0.15); /* Slightly stronger bg */ + --btc-orange: #f7931a; + --btc-orange-glow: rgba(247, 147, 26, 0.7); + --btc-orange-subtle-glow: rgba(247, 147, 26, 0.4); + /* Bitcoin Category Colors (Neon Emphasis) */ + --btc-color-concept: #9ca3af; + --btc-glow-concept: rgba(156, 163, 175, 0.5); + --btc-color-hot: #ff7b72; + --btc-glow-hot: rgba(255, 123, 114, 0.7); /* Neon Red */ + --btc-color-cold: #6cb6ff; + --btc-glow-cold: rgba(108, 182, 255, 0.6); /* Neon Blue */ + --btc-color-operations: #56d364; + --btc-glow-operations: rgba(86, 211, 100, 0.6); /* Neon Green */ + --btc-color-security: #f778ba; + --btc-glow-security: rgba(247, 120, 186, 0.6); /* Neon Pink */ + --btc-color-advanced: #c39ac5; + --btc-glow-advanced: rgba(195, 154, 197, 0.6); /* Neon Purple */ + --btc-color-comparison: #79c0ff; + --btc-glow-comparison: rgba(121, 192, 255, 0.6); /* Light Neon Blue */ + --btc-color-pitfalls: #f7c85c; + --btc-glow-pitfalls: rgba(247, 200, 92, 0.7); /* Neon Yellow */ + --btc-color-glossary: #8b949e; + --btc-glow-glossary: rgba(139, 148, 158, 0.5); + --btc-color-resources: #56d364; + --btc-glow-resources: rgba(86, 211, 100, 0.6); /* Neon Green again */ - /* Bitcoin Category Colors (Neon Emphasis) */ - --btc-color-concept: #9ca3af; --btc-glow-concept: rgba(156, 163, 175, 0.5); - --btc-color-hot: #ff7b72; --btc-glow-hot: rgba(255, 123, 114, 0.7); /* Neon Red */ - --btc-color-cold: #6cb6ff; --btc-glow-cold: rgba(108, 182, 255, 0.6); /* Neon Blue */ - --btc-color-operations: #56d364; --btc-glow-operations: rgba(86, 211, 100, 0.6); /* Neon Green */ - --btc-color-security: #f778ba; --btc-glow-security: rgba(247, 120, 186, 0.6); /* Neon Pink */ - --btc-color-advanced: #c39ac5; --btc-glow-advanced: rgba(195, 154, 197, 0.6); /* Neon Purple */ - --btc-color-comparison: #79c0ff; --btc-glow-comparison: rgba(121, 192, 255, 0.6); /* Light Neon Blue */ - --btc-color-pitfalls: #f7c85c; --btc-glow-pitfalls: rgba(247, 200, 92, 0.7); /* Neon Yellow */ - --btc-color-glossary: #8b949e; --btc-glow-glossary: rgba(139, 148, 158, 0.5); - --btc-color-resources: #56d364; --btc-glow-resources: rgba(86, 211, 100, 0.6); /* Neon Green again */ + --category-color: var(--btc-color-concept); /* Default */ + --category-color-glow: var(--btc-glow-concept); + color-scheme: dark; + } - --category-color: var(--btc-color-concept); /* Default */ - --category-color-glow: var(--btc-glow-concept); - color-scheme: dark; - } + body { + background-color: var(--bg-main); + /* Animated "data stream" background */ + background-image: linear-gradient( + 0deg, + rgba(13, 17, 23, 0) 0%, + rgba(88, 166, 255, 0.03) 50%, + rgba(13, 17, 23, 0) 100% + ), + linear-gradient(90deg, rgba(48, 54, 61, 0.1) 1px, transparent 1px), + linear-gradient(0deg, rgba(48, 54, 61, 0.1) 1px, transparent 1px); + background-size: 100% 60px, 40px 40px, 40px 40px; /* stream height, grid x, grid y */ + animation: subtleDataStream 4s linear infinite; - body { - background-color: var(--bg-main); - /* Animated "data stream" background */ - background-image: - linear-gradient(0deg, rgba(13, 17, 23, 0) 0%, rgba(88, 166, 255, 0.03) 50%, rgba(13, 17, 23, 0) 100%), - linear-gradient(90deg, rgba(48, 54, 61, 0.1) 1px, transparent 1px), - linear-gradient(0deg, rgba(48, 54, 61, 0.1) 1px, transparent 1px); - background-size: 100% 60px, 40px 40px, 40px 40px; /* stream height, grid x, grid y */ - animation: subtleDataStream 4s linear infinite; + color: var(--text-primary); + font-family: "Inter", -apple-system, BlinkMacSystemFont, "Segoe UI", + Roboto, Helvetica, Arial, sans-serif; /* Modern Sans-serif */ + padding-bottom: 3rem; + font-size: 15px; + box-sizing: border-box; + line-height: 1.7; /* Increased line height */ + } + *, + *::before, + *::after { + box-sizing: inherit; + } - color: var(--text-primary); - font-family: 'Inter', -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Helvetica, Arial, sans-serif; /* Modern Sans-serif */ - padding-bottom: 3rem; - font-size: 15px; - box-sizing: border-box; - line-height: 1.7; /* Increased line height */ - } - *, *::before, *::after { box-sizing: inherit; } - - /* --- Bitcoin Header Styling --- */ - .page-header { - background: - linear-gradient(135deg, rgba(247, 147, 26, 0.08) 0%, transparent 30%), - linear-gradient(225deg, rgba(247, 147, 26, 0.05) 0%, transparent 30%), - linear-gradient(45deg, rgba(48, 54, 61, 0.1) 0%, transparent 50%), - var(--bg-container); - backdrop-filter: blur(2px); - padding: 3rem 1.5rem; - text-align: center; - border-bottom: 1px solid var(--border-color); - margin-bottom: 3rem; - position: relative; - z-index: 10; - box-shadow: 0 5px 25px rgba(0, 0, 0, 0.4), inset 0 0 15px rgba(0,0,0,0.3); - overflow: hidden; - } + /* --- Bitcoin Header Styling --- */ + .page-header { + background: linear-gradient( + 135deg, + rgba(247, 147, 26, 0.08) 0%, + transparent 30% + ), + linear-gradient(225deg, rgba(247, 147, 26, 0.05) 0%, transparent 30%), + linear-gradient(45deg, rgba(48, 54, 61, 0.1) 0%, transparent 50%), + var(--bg-container); + backdrop-filter: blur(2px); + padding: 3rem 1.5rem; + text-align: center; + border-bottom: 1px solid var(--border-color); + margin-bottom: 3rem; + position: relative; + z-index: 10; + box-shadow: 0 5px 25px rgba(0, 0, 0, 0.4), + inset 0 0 15px rgba(0, 0, 0, 0.3); + overflow: hidden; + } - .page-header::before, - .page-header::after { - content: ''; - position: absolute; - width: 20px; height: 20px; - border-color: var(--btc-orange); border-style: solid; - opacity: 0.7; filter: drop-shadow(0 0 4px var(--btc-orange-glow)); - transition: all 0.3s ease; - } - .page-header::before { top: 10px; left: 10px; border-width: 2px 0 0 2px; border-top-left-radius: 5px; } - .page-header::after { bottom: 10px; right: 10px; border-width: 0 2px 2px 0; border-bottom-right-radius: 5px; } - .page-header:hover::before, - .page-header:hover::after { width: 25px; height: 25px; opacity: 1; filter: drop-shadow(0 0 8px var(--btc-orange-glow)); } + .page-header::before, + .page-header::after { + content: ""; + position: absolute; + width: 20px; + height: 20px; + border-color: var(--btc-orange); + border-style: solid; + opacity: 0.7; + filter: drop-shadow(0 0 4px var(--btc-orange-glow)); + transition: all 0.3s ease; + } + .page-header::before { + top: 10px; + left: 10px; + border-width: 2px 0 0 2px; + border-top-left-radius: 5px; + } + .page-header::after { + bottom: 10px; + right: 10px; + border-width: 0 2px 2px 0; + border-bottom-right-radius: 5px; + } + .page-header:hover::before, + .page-header:hover::after { + width: 25px; + height: 25px; + opacity: 1; + filter: drop-shadow(0 0 8px var(--btc-orange-glow)); + } - .page-header h1 { - color: var(--text-heading); font-weight: 300; letter-spacing: 1.5px; - margin-bottom: 0.7rem; font-size: 2.8rem; - text-shadow: 0 0 15px var(--btc-orange-glow), 0 0 5px var(--btc-orange-subtle-glow); - } - .page-header h1 .bi.bi-currency-bitcoin { - 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); - } - /* --- End Bitcoin Header Styling --- */ + .page-header h1 { + color: var(--text-heading); + font-weight: 300; + letter-spacing: 1.5px; + margin-bottom: 0.7rem; + font-size: 2.8rem; + text-shadow: 0 0 15px var(--btc-orange-glow), + 0 0 5px var(--btc-orange-subtle-glow); + } + .page-header h1 .bi.bi-currency-bitcoin { + 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); + } + /* --- End Bitcoin Header Styling --- */ - .schema-container { - padding: 0 1rem 0.5rem 1rem; margin-bottom: 3rem; position: relative; - } + .schema-container { + padding: 0 1rem 0.5rem 1rem; + margin-bottom: 3rem; + position: relative; + } - .section-title { - color: var(--category-color); margin: 0 0 2rem 0; font-weight: 500; - text-transform: uppercase; letter-spacing: 0.12em; font-size: 1rem; - border-bottom: 1px solid var(--border-color); - padding: 0.5rem 0; display: block; position: relative; z-index: 15; - text-shadow: 0 0 8px var(--category-color-glow); - } - /* Apply category colors vars */ - .cat-concept > .section-title { --category-color: var(--btc-color-concept); --category-color-glow: var(--btc-glow-concept);} - .cat-hot > .section-title { --category-color: var(--btc-color-hot); --category-color-glow: var(--btc-glow-hot);} - .cat-cold > .section-title { --category-color: var(--btc-color-cold); --category-color-glow: var(--btc-glow-cold);} - .cat-operations > .section-title { --category-color: var(--btc-color-operations); --category-color-glow: var(--btc-glow-operations);} - .cat-security > .section-title { --category-color: var(--btc-color-security); --category-color-glow: var(--btc-glow-security);} - .cat-advanced > .section-title { --category-color: var(--btc-color-advanced); --category-color-glow: var(--btc-glow-advanced);} - .cat-comparison > .section-title { --category-color: var(--btc-color-comparison); --category-color-glow: var(--btc-glow-comparison);} - .cat-pitfalls > .section-title { --category-color: var(--btc-color-pitfalls); --category-color-glow: var(--btc-glow-pitfalls);} - .cat-glossary > .section-title { --category-color: var(--btc-color-glossary); --category-color-glow: var(--btc-glow-glossary);} - .cat-resources > .section-title { --category-color: var(--btc-color-resources); --category-color-glow: var(--btc-glow-resources);} + .section-title { + color: var(--category-color); + margin: 0 0 2rem 0; + font-weight: 500; + text-transform: uppercase; + letter-spacing: 0.12em; + font-size: 1rem; + border-bottom: 1px solid var(--border-color); + padding: 0.5rem 0; + display: block; + position: relative; + z-index: 15; + text-shadow: 0 0 8px var(--category-color-glow); + } + /* Apply category colors vars */ + .cat-concept > .section-title { + --category-color: var(--btc-color-concept); + --category-color-glow: var(--btc-glow-concept); + } + .cat-hot > .section-title { + --category-color: var(--btc-color-hot); + --category-color-glow: var(--btc-glow-hot); + } + .cat-cold > .section-title { + --category-color: var(--btc-color-cold); + --category-color-glow: var(--btc-glow-cold); + } + .cat-operations > .section-title { + --category-color: var(--btc-color-operations); + --category-color-glow: var(--btc-glow-operations); + } + .cat-security > .section-title { + --category-color: var(--btc-color-security); + --category-color-glow: var(--btc-glow-security); + } + .cat-advanced > .section-title { + --category-color: var(--btc-color-advanced); + --category-color-glow: var(--btc-glow-advanced); + } + .cat-comparison > .section-title { + --category-color: var(--btc-color-comparison); + --category-color-glow: var(--btc-glow-comparison); + } + .cat-pitfalls > .section-title { + --category-color: var(--btc-color-pitfalls); + --category-color-glow: var(--btc-glow-pitfalls); + } + .cat-glossary > .section-title { + --category-color: var(--btc-color-glossary); + --category-color-glow: var(--btc-glow-glossary); + } + .cat-resources > .section-title { + --category-color: var(--btc-color-resources); + --category-color-glow: var(--btc-glow-resources); + } - /* --- Card Styling ("Nodes" v2) --- */ - .info-card { - background-color: var(--bg-card); border: 1px solid var(--border-color); - border-radius: 6px; box-shadow: 0 4px 12px rgba(0,0,0, 0.3), inset 0 0 8px rgba(0,0,0,0.2); - height: 100%; display: flex; flex-direction: column; - transition: all 0.3s ease; position: relative; z-index: 5; overflow: hidden; - --category-color: inherit; --category-color-glow: inherit; /* Prepare for hover */ - } + /* --- Card Styling ("Nodes" v2) --- */ + .info-card { + background-color: var(--bg-card); + border: 1px solid var(--border-color); + border-radius: 6px; + box-shadow: 0 4px 12px rgba(0, 0, 0, 0.3), + inset 0 0 8px rgba(0, 0, 0, 0.2); + height: 100%; + display: flex; + flex-direction: column; + transition: all 0.3s ease; + position: relative; + z-index: 5; + overflow: hidden; + --category-color: inherit; + --category-color-glow: inherit; /* Prepare for hover */ + } - /* 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);} - .info-card.btc-type-paper { --category-color: var(--btc-color-cold); --category-color-glow: var(--btc-glow-cold); filter: brightness(0.85); } - .info-card.btc-type-airgap { --category-color: var(--btc-color-cold); --category-color-glow: var(--btc-glow-cold);} - .info-card.btc-type-operation { --category-color: var(--btc-color-operations); --category-color-glow: var(--btc-glow-operations);} - .info-card.btc-type-security { --category-color: var(--btc-color-security); --category-color-glow: var(--btc-glow-security);} - .info-card.btc-type-advanced { --category-color: var(--btc-color-advanced); --category-color-glow: var(--btc-glow-advanced);} - .info-card.btc-type-comparison { --category-color: var(--btc-color-comparison); --category-color-glow: var(--btc-glow-comparison);} /* Applied */ - .info-card.btc-type-pitfall { --category-color: var(--btc-color-pitfalls); --category-color-glow: var(--btc-glow-pitfalls);} - .info-card.btc-type-glossary { --category-color: var(--btc-color-glossary); --category-color-glow: var(--btc-glow-glossary);} - .info-card.btc-type-resource { --category-color: var(--btc-color-resources); --category-color-glow: var(--btc-glow-resources);} + /* 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); + } + .info-card.btc-type-paper { + --category-color: var(--btc-color-cold); + --category-color-glow: var(--btc-glow-cold); + filter: brightness(0.85); + } + .info-card.btc-type-airgap { + --category-color: var(--btc-color-cold); + --category-color-glow: var(--btc-glow-cold); + } + .info-card.btc-type-operation { + --category-color: var(--btc-color-operations); + --category-color-glow: var(--btc-glow-operations); + } + .info-card.btc-type-security { + --category-color: var(--btc-color-security); + --category-color-glow: var(--btc-glow-security); + } + .info-card.btc-type-advanced { + --category-color: var(--btc-color-advanced); + --category-color-glow: var(--btc-glow-advanced); + } + .info-card.btc-type-comparison { + --category-color: var(--btc-color-comparison); + --category-color-glow: var(--btc-glow-comparison); + } /* Applied */ + .info-card.btc-type-pitfall { + --category-color: var(--btc-color-pitfalls); + --category-color-glow: var(--btc-glow-pitfalls); + } + .info-card.btc-type-glossary { + --category-color: var(--btc-color-glossary); + --category-color-glow: var(--btc-glow-glossary); + } + .info-card.btc-type-resource { + --category-color: var(--btc-color-resources); + --category-color-glow: var(--btc-glow-resources); + } - /* Circuit Board Corner Effect */ - .info-card::before { - content: ''; position: absolute; top: -1px; left: -1px; - width: 15px; height: 15px; border-top: 2px solid var(--category-color); - border-left: 2px solid var(--category-color); border-radius: 6px 0 0 0; - opacity: 0.6; transition: all 0.3s ease; - filter: drop-shadow(0 0 3px var(--category-color-glow)); - } - .info-card:hover::before { opacity: 1; width: 25px; height: 25px; filter: drop-shadow(0 0 6px var(--category-color-glow)); } + /* Circuit Board Corner Effect */ + .info-card::before { + content: ""; + position: absolute; + top: -1px; + left: -1px; + width: 15px; + height: 15px; + border-top: 2px solid var(--category-color); + border-left: 2px solid var(--category-color); + border-radius: 6px 0 0 0; + opacity: 0.6; + transition: all 0.3s ease; + filter: drop-shadow(0 0 3px var(--category-color-glow)); + } + .info-card:hover::before { + opacity: 1; + width: 25px; + height: 25px; + filter: drop-shadow(0 0 6px var(--category-color-glow)); + } - .info-card:hover { - transform: translateY(-4px) scale(1.01); z-index: 20; - animation: pulseGlowIntense 1.8s infinite ease-in-out; - } + .info-card:hover { + transform: translateY(-4px) scale(1.01); + z-index: 20; + animation: pulseGlowIntense 1.8s infinite ease-in-out; + } - .info-card .card-body { padding: 0; flex-grow: 1; display: flex; flex-direction: column; } - .info-card h5 { - color: var(--text-heading); - background: linear-gradient(135deg, var(--category-color) 0%, color-mix(in srgb, var(--category-color) 80%, black 20%) 100%); - font-size: 0.85rem; text-align: center; margin: 0; padding: 0.7rem 0.5rem; - font-weight: 600; display: flex; justify-content: center; align-items: center; - gap: .6rem; font-family: 'Orbitron', 'Fira Code', monospace; - border-bottom: 1px solid var(--border-color); border-radius: 5px 5px 0 0; - text-transform: uppercase; letter-spacing: 1px; text-shadow: 0 0 5px rgba(0,0,0,0.6); - } - .info-card h5 .bi { font-size: 1.2em; color: var(--text-heading); opacity: 1; filter: drop-shadow(0 0 3px rgba(0,0,0,0.6));} - .card-content-wrapper { padding: 1.1rem; flex-grow: 1; display: flex; flex-direction: column; } - .info-card p.summary { font-size: .88rem; color: var(--text-secondary); margin-bottom: 1rem; flex-grow: 1; line-height: 1.6;} + .info-card .card-body { + padding: 0; + flex-grow: 1; + display: flex; + flex-direction: column; + } + .info-card h5 { + color: var(--text-heading); + background: linear-gradient( + 135deg, + var(--category-color) 0%, + color-mix(in srgb, var(--category-color) 80%, black 20%) 100% + ); + font-size: 0.85rem; + text-align: center; + margin: 0; + padding: 0.7rem 0.5rem; + font-weight: 600; + display: flex; + justify-content: center; + align-items: center; + gap: 0.6rem; + font-family: "Orbitron", "Fira Code", monospace; + border-bottom: 1px solid var(--border-color); + border-radius: 5px 5px 0 0; + text-transform: uppercase; + letter-spacing: 1px; + text-shadow: 0 0 5px rgba(0, 0, 0, 0.6); + } + .info-card h5 .bi { + font-size: 1.2em; + color: var(--text-heading); + opacity: 1; + filter: drop-shadow(0 0 3px rgba(0, 0, 0, 0.6)); + } + .card-content-wrapper { + padding: 1.1rem; + flex-grow: 1; + display: flex; + flex-direction: column; + } + .info-card p.summary { + font-size: 0.88rem; + color: var(--text-secondary); + margin-bottom: 1rem; + flex-grow: 1; + line-height: 1.6; + } - /* Collapse Content Styling */ - .collapse-content { - font-size: 0.88rem; border-top: 1px dashed var(--border-color); - padding: 1.2rem; margin: 0; background-color: var(--bg-card-content); - border-radius: 0 0 5px 5px; color: var(--text-primary); - } - .collapse-content h6 { font-weight: 600; color: var(--accent-primary); margin: 1rem 0 0.5rem 0; font-size: 0.95rem; text-transform: uppercase; letter-spacing: 0.5px;} - .collapse-content ul { padding-left: 0; margin-bottom: 1rem; list-style-type: none; } - .collapse-content li { margin-bottom: 0.6rem; font-size: 0.88rem; line-height: 1.7; padding-left: 1.5em; position: relative; } - .collapse-content li::before { /* Neon bullet */ - content: ""; display: block; position: absolute; left: 0.2em; top: 0.5em; - width: 6px; height: 6px; background-color: var(--category-color); - border-radius: 50%; box-shadow: 0 0 5px 1px var(--category-color-glow); - } - /* Style list bullets based on card category */ - .info-card .collapse-content li::before { color: var(--category-color); box-shadow: 0 0 5px 1px var(--category-color-glow); background-color: var(--category-color); } + /* Collapse Content Styling */ + .collapse-content { + font-size: 0.88rem; + border-top: 1px dashed var(--border-color); + padding: 1.2rem; + margin: 0; + background-color: var(--bg-card-content); + border-radius: 0 0 5px 5px; + color: var(--text-primary); + } + .collapse-content h6 { + font-weight: 600; + color: var(--accent-primary); + margin: 1rem 0 0.5rem 0; + font-size: 0.95rem; + text-transform: uppercase; + letter-spacing: 0.5px; + } + .collapse-content ul { + padding-left: 0; + margin-bottom: 1rem; + list-style-type: none; + } + .collapse-content li { + margin-bottom: 0.6rem; + font-size: 0.88rem; + line-height: 1.7; + padding-left: 1.5em; + position: relative; + } + .collapse-content li::before { + /* Neon bullet */ + content: ""; + display: block; + position: absolute; + left: 0.2em; + top: 0.5em; + width: 6px; + height: 6px; + background-color: var(--category-color); + border-radius: 50%; + box-shadow: 0 0 5px 1px var(--category-color-glow); + } + /* Style list bullets based on card category */ + .info-card .collapse-content li::before { + color: var(--category-color); + box-shadow: 0 0 5px 1px var(--category-color-glow); + background-color: var(--category-color); + } - .collapse-content code { font-size: 0.8rem; color: #ffcc99; background-color: #30363d; padding: 0.2em 0.5em; border-radius: 4px; font-family: 'Fira Code', 'Courier New', monospace; border: 1px solid #444;} - .collapse-content pre code { display: block; padding: 1em; margin: 1em 0; background-color: #0d1117; border: 1px solid var(--border-color); border-radius: 4px; overflow-x: auto; } - .collapse-content dl dt { font-weight: bold; margin-top: 0.7em; color: var(--text-heading); } - .collapse-content dl dd { margin-left: 1.5em; margin-bottom: 0.5em; color: var(--text-secondary); } + .collapse-content code { + font-size: 0.8rem; + color: #ffcc99; + background-color: #30363d; + padding: 0.2em 0.5em; + border-radius: 4px; + font-family: "Fira Code", "Courier New", monospace; + border: 1px solid #444; + } + .collapse-content pre code { + display: block; + padding: 1em; + margin: 1em 0; + background-color: #0d1117; + border: 1px solid var(--border-color); + border-radius: 4px; + overflow-x: auto; + } + .collapse-content dl dt { + font-weight: bold; + margin-top: 0.7em; + color: var(--text-heading); + } + .collapse-content dl dd { + margin-left: 1.5em; + margin-bottom: 0.5em; + color: var(--text-secondary); + } - .row > * { margin-bottom: 2rem; } - footer { padding: 3rem 1rem 1rem 1rem; font-size: .8rem; color: var(--text-secondary); text-align: center; } + .row > * { + margin-bottom: 2rem; + } + footer { + padding: 3rem 1rem 1rem 1rem; + font-size: 0.8rem; + color: var(--text-secondary); + text-align: center; + } - /* Details Toggle Button */ - .details-toggle { - font-size: 0.7rem; margin-top: auto; align-self: flex-start; - padding: 0.4rem 0.8rem; color: var(--accent-primary); - border: 1px solid var(--accent-primary); background-color: transparent; - border-radius: 4px; transition: all 0.2s ease; - display: inline-flex; align-items: center; gap: 0.4em; - text-transform: uppercase; font-weight: 700; letter-spacing: 0.8px; - box-shadow: 0 0 5px 0px var(--accent-primary-glow); - } - .details-toggle:hover { background-color: var(--accent-primary); color: var(--bg-main); border-color: var(--accent-primary); transform: scale(1.05); box-shadow: 0 0 10px 2px var(--accent-primary-glow);} - .details-toggle .bi { transition: transform 0.2s ease-in-out; } - .details-toggle[aria-expanded="true"] .bi { transform: rotate(180deg); } + /* Details Toggle Button */ + .details-toggle { + font-size: 0.7rem; + margin-top: auto; + align-self: flex-start; + padding: 0.4rem 0.8rem; + color: var(--accent-primary); + border: 1px solid var(--accent-primary); + background-color: transparent; + border-radius: 4px; + transition: all 0.2s ease; + display: inline-flex; + align-items: center; + gap: 0.4em; + text-transform: uppercase; + font-weight: 700; + letter-spacing: 0.8px; + box-shadow: 0 0 5px 0px var(--accent-primary-glow); + } + .details-toggle:hover { + background-color: var(--accent-primary); + color: var(--bg-main); + border-color: var(--accent-primary); + transform: scale(1.05); + box-shadow: 0 0 10px 2px var(--accent-primary-glow); + } + .details-toggle .bi { + transition: transform 0.2s ease-in-out; + } + .details-toggle[aria-expanded="true"] .bi { + transform: rotate(180deg); + } - /* Terms & Links */ - .term { font-weight: 600; color: var(--accent-primary); background-color: transparent; border-bottom: 1px dotted var(--accent-primary); padding-bottom: 1px; border-radius: 0; font-family: 'Fira Code', 'Consolas', monospace; filter: drop-shadow(0 0 3px var(--accent-primary-glow)); } - .critical { color: var(--critical-color); font-weight: bold; text-shadow: 0 0 6px rgba(248, 81, 73, 0.6); } - .rule { - color: #ffc1bd; font-weight: 500; display: block; margin: 1em 0; - border: 1px solid var(--rule-border-color); border-left-width: 5px; - padding: 0.8em 1.2em; background-color: var(--rule-bg-color); - border-radius: 4px; font-size: 0.9rem; - box-shadow: inset 3px 0 8px rgba(0,0,0,0.2), 0 0 8px var(--rule-bg-color); - } - .pros::before { content: '[+] '; color: #56d364; font-weight: bold; filter: drop-shadow(0 0 3px var(--btc-glow-operations));} - .cons::before { content: '[-] '; color: #ff7b72; font-weight: bold; filter: drop-shadow(0 0 3px var(--btc-glow-hot));} - .pros, .cons { display: block; margin-left: 0; padding-left: 0;} + /* Terms & Links */ + .term { + font-weight: 600; + color: var(--accent-primary); + background-color: transparent; + border-bottom: 1px dotted var(--accent-primary); + padding-bottom: 1px; + border-radius: 0; + font-family: "Fira Code", "Consolas", monospace; + filter: drop-shadow(0 0 3px var(--accent-primary-glow)); + } + .critical { + color: var(--critical-color); + font-weight: bold; + text-shadow: 0 0 6px rgba(248, 81, 73, 0.6); + } + .rule { + color: #ffc1bd; + font-weight: 500; + display: block; + margin: 1em 0; + border: 1px solid var(--rule-border-color); + border-left-width: 5px; + padding: 0.8em 1.2em; + background-color: var(--rule-bg-color); + border-radius: 4px; + font-size: 0.9rem; + box-shadow: inset 3px 0 8px rgba(0, 0, 0, 0.2), + 0 0 8px var(--rule-bg-color); + } + .pros::before { + content: "[+] "; + color: #56d364; + font-weight: bold; + filter: drop-shadow(0 0 3px var(--btc-glow-operations)); + } + .cons::before { + content: "[-] "; + color: #ff7b72; + font-weight: bold; + filter: drop-shadow(0 0 3px var(--btc-glow-hot)); + } + .pros, + .cons { + display: block; + margin-left: 0; + padding-left: 0; + } - a { color: var(--accent-primary); text-decoration: none; transition: color 0.2s ease;} - a:hover { color: #9ecbff; text-decoration: underline; text-shadow: 0 0 5px var(--accent-primary-glow);} - .collapse-content a { color: #79c0ff; } - .collapse-content a:hover { color: #aedbff; } + a { + color: var(--accent-primary); + text-decoration: none; + transition: color 0.2s ease; + } + a:hover { + color: #9ecbff; + text-decoration: underline; + text-shadow: 0 0 5px var(--accent-primary-glow); + } + .collapse-content a { + color: #79c0ff; + } + .collapse-content a:hover { + color: #aedbff; + } - /* Animated Flow Line Between Rows */ - .row + .row::before { /* Add line *before* subsequent rows */ - content: ''; position: absolute; left: 10%; right: 10%; top: -1rem; - height: 1px; /* Thinner line */ - background: linear-gradient(90deg, transparent, var(--accent-primary-glow), var(--accent-primary), var(--accent-primary-glow), transparent); - background-size: 200% 1px; - opacity: 0.4; animation: flowLineGradient 6s linear infinite; - z-index: 1; border-radius: 1px; - } + /* Animated Flow Line Between Rows */ + .row + .row::before { + /* Add line *before* subsequent rows */ + content: ""; + position: absolute; + left: 10%; + right: 10%; + top: -1rem; + height: 1px; /* Thinner line */ + background: linear-gradient( + 90deg, + transparent, + var(--accent-primary-glow), + var(--accent-primary), + var(--accent-primary-glow), + transparent + ); + background-size: 200% 1px; + opacity: 0.4; + animation: flowLineGradient 6s linear infinite; + z-index: 1; + border-radius: 1px; + } </style> -</head> -<body> -<header class="page-header"> - <!-- Updated Title --> - <h1 class="display-5"> + </head> + <body> + <header class="page-header"> + <!-- Updated Title --> + <h1 class="display-5"> <i class="bi bi-currency-bitcoin"></i> Bitcoin Wallet Cheatsheet - </h1> - <!-- 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> + </h1> + <!-- 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 0: What is Bitcoin? (Renumbered) --> - <!-- ========================== --> - <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="container" id="main-container"> + <!-- ========================== --> + <!-- SECTION 0: What is Bitcoin? (Renumbered) --> + <!-- ========================== --> + <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-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-info-circle-fill"></i> Bitcoin :: The Basics</h5> - <div class="card-content-wrapper"> - <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="collapseWhatIsBtc"> - <h6>Key Characteristics:</h6> - <ul> - <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> - <!-- Added Whitepaper Link --> - <li><strong>Original Vision:</strong> <a href="https://bitcoin.org/bitcoin.pdf" target="_blank" rel="noopener noreferrer"><i class="bi bi-file-earmark-text-fill"></i> Bitcoin Whitepaper</a></li> - </ul> - </div> - </div> + <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-info-circle-fill"></i> Bitcoin :: The Basics + </h5> + <div class="card-content-wrapper"> + <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="collapseWhatIsBtc"> + <h6>Key Characteristics:</h6> + <ul> + <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> + <!-- Added Whitepaper Link --> + <li> + <strong>Original Vision:</strong> + <a + href="https://bitcoin.org/bitcoin.pdf" + target="_blank" + rel="noopener noreferrer" + ><i class="bi bi-file-earmark-text-fill"></i> Bitcoin + Whitepaper</a + > + </li> + </ul> + </div> </div> - </div> <!-- /.row --> - </div> <!-- /.schema-container --> + </div> + </div> + <!-- /.row --> + </div> + <!-- /.schema-container --> - <!-- ========================== --> - <!-- SECTION I: Introduction (Renumbered) --> - <!-- ========================== --> - <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> + <!-- ========================== --> + <!-- SECTION I: Introduction (Renumbered) --> + <!-- ========================== --> + <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-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> 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 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> 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 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">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 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"> + 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> <!-- /.row --> - </div> <!-- /.schema-container --> + </div> + </div> + <!-- /.row --> + </div> + <!-- /.schema-container --> - <!-- ================================================== --> - <!-- SECTION II: Protecting Your Bitcoin (Renumbered) --> - <!-- ================================================== --> - <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> + <!-- ================================================== --> + <!-- SECTION II: Protecting Your Bitcoin (Renumbered) --> + <!-- ================================================== --> + <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 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 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> - <!-- Updated links to point to correct section VIII cards --> - <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 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> <!-- /.row --> - </div> <!-- /.schema-container --> - + </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> + <!-- Updated links to point to correct section VIII cards --> + <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 --> - <!-- ================================= --> - <!-- SECTION III: Wallet Fundamentals (Renumbered) --> - <!-- ================================= --> - <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> + <!-- ================================= --> + <!-- SECTION III: Wallet Fundamentals (Renumbered) --> + <!-- ================================= --> + <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> Private & Public Keys</h5> - <div class="card-content-wrapper"> - <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> + <!-- 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> Private & Public Keys</h5> + <div class="card-content-wrapper"> + <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> - <!-- 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> Bitcoin Addresses</h5> - <div class="card-content-wrapper"> - <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"> - Address Formats <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseAddresses"> - <h6>Common Address Formats (Look at the starting characters):</h6> - <ul> - <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">Privacy Tip: Generate and use a fresh address for every payment you receive.</strong> Most wallets do this automatically.</p> - </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> Bitcoin Addresses</h5> + <div class="card-content-wrapper"> + <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" + > + Address Formats <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseAddresses"> + <h6> + Common Address Formats (Look at the starting characters): + </h6> + <ul> + <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" + >Privacy Tip: Generate and use a fresh address for every + payment you receive.</strong + > + Most wallets do this automatically. + </p> + </div> </div> - <!-- Seed Phrase --> - <div class="col-lg-4 col-md-12"> - <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 :: Master Backup</h5> - <div class="card-content-wrapper"> - <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"> - Critical Details <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseSeed"> - <h6>Understanding Your Seed Phrase (BIP-39):</h6> - <ul> - <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> - <!-- Updated link to point to correct section VI --> - <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> + <!-- Seed Phrase --> + <div class="col-lg-4 col-md-12"> + <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 :: Master + Backup + </h5> + <div class="card-content-wrapper"> + <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" + > + Critical Details <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseSeed"> + <h6>Understanding Your Seed Phrase (BIP-39):</h6> + <ul> + <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> + <!-- Updated link to point to correct section VI --> + <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> - <!-- Transactions --> - <div class="col-lg-6 col-md-6"> <!-- Adjusted column width for better balance --> - <div class="info-card btc-type-concept" id="card-transactions"> - <div class="card-body"> - <h5><i class="bi bi-arrows-fullscreen"></i> How Transactions Work</h5> - <div class="card-content-wrapper"> - <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"> - Transaction Lifecycle <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseTx"> - <h6>Transaction Flow:</h6> - <ul> - <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> + </div> + <!-- Transactions --> + <div class="col-lg-6 col-md-6"> + <!-- Adjusted column width for better balance --> + <div class="info-card btc-type-concept" id="card-transactions"> + <div class="card-body"> + <h5> + <i class="bi bi-arrows-fullscreen"></i> How Transactions Work + </h5> + <div class="card-content-wrapper"> + <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" + > + Transaction Lifecycle <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseTx"> + <h6>Transaction Flow:</h6> + <ul> + <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> - <div class="col-lg-6 col-md-6"> <!-- Adjusted column width for better balance --> - <div class="info-card btc-type-concept" id="card-fee-estimation"> - <div class="card-body"> - <h5><i class="bi bi-speedometer2"></i> Transaction Fees</h5> - <div class="card-content-wrapper"> - <p class="summary">Fees (<span class="term">sat/vB</span>) pay miners to include your transaction. They fluctuate based on network demand. Wallets suggest fees, but manual adjustment is possible for urgency vs. cost savings.</p> - <button class="btn btn-sm details-toggle" type="button" data-bs-toggle="collapse" data-bs-target="#collapseFees" aria-expanded="false" aria-controls="collapseFees"> - Fee Strategy <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseFees"> - <h6>Understanding Fees:</h6> - <ul> - <li><strong>Unit:</strong> <span class="term">Satoshis per virtual Byte</span> (sat/vB). Higher sat/vB = higher priority for miners.</li> - <li><strong>Estimation:</strong> Check sites like <a href="https://mempool.space/" target="_blank" rel="noopener noreferrer">mempool.space</a> for current rates for low, medium, high priority.</li> - <li><strong>Wallet Defaults:</strong> Most wallets estimate fees, but you can often override them.</li> - <li><strong>Too Low?</strong> Transaction may get stuck (see <a href="#card-adv-fee-bump">Fee Bumping, Section VII</a>).</li> - <li><strong>Too High?</strong> Wasted funds.</li> - </ul> - </div> - </div> + </div> + <div class="col-lg-6 col-md-6"> + <!-- Adjusted column width for better balance --> + <div class="info-card btc-type-concept" id="card-fee-estimation"> + <div class="card-body"> + <h5><i class="bi bi-speedometer2"></i> Transaction Fees</h5> + <div class="card-content-wrapper"> + <p class="summary"> + Fees (<span class="term">sat/vB</span>) pay miners to + include your transaction. They fluctuate based on network + demand. Wallets suggest fees, but manual adjustment is + possible for urgency vs. cost savings. + </p> + <button + class="btn btn-sm details-toggle" + type="button" + data-bs-toggle="collapse" + data-bs-target="#collapseFees" + aria-expanded="false" + aria-controls="collapseFees" + > + Fee Strategy <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseFees"> + <h6>Understanding Fees:</h6> + <ul> + <li> + <strong>Unit:</strong> + <span class="term">Satoshis per virtual Byte</span> + (sat/vB). Higher sat/vB = higher priority for miners. + </li> + <li> + <strong>Estimation:</strong> Check sites like + <a + href="https://mempool.space/" + target="_blank" + rel="noopener noreferrer" + >mempool.space</a + > + for current rates for low, medium, high priority. + </li> + <li> + <strong>Wallet Defaults:</strong> Most wallets estimate + fees, but you can often override them. + </li> + <li> + <strong>Too Low?</strong> Transaction may get stuck (see + <a href="#card-adv-fee-bump">Fee Bumping, Section VII</a>). + </li> + <li><strong>Too High?</strong> Wasted funds.</li> + </ul> + </div> </div> - </div> <!-- /.row --> - </div> <!-- /.schema-container --> + </div> + </div> + <!-- /.row --> + </div> + <!-- /.schema-container --> - <!-- ================================ --> - <!-- SECTION IV: Types of Wallets (Renumbered) --> - <!-- ================================ --> - <div class="schema-container" data-section-id="section-types"> + <!-- ================================ --> + <!-- SECTION IV: Types of Wallets (Renumbered) --> + <!-- ================================ --> + <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> // IV.A Hot Wallets :: ONLINE / CONNECTED</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 Wallets (Desktop/Mobile)</h5> - <div class="card-content-wrapper"> - <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"> - Types & Risks <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseSoftware"> - <h6>Custody Type Matters:</h6> - <ul> - <li><strong class="pros">Non-Custodial:</strong> YOU control the keys/seed phrase. Examples: <a href="#card-compare-app-electrum">Electrum</a>, <a href="#card-compare-app-sparrow">Sparrow</a> (Desktop); <a href="#card-compare-app-bluewallet">BlueWallet</a>, <a href="#card-compare-app-muun">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>Threats to Hot Wallets:</h6> - <ul> - <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> - <!-- ADDED WARNING --> - <li><strong class="critical">Rule of Thumb: Only keep small, spendable amounts in hot wallets. Use hardware wallets for long-term savings / significant holdings.</strong></li> - </ul> - </div> - </div> + <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 Wallets + (Desktop/Mobile) + </h5> + <div class="card-content-wrapper"> + <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" + > + Types & Risks <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseSoftware"> + <h6>Custody Type Matters:</h6> + <ul> + <li> + <strong class="pros">Non-Custodial:</strong> YOU control the + keys/seed phrase. Examples: + <a href="#card-compare-app-electrum">Electrum</a>, + <a href="#card-compare-app-sparrow">Sparrow</a> (Desktop); + <a href="#card-compare-app-bluewallet">BlueWallet</a>, + <a href="#card-compare-app-muun">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>Threats to Hot Wallets:</h6> + <ul> + <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> + <!-- ADDED WARNING --> + <li> + <strong class="critical" + >Rule of Thumb: Only keep small, spendable amounts in hot + wallets. Use hardware wallets for long-term savings / + significant holdings.</strong + > + </li> + </ul> + </div> </div> - <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 Wallets</h5> - <div class="card-content-wrapper"> - <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> + </div> + <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 Wallets</h5> + <div class="card-content-wrapper"> + <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> - </div> <!-- /.row --> + </div> + </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> // IV.B Cold Wallets :: 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-detail"> - <div class="card-body"> - <h5><i class="bi bi-memory"></i> Hardware Wallets (Recap)</h5> - <div class="card-content-wrapper"> - <!-- Updated link to point to correct section II --> - <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="collapseHardwareDetail"> - <h6>Key Advantages:</h6> - <ul> - <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>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> - <!-- Updated links to point to correct section VIII cards --> - <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> + <div class="col-lg-4 col-md-6"> + <div class="info-card btc-type-hardware" id="card-hardware-detail"> + <div class="card-body"> + <h5><i class="bi bi-memory"></i> Hardware Wallets (Recap)</h5> + <div class="card-content-wrapper"> + <!-- Updated link to point to correct section II --> + <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="collapseHardwareDetail" + > + <h6>Key Advantages:</h6> + <ul> + <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>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> + <!-- Updated links to point to correct section VIII cards --> + <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> - <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 Wallets</h5> - <div class="card-content-wrapper"> - <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"> - Why Avoid Them? <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapsePaper"> - <h6>Major Drawbacks:</h6> - <ul> - <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><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-paper" id="card-paper"> + <div class="card-body"> + <h5><i class="bi bi-journal"></i> Paper Wallets</h5> + <div class="card-content-wrapper"> + <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" + > + Why Avoid Them? <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapsePaper"> + <h6>Major Drawbacks:</h6> + <ul> + <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> + <strong class="critical" + >Recommendation: Use a hardware wallet instead for much + better security and usability.</strong + > + </p> + </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 Setups</h5> - <div class="card-content-wrapper"> - <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"> - Process & Tradeoffs <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseAirgap"> - <h6>How it Works (Simplified):</h6> - <ol> - <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>Pros & Cons:</h6> - <ul> - <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> - <!-- Updated links to point to correct section VIII cards --> - <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> + <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 Setups</h5> + <div class="card-content-wrapper"> + <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" + > + Process & Tradeoffs <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseAirgap"> + <h6>How it Works (Simplified):</h6> + <ol> + <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>Pros & Cons:</h6> + <ul> + <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> + <!-- Updated links to point to correct section VIII cards --> + <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> <!-- /.row --> - </div> <!-- /.schema-container --> + </div> + </div> + <!-- /.row --> + </div> + <!-- /.schema-container --> - - <!-- ============================== --> - <!-- SECTION V: Core Operations (Renumbered) --> - <!-- ============================== --> - <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> // V. Core Wallet Operations</h2> + <!-- ============================== --> + <!-- SECTION V: Core Operations (Renumbered) --> + <!-- ============================== --> + <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> // 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> Wallet Setup & Backup</h5> - <div class="card-content-wrapper"> - <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"> - Setup Checklist <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseOpSetup"> - <h6>Initialization Checklist:</h6> - <ol> - <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> - <!-- Updated link to point to correct section VI --> - <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> - <!-- Updated link to point to correct section VII --> - <li><strong>(Advanced) Passphrase:</strong> Consider adding a BIP-39 Passphrase later for extra security (see Section VII).</li> - </ol> - </div> - </div> + <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> Wallet Setup & Backup + </h5> + <div class="card-content-wrapper"> + <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" + > + Setup Checklist <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseOpSetup"> + <h6>Initialization Checklist:</h6> + <ol> + <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> + <!-- Updated link to point to correct section VI --> + <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> + <!-- Updated link to point to correct section VII --> + <li> + <strong>(Advanced) Passphrase:</strong> Consider adding a + BIP-39 Passphrase later for extra security (see Section + VII). + </li> + </ol> + </div> </div> - <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> Receiving Bitcoin</h5> - <div class="card-content-wrapper"> - <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> - </div> + </div> + <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> Receiving Bitcoin</h5> + <div class="card-content-wrapper"> + <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> </div> - <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> Sending Bitcoin</h5> - <div class="card-content-wrapper"> - <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"> - Sending Checklist <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseOpSend"> - <h6>Sending Checklist:</h6> - <ol> - <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> + </div> + <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> Sending Bitcoin</h5> + <div class="card-content-wrapper"> + <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" + > + Sending Checklist <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseOpSend"> + <h6>Sending Checklist:</h6> + <ol> + <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> - <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> Checking Balance & History</h5> - <div class="card-content-wrapper"> - <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> - </div> + </div> + <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> Checking Balance & History</h5> + <div class="card-content-wrapper"> + <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> </div> - </div> <!-- /.row --> - </div> <!-- /.schema-container --> + </div> + </div> + <!-- /.row --> + </div> + <!-- /.schema-container --> - - <!-- ================================== --> - <!-- SECTION VI: Security Best Practices (Renumbered) --> - <!-- ================================== --> - <div class="schema-container cat-security" data-section-id="section-security"> - <h2 class="section-title" id="section-security"><i class="bi bi-fingerprint"></i> // VI. Security Best Practices (OPSEC)</h2> + <!-- ================================== --> + <!-- SECTION VI: Security Best Practices (Renumbered) --> + <!-- ================================== --> + <div + class="schema-container cat-security" + data-section-id="section-security" + > + <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 Security :: Rule #1</h5> - <div class="card-content-wrapper"> - <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"> - Unbreakable Rules <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseSecSeed"> - <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 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> - <!-- Updated link to point to correct section VII --> - <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> + <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 Security :: + Rule #1 + </h5> + <div class="card-content-wrapper"> + <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" + > + Unbreakable Rules <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseSecSeed"> + <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 + 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> + <!-- Updated link to point to correct section VII --> + <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> - <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 Wallet Security</h5> - <div class="card-content-wrapper"> - <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"> - Device Procedures <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseSecDevice"> - <h6>Hardware Wallet Best Practices:</h6> - <ul> - <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> - <!-- Updated link to point to correct section VII --> - <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> + <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 Wallet Security</h5> + <div class="card-content-wrapper"> + <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" + > + Device Procedures <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseSecDevice"> + <h6>Hardware Wallet Best Practices:</h6> + <ul> + <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> + <!-- Updated link to point to correct section VII --> + <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 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> Computer & Network Security</h5> - <div class="card-content-wrapper"> - <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"> - Digital Hygiene <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseSecSw"> - <h6>Protecting Your Digital Environment:</h6> - <ul> - <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> + </div> + <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> Computer & Network + Security + </h5> + <div class="card-content-wrapper"> + <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" + > + Digital Hygiene <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseSecSw"> + <h6>Protecting Your Digital Environment:</h6> + <ul> + <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> - <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 & Inheritance</h5> - <div class="card-content-wrapper"> - <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 Plans <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseSecBackup"> - <h6>Planning for the Unexpected:</h6> - <ul> - <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> - <!-- Updated link to point to correct section VII --> - <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>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> + </div> + <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 & Inheritance + </h5> + <div class="card-content-wrapper"> + <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 Plans <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseSecBackup"> + <h6>Planning for the Unexpected:</h6> + <ul> + <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> + <!-- Updated link to point to correct section VII --> + <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>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> + </div> + </div> + <!-- /.row --> + </div> + <!-- /.schema-container --> - </div> <!-- /.row --> - </div> <!-- /.schema-container --> - - - <!-- ==================================== --> - <!-- SECTION VII: Advanced Features & Techniques (Renumbered) --> - <!-- ==================================== --> - <div class="schema-container cat-advanced" data-section-id="section-advanced"> - <h2 class="section-title" id="section-advanced"><i class="bi bi-motherboard"></i> // VII. Advanced Features & Techniques</h2> + <!-- ==================================== --> + <!-- SECTION VII: Advanced Features & Techniques (Renumbered) --> + <!-- ==================================== --> + <div + class="schema-container cat-advanced" + data-section-id="section-advanced" + > + <h2 class="section-title" id="section-advanced"> + <i class="bi bi-motherboard"></i> // VII. Advanced Features & + Techniques + </h2> <div class="row"> - <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 ("Hidden Wallet")</h5> - <div class="card-content-wrapper"> - <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"> - Use Cases & Risks <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseAdvPassphrase"> - <h6>How it Works:</h6> - <ul> - <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">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> + <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 ("Hidden Wallet") + </h5> + <div class="card-content-wrapper"> + <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" + > + Use Cases & Risks <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseAdvPassphrase"> + <h6>How it Works:</h6> + <ul> + <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" + >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> - <div class="col-lg-4 col-md-6"> - <div class="info-card btc-type-advanced" id="card-adv-multisig"> - <div class="card-body"> - <h5><i class="bi bi-diagram-3-fill"></i> Multisignature (Multisig)</h5> - <div class="card-content-wrapper"> - <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"> - Benefits & Setup <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseAdvMultisig"> - <h6>Why Use Multisig?</h6> - <ul> - <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> - <!-- Updated links to point to correct section IX cards --> - <li>Requires specialized software (like <a href="#card-compare-app-sparrow">Sparrow Wallet</a>, <a href="https://specter.solutions/" target="_blank" rel="noopener noreferrer">Specter Desktop</a>, <a href="#card-compare-app-nunchuk">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> - </div> - </div> + </div> + <div class="col-lg-4 col-md-6"> + <div class="info-card btc-type-advanced" id="card-adv-multisig"> + <div class="card-body"> + <h5> + <i class="bi bi-diagram-3-fill"></i> Multisignature (Multisig) + </h5> + <div class="card-content-wrapper"> + <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" + > + Benefits & Setup <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseAdvMultisig"> + <h6>Why Use Multisig?</h6> + <ul> + <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> + <!-- Updated links to point to correct section IX cards --> + <li> + Requires specialized software (like + <a href="#card-compare-app-sparrow">Sparrow Wallet</a>, + <a + href="https://specter.solutions/" + target="_blank" + rel="noopener noreferrer" + >Specter Desktop</a + >, <a href="#card-compare-app-nunchuk">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> + </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> Using Your Own Full Node</h5> - <div class="card-content-wrapper"> - <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"> - Why Run a Node? <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseAdvNode"> - <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>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> - </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> Using Your Own Full + Node + </h5> + <div class="card-content-wrapper"> + <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" + > + Why Run a Node? <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseAdvNode"> + <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> + 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> + </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 Management)</h5> - <div class="card-content-wrapper"> - <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"> - 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 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> - <!-- Updated links to point to correct section IX cards --> - <p>Requires wallet software that supports this feature (e.g., <a href="#card-compare-app-electrum">Electrum</a>, <a href="#card-compare-app-sparrow">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-coincontrol"> + <div class="card-body"> + <h5> + <i class="bi bi-vinyl-fill"></i> Coin Control (UTXO + Management) + </h5> + <div class="card-content-wrapper"> + <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" + > + 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 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> + <!-- Updated links to point to correct section IX cards --> + <p> + Requires wallet software that supports this feature (e.g., + <a href="#card-compare-app-electrum">Electrum</a>, + <a href="#card-compare-app-sparrow">Sparrow</a>, + <a + href="https://specter.solutions/" + target="_blank" + rel="noopener noreferrer" + >Specter</a + >). + </p> + </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> PSBT (Partially Signed Bitcoin Tx)</h5> - <div class="card-content-wrapper"> - <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"> - How It's Used <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseAdvPsbt"> - <h6>Common Workflows:</h6> - <ul> - <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-psbt"> + <div class="card-body"> + <h5> + <i class="bi bi-file-binary-fill"></i> PSBT (Partially Signed + Bitcoin Tx) + </h5> + <div class="card-content-wrapper"> + <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" + > + How It's Used <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseAdvPsbt"> + <h6>Common Workflows:</h6> + <ul> + <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 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> - <div class="card-content-wrapper"> - <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-fee-bump"> + <div class="card-body"> + <h5> + <i class="bi bi-graph-up-arrow"></i> Fee Bumping (RBF / CPFP) + </h5> + <div class="card-content-wrapper"> + <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 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 Splitting)</h5> - <div class="card-content-wrapper"> - <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"> - Pros & Cons <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseAdvShamir"> - <h6>How it Helps:</h6> - <ul> - <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> + </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 Splitting) + </h5> + <div class="card-content-wrapper"> + <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" + > + Pros & Cons <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseAdvShamir"> + <h6>How it Helps:</h6> + <ul> + <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> - <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 (Practice Network)</h5> - <div class="card-content-wrapper"> - <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> + </div> + <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 (Practice Network) + </h5> + <div class="card-content-wrapper"> + <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> - </div> <!-- /.row --> - </div> <!-- /.schema-container --> - + </div> + </div> + <!-- /.row --> + </div> + <!-- /.schema-container --> - <!-- ========================================= --> - <!-- SECTION VIII: Hardware Wallet Comparison (Renumbered) --> - <!-- ========================================= --> - <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> // VIII. Hardware Wallet Comparison</h2> + <!-- ========================================= --> + <!-- SECTION VIII: Hardware Wallet Comparison (Renumbered) --> + <!-- ========================================= --> + <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> // 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> How to Choose a Hardware Wallet</h5> - <div class="card-content-wrapper"> - <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"> - Factors Explained <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseCompareFactors"> - <h6>Key Comparison Factors:</h6> - <ul> - <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> - <!-- Updated link to point to correct card --> - <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 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> How to Choose a Hardware Wallet + </h5> + <div class="card-content-wrapper"> + <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" + > + Factors Explained <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div + class="collapse collapse-content" + id="collapseCompareFactors" + > + <h6>Key Comparison Factors:</h6> + <ul> + <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> + <!-- Updated link to point to correct card --> + <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 --> - <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 (Safe 5 / Safe 3 / Model T)</h5> - <div class="card-content-wrapper"> - <p class="summary"> - <span class="pros">[+] Long history, Open Source FW (device), User-friendly Suite, Passphrase (All). Safe 5: Large Color Touchscreen, Haptic feedback, Shamir/Enhanced Backup. Safe 3/5: Secure Element Option. Model T: Shamir Backup.</span> - <span class="cons">[-] Safe 3/5 SE firmware is closed source. Model T uses MCU (less physical tamper resistance vs SE). No native air-gap mode (USB required). Safe 5 is higher priced.</span> - </p> - <p><a href="https://trezor.io/" target="_blank" rel="noopener noreferrer">trezor.io</a></p> - </div> - </div> - </div> - </div> - - <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> - <div class="card-content-wrapper"> - <p class="summary"> - <span class="pros">[+] Bitcoin-Only (reduced attack surface), Strong security reputation, True Air-Gap (SD card, NFC, USB-PSBT), Excellent PSBT/Multisig support, Open Source Firmware, Dual Secure Elements (Mk4/Q1), Physical security (PIN, Duress PIN, Brick Me PIN). Q1 adds QWERTY keyboard, larger screen.</span> - <span class="cons">[-] Steeper learning curve than others, Requires coordinator software (e.g., Sparrow, Specter), Basic UI (functional, not fancy), Q1 is larger and more expensive.</span> - </p> - <p><a href="https://coldcard.com/" target="_blank" rel="noopener noreferrer">coldcard.com</a></p> - </div> - </div> - </div> - </div> + <!-- Specific Wallet Cards --> + <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 (Safe 5 / Safe 3 / + Model T) + </h5> + <div class="card-content-wrapper"> + <p class="summary"> + <span class="pros" + >[+] Long history, Open Source FW (device), User-friendly + Suite, Passphrase (All). Safe 5: Large Color Touchscreen, + Haptic feedback, Shamir/Enhanced Backup. Safe 3/5: Secure + Element Option. Model T: Shamir Backup.</span + > + <span class="cons" + >[-] Safe 3/5 SE firmware is closed source. Model T uses + MCU (less physical tamper resistance vs SE). No native + air-gap mode (USB required). Safe 5 is higher + priced.</span + > + </p> + <p> + <a + href="https://trezor.io/" + target="_blank" + rel="noopener noreferrer" + >trezor.io</a + > + </p> + </div> + </div> + </div> + </div> + + <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> + <div class="card-content-wrapper"> + <p class="summary"> + <span class="pros" + >[+] Bitcoin-Only (reduced attack surface), Strong + security reputation, True Air-Gap (SD card, NFC, + USB-PSBT), Excellent PSBT/Multisig support, Open Source + Firmware, Dual Secure Elements (Mk4/Q1), Physical security + (PIN, Duress PIN, Brick Me PIN). Q1 adds QWERTY keyboard, + larger screen.</span + > + <span class="cons" + >[-] Steeper learning curve than others, Requires + coordinator software (e.g., Sparrow, Specter), Basic UI + (functional, not fancy), Q1 is larger and more + expensive.</span + > + </p> + <p> + <a + href="https://coldcard.com/" + target="_blank" + rel="noopener noreferrer" + >coldcard.com</a + > + </p> + </div> + </div> + </div> + </div> - <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 S+ / Nano X / Stax)</h5> - <div class="card-content-wrapper"> - <p class="summary"> - <span class="pros">[+] Uses Secure Element (SE) chip, Wide Coin Support, Popular/Well-known brand, Polished Ledger Live companion app (Desktop/Mobile), Bluetooth (Nano X).</span> - <span class="cons">[-] Closed Source device firmware & SE firmware, Requires trust in vendor. Controversial 'Ledger Recover' service (opt-in seed fragment backup). Past *customer data* breach (not keys). Heavy reliance on Ledger Live app. Multi-coin support increases code complexity/attack surface vs Bitcoin-only. Stax significantly delayed.</span> - </p> - <p><a href="https://www.ledger.com/" target="_blank" rel="noopener noreferrer">ledger.com</a></p> - </div> - </div> - </div> - </div> + <div class="col-lg-4 col-md-6"> + <div + class="info-card btc-type-comparison comparison-item" + id="card-compare-bitkey" + > + <div class="card-body"> + <h5><i class="bi bi-key-fill"></i> Bitkey</h5> + <div class="card-content-wrapper"> + <p class="summary"> + <span class="pros" + >[+] Beginner-friendly setup, No user-managed seed phrase + (removes major user error point), Simple hardware + (fingerprint), Recovery assistance via 2-of-3 multisig + (Mobile Key, Hardware Key, Server Key), Integration with + partners (e.g., Cash App, Coinbase).</span + > + <span class="cons" + >[-] **Not traditional self-custody:** Relies on a 2-of-3 + multisig where Block/Bitkey holds one server key, + introducing counterparty risk (server availability, policy + enforcement/limits, potential censorship). Mobile key is + hot. Hardware key doesn't operate standalone like + traditional HWs. Requires server interaction for + signing/recovery. Closed-source components + (especially server-side). Different trust model than fully + user-controlled wallets.</span + > + </p> + <p> + <a + href="https://bitkey.world/" + target="_blank" + rel="noopener noreferrer" + >bitkey.world</a + > + </p> + </div> + </div> + </div> + </div> - <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 (Bitcoin-Only Ed.)</h5> - <div class="card-content-wrapper"> - <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> - </div> - </div> - <div class="col-lg-4 col-md-6"> - <div class="info-card btc-type-comparison comparison-item" id="card-compare-seedsigner"> - <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">[+] 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> - </div> - </div> - <div class="col-lg-4 col-md-6"> - <div class="info-card btc-type-comparison comparison-item" id="card-compare-jade"> - <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, 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> - </div> - </div> - <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 (Batch 2)</h5> - <div class="card-content-wrapper"> - <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"> <!-- Spacer/Choice 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> Making Your Choice</h5> - <div class="card-content-wrapper"> - <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> - </div> - </div> <!-- /.row --> - </div> <!-- /.schema-container --> + <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 S+ / Nano X / + Stax) + </h5> + <div class="card-content-wrapper"> + <p class="summary"> + <span class="pros" + >[+] Uses Secure Element (SE) chip, Wide Coin Support, + Popular/Well-known brand, Polished Ledger Live companion + app (Desktop/Mobile), Bluetooth (Nano X).</span + > + <span class="cons" + >[-] Closed Source device firmware & SE firmware, Requires + trust in vendor. Controversial 'Ledger Recover' service + (opt-in seed fragment backup). Past *customer data* breach + (not keys). Heavy reliance on Ledger Live app. Multi-coin + support increases code complexity/attack surface vs + Bitcoin-only. Stax significantly delayed.</span + > + </p> + <p> + <a + href="https://www.ledger.com/" + target="_blank" + rel="noopener noreferrer" + >ledger.com</a + > + </p> + </div> + </div> + </div> + </div> + <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 (Bitcoin-Only Ed.) + </h5> + <div class="card-content-wrapper"> + <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> + </div> + </div> + <div class="col-lg-4 col-md-6"> + <div + class="info-card btc-type-comparison comparison-item" + id="card-compare-seedsigner" + > + <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" + >[+] 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> + </div> + </div> + <div class="col-lg-4 col-md-6"> + <div + class="info-card btc-type-comparison comparison-item" + id="card-compare-jade" + > + <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, 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> + </div> + </div> + <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 (Batch + 2) + </h5> + <div class="card-content-wrapper"> + <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"> + <!-- Spacer/Choice 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> Making Your Choice + </h5> + <div class="card-content-wrapper"> + <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> + </div> + </div> + <!-- /.row --> + </div> + <!-- /.schema-container --> - <!-- ========================================= --> - <!-- SECTION IX: App Wallet Comparison (Renumbered & Styled) --> - <!-- ========================================= --> - <div class="schema-container cat-comparison" data-section-id="section-app-comparison"> + <!-- ========================================= --> + <!-- SECTION IX: App Wallet Comparison (Renumbered & Styled) --> + <!-- ========================================= --> + <div + class="schema-container cat-comparison" + data-section-id="section-app-comparison" + > <!-- Note: This becomes Section IX --> - <h2 class="section-title" id="section-app-comparison"><i class="bi bi-grid-1x2-fill"></i> // IX. App Wallet Comparison (Software/Mobile)</h2> + <h2 class="section-title" id="section-app-comparison"> + <i class="bi bi-grid-1x2-fill"></i> // IX. App Wallet Comparison + (Software/Mobile) + </h2> <div class="row"> - <div class="col-12"> - <div class="info-card btc-type-comparison" id="card-app-compare-factors"> - <div class="card-body"> - <h5 class="text-center"><i class="bi bi-sliders"></i> How to Choose an App Wallet</h5> - <div class="card-content-wrapper"> - <!-- ADDED WARNING --> - <p class="summary text-center">Consider: Platform (Desktop/Mobile), Ease of Use, Features (Lightning, Coin Control, Node Connect, HW Support), Security Model, Open Source Status, Vendor Reputation. <strong class="critical">App wallets carry inherent online risks; hardware wallets are advised for substantial amounts. Focus on Non-Custodial options where YOU control the keys/seed.</strong></p> - <button class="btn btn-sm details-toggle mx-auto" type="button" data-bs-toggle="collapse" data-bs-target="#collapseAppCompareFactors" aria-expanded="false" aria-controls="collapseAppCompareFactors"> - Factors Explained <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseAppCompareFactors"> - <h6>Key Comparison Factors for App Wallets:</h6> - <ul> - <li><strong>Platform:</strong> Is it available for your device (iOS, Android, Windows, macOS, Linux)?</li> - <li><strong>User Experience (UX):</strong> Is it intuitive for beginners or geared towards advanced users?</li> - <li><strong>Key Features:</strong> - <ul> - <li><span class="term">Lightning Network:</span> Does it support faster, cheaper Layer 2 payments?</li> - <li><span class="term">Coin Control:</span> Can you manually select UTXOs for privacy/fee management?</li> - <li><span class="term">Full Node Connection:</span> Can it connect to your own Bitcoin node for maximum privacy?</li> - <li><span class="term">Hardware Wallet Integration:</span> Can it act as an interface for your hardware wallet?</li> - <li><span class="term">Multisig Support:</span> Does it facilitate setting up or signing multisignature transactions?</li> - </ul> - </li> - <li><strong>Security Model:</strong> How are keys stored? Does it offer extra security features (e.g., Tor support)?</li> - <li><strong>Open Source:</strong> Is the code publicly available for review? This increases transparency and trust.</li> - <li><strong>Reputation:</strong> Vendor track record, community perception, responsiveness to issues.</li> - </ul> - <p><strong class="term">Prioritize wallets that are non-custodial, well-reviewed, and ideally open-source. Test with small amounts first.</strong></p> - </div> - </div> + <div class="col-12"> + <div + class="info-card btc-type-comparison" + id="card-app-compare-factors" + > + <div class="card-body"> + <h5 class="text-center"> + <i class="bi bi-sliders"></i> How to Choose an App Wallet + </h5> + <div class="card-content-wrapper"> + <!-- ADDED WARNING --> + <p class="summary text-center"> + Consider: Platform (Desktop/Mobile), Ease of Use, Features + (Lightning, Coin Control, Node Connect, HW Support), + Security Model, Open Source Status, Vendor Reputation. + <strong class="critical" + >App wallets carry inherent online risks; hardware wallets + are advised for substantial amounts. Focus on + Non-Custodial options where YOU control the + keys/seed.</strong + > + </p> + <button + class="btn btn-sm details-toggle mx-auto" + type="button" + data-bs-toggle="collapse" + data-bs-target="#collapseAppCompareFactors" + aria-expanded="false" + aria-controls="collapseAppCompareFactors" + > + Factors Explained <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div + class="collapse collapse-content" + id="collapseAppCompareFactors" + > + <h6>Key Comparison Factors for App Wallets:</h6> + <ul> + <li> + <strong>Platform:</strong> Is it available for your device + (iOS, Android, Windows, macOS, Linux)? + </li> + <li> + <strong>User Experience (UX):</strong> Is it intuitive for + beginners or geared towards advanced users? + </li> + <li> + <strong>Key Features:</strong> + <ul> + <li> + <span class="term">Lightning Network:</span> Does it + support faster, cheaper Layer 2 payments? + </li> + <li> + <span class="term">Coin Control:</span> Can you manually + select UTXOs for privacy/fee management? + </li> + <li> + <span class="term">Full Node Connection:</span> Can it + connect to your own Bitcoin node for maximum privacy? + </li> + <li> + <span class="term">Hardware Wallet Integration:</span> + Can it act as an interface for your hardware wallet? + </li> + <li> + <span class="term">Multisig Support:</span> Does it + facilitate setting up or signing multisignature + transactions? + </li> + </ul> + </li> + <li> + <strong>Security Model:</strong> How are keys stored? Does + it offer extra security features (e.g., Tor support)? + </li> + <li> + <strong>Open Source:</strong> Is the code publicly available + for review? This increases transparency and trust. + </li> + <li> + <strong>Reputation:</strong> Vendor track record, community + perception, responsiveness to issues. + </li> + </ul> + <p> + <strong class="term" + >Prioritize wallets that are non-custodial, well-reviewed, + and ideally open-source. Test with small amounts + first.</strong + > + </p> + </div> </div> + </div> - <!-- Specific App Wallet Cards --> - <div class="col-lg-4 col-md-6"> - <div class="info-card btc-type-comparison comparison-item" id="card-compare-app-sparrow"> - <div class="card-body"> - <h5><i class="bi bi-tools"></i> Sparrow Wallet</h5> - <div class="card-content-wrapper"> - <!-- FIXED DOUBLE MARKERS --> - <p class="summary"><span class="pros">[+] Desktop (Win/Mac/Linux), Feature-Rich (Coin Control, Node, HW, Multisig), Privacy focus (Tor), Open Source.</span> <span class="cons">[-] Desktop only, Can be complex for beginners.</span></p> - <p><a href="https://sparrowwallet.com/" target="_blank" rel="noopener noreferrer">sparrowwallet.com</a></p> - </div> - </div> - </div> - </div> - <div class="col-lg-4 col-md-6"> - <div class="info-card btc-type-comparison comparison-item" id="card-compare-app-bluewallet"> - <div class="card-body"> - <h5><i class="bi bi-phone-fill"></i> BlueWallet</h5> - <div class="card-content-wrapper"> - <p class="summary"><span class="pros">[+] Mobile (iOS/Android), User-Friendly, Supports Lightning (custodial LDK node option), HW integration, Multisig Vaults, Open Source.</span> <span class="cons">[-] Some advanced features less obvious, LN is custodial by default (but configurable).</span></p> - <p><a href="https://bluewallet.io/" target="_blank" rel="noopener noreferrer">bluewallet.io</a></p> - </div> - </div> - </div> - </div> - <div class="col-lg-4 col-md-6"> - <div class="info-card btc-type-comparison comparison-item" id="card-compare-app-electrum"> - <div class="card-body"> - <h5><i class="bi bi-pc-display"></i> Electrum</h5> - <div class="card-content-wrapper"> - <p class="summary"><span class="pros">[+] Desktop (Win/Mac/Linux), Mobile (Android), Long-standing, Advanced features (Coin Control, LN, Multisig, HW support), Open Source.</span> <span class="cons">[-] UI can feel dated/complex for beginners, relies on Electrum servers by default (can connect to own node).</span></p> - <p><a href="https://electrum.org/" target="_blank" rel="noopener noreferrer">electrum.org</a></p> - </div> - </div> - </div> - </div> - <div class="col-lg-4 col-md-6"> - <div class="info-card btc-type-comparison comparison-item" id="card-compare-app-muun"> - <div class="card-body"> - <h5><i class="bi bi-recycle"></i> Muun Wallet</h5> - <div class="card-content-wrapper"> - <p class="summary"><span class="pros">[+] Mobile (iOS/Android), Very Simple UI, Seamless On-chain/Lightning handling (via submarine swaps), Non-custodial LN.</span> <span class="cons">[-] Fewer advanced features (no coin control/node connect), Unique backup method (Emergency Kit + Email/Password or Social Recovery - understand it!).</span></p> - <p><a href="https://muun.com/" target="_blank" rel="noopener noreferrer">muun.com</a></p> - </div> - </div> - </div> - </div> - <div class="col-lg-4 col-md-6"> - <div class="info-card btc-type-comparison comparison-item" id="card-compare-app-green"> - <div class="card-body"> - <h5><i class="bi bi-shield-check"></i> Blockstream Green</h5> - <div class="card-content-wrapper"> - <p class="summary"><span class="pros">[+] Mobile (iOS/Android), Desktop (Limited), Strong focus on Multisig security (2-of-2 with server, or 2-of-3), HW support, Tor support, Open Source.</span> <span class="cons">[-] Default multisig relies on Blockstream server for one signature (2FA helps), Fewer features than Sparrow/Electrum.</span></p> - <p><a href="https://blockstream.com/green/" target="_blank" rel="noopener noreferrer">blockstream.com/green</a></p> - </div> - </div> - </div> - </div> - <div class="col-lg-4 col-md-6"> - <div class="info-card btc-type-comparison comparison-item" id="card-compare-app-nunchuk"> - <div class="card-body"> - <h5><i class="bi bi-diagram-3"></i> Nunchuk</h5> - <div class="card-content-wrapper"> - <p class="summary"><span class="pros">[+] Mobile (iOS/Android), Desktop (Win/Mac/Linux), Strong focus on Collaborative Multisig, Intuitive multisig setup, HW support, Air-gapped signing option.</span> <span class="cons">[-] Primarily designed for multisig (can do single sig), Subscription model for some features.</span></p> - <p><a href="https://nunchuk.io/" target="_blank" rel="noopener noreferrer">nunchuk.io</a></p> - </div> - </div> - </div> - </div> - <!-- Spacer/Choice Card --> - <div class="col-lg-4 col-md-6"> - <div class="info-card btc-type-comparison comparison-item" id="card-app-compare-choice"> - <div class="card-body"> - <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">Choose based on your primary device (mobile/desktop), technical comfort, need for specific features like Lightning or Multisig, and privacy requirements. <strong class="term">Always download from official sources and verify authenticity where possible.</strong></p> - </div> - </div> - </div> - </div> - </div> <!-- /.row --> - </div> <!-- /.schema-container --> - + <!-- Specific App Wallet Cards --> + <div class="col-lg-4 col-md-6"> + <div + class="info-card btc-type-comparison comparison-item" + id="card-compare-app-sparrow" + > + <div class="card-body"> + <h5><i class="bi bi-tools"></i> Sparrow Wallet</h5> + <div class="card-content-wrapper"> + <!-- FIXED DOUBLE MARKERS --> + <p class="summary"> + <span class="pros" + >[+] Desktop (Win/Mac/Linux), Feature-Rich (Coin Control, + Node, HW, Multisig), Privacy focus (Tor), Open + Source.</span + > + <span class="cons" + >[-] Desktop only, Can be complex for beginners.</span + > + </p> + <p> + <a + href="https://sparrowwallet.com/" + target="_blank" + rel="noopener noreferrer" + >sparrowwallet.com</a + > + </p> + </div> + </div> + </div> + </div> + <div class="col-lg-4 col-md-6"> + <div + class="info-card btc-type-comparison comparison-item" + id="card-compare-app-bluewallet" + > + <div class="card-body"> + <h5><i class="bi bi-phone-fill"></i> BlueWallet</h5> + <div class="card-content-wrapper"> + <p class="summary"> + <span class="pros" + >[+] Mobile (iOS/Android), User-Friendly, Supports + Lightning (custodial LDK node option), HW integration, + Multisig Vaults, Open Source.</span + > + <span class="cons" + >[-] Some advanced features less obvious, LN is custodial + by default (but configurable).</span + > + </p> + <p> + <a + href="https://bluewallet.io/" + target="_blank" + rel="noopener noreferrer" + >bluewallet.io</a + > + </p> + </div> + </div> + </div> + </div> + <div class="col-lg-4 col-md-6"> + <div + class="info-card btc-type-comparison comparison-item" + id="card-compare-app-electrum" + > + <div class="card-body"> + <h5><i class="bi bi-pc-display"></i> Electrum</h5> + <div class="card-content-wrapper"> + <p class="summary"> + <span class="pros" + >[+] Desktop (Win/Mac/Linux), Mobile (Android), + Long-standing, Advanced features (Coin Control, LN, + Multisig, HW support), Open Source.</span + > + <span class="cons" + >[-] UI can feel dated/complex for beginners, relies on + Electrum servers by default (can connect to own + node).</span + > + </p> + <p> + <a + href="https://electrum.org/" + target="_blank" + rel="noopener noreferrer" + >electrum.org</a + > + </p> + </div> + </div> + </div> + </div> + <div class="col-lg-4 col-md-6"> + <div + class="info-card btc-type-comparison comparison-item" + id="card-compare-app-muun" + > + <div class="card-body"> + <h5><i class="bi bi-recycle"></i> Muun Wallet</h5> + <div class="card-content-wrapper"> + <p class="summary"> + <span class="pros" + >[+] Mobile (iOS/Android), Very Simple UI, Seamless + On-chain/Lightning handling (via submarine swaps), + Non-custodial LN.</span + > + <span class="cons" + >[-] Fewer advanced features (no coin control/node + connect), Unique backup method (Emergency Kit + + Email/Password or Social Recovery - understand it!).</span + > + </p> + <p> + <a + href="https://muun.com/" + target="_blank" + rel="noopener noreferrer" + >muun.com</a + > + </p> + </div> + </div> + </div> + </div> + <div class="col-lg-4 col-md-6"> + <div + class="info-card btc-type-comparison comparison-item" + id="card-compare-app-green" + > + <div class="card-body"> + <h5><i class="bi bi-shield-check"></i> Blockstream Green</h5> + <div class="card-content-wrapper"> + <p class="summary"> + <span class="pros" + >[+] Mobile (iOS/Android), Desktop (Limited), Strong focus + on Multisig security (2-of-2 with server, or 2-of-3), HW + support, Tor support, Open Source.</span + > + <span class="cons" + >[-] Default multisig relies on Blockstream server for one + signature (2FA helps), Fewer features than + Sparrow/Electrum.</span + > + </p> + <p> + <a + href="https://blockstream.com/green/" + target="_blank" + rel="noopener noreferrer" + >blockstream.com/green</a + > + </p> + </div> + </div> + </div> + </div> + <div class="col-lg-4 col-md-6"> + <div + class="info-card btc-type-comparison comparison-item" + id="card-compare-app-nunchuk" + > + <div class="card-body"> + <h5><i class="bi bi-diagram-3"></i> Nunchuk</h5> + <div class="card-content-wrapper"> + <p class="summary"> + <span class="pros" + >[+] Mobile (iOS/Android), Desktop (Win/Mac/Linux), Strong + focus on Collaborative Multisig, Intuitive multisig setup, + HW support, Air-gapped signing option.</span + > + <span class="cons" + >[-] Primarily designed for multisig (can do single sig), + Subscription model for some features.</span + > + </p> + <p> + <a + href="https://nunchuk.io/" + target="_blank" + rel="noopener noreferrer" + >nunchuk.io</a + > + </p> + </div> + </div> + </div> + </div> + <!-- Spacer/Choice Card --> + <div class="col-lg-4 col-md-6"> + <div + class="info-card btc-type-comparison comparison-item" + id="card-app-compare-choice" + > + <div class="card-body"> + <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"> + Choose based on your primary device (mobile/desktop), + technical comfort, need for specific features like Lightning + or Multisig, and privacy requirements. + <strong class="term" + >Always download from official sources and verify + authenticity where possible.</strong + > + </p> + </div> + </div> + </div> + </div> + </div> + <!-- /.row --> + </div> + <!-- /.schema-container --> - <!-- =============================================== --> - <!-- SECTION X: Common Mistakes & Pitfalls (Renumbered) --> - <!-- =============================================== --> - <div class="schema-container cat-pitfalls" data-section-id="section-pitfalls"> + <!-- =============================================== --> + <!-- SECTION X: Common Mistakes & Pitfalls (Renumbered) --> + <!-- =============================================== --> + <div + class="schema-container cat-pitfalls" + data-section-id="section-pitfalls" + > <!-- Note: This becomes Section X --> - <h2 class="section-title" id="section-pitfalls"><i class="bi bi-exclamation-diamond-fill"></i> // X. How People Lose Bitcoin (Avoid These!)</h2> + <h2 class="section-title" id="section-pitfalls"> + <i class="bi bi-exclamation-diamond-fill"></i> // X. 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 Loss / Compromise</h5> - <div class="card-content-wrapper"> - <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> + <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 Loss / Compromise + </h5> + <div class="card-content-wrapper"> + <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> - <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 / Scams</h5> - <div class="card-content-wrapper"> - <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-phishing"> + <div class="card-body"> + <h5><i class="bi bi-broadcast"></i> Phishing / Scams</h5> + <div class="card-content-wrapper"> + <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 class="col-lg-4 col-md-6"> - <div class="info-card btc-type-pitfall" id="card-pitfall-malware"> - <div class="card-body"> - <h5><i class="bi bi-virus"></i> Malware on Computer/Phone</h5> - <div class="card-content-wrapper"> - <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="card-body"> + <h5><i class="bi bi-virus"></i> Malware on Computer/Phone</h5> + <div class="card-content-wrapper"> + <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 class="col-lg-4 col-md-6"> - <div class="info-card btc-type-pitfall" id="card-pitfall-physical"> - <div class="card-body"> - <h5><i class="bi bi-person-fill-x"></i> Physical Theft / Coercion</h5> - <div class="card-content-wrapper"> - <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="card-body"> + <h5> + <i class="bi bi-person-fill-x"></i> Physical Theft / Coercion + </h5> + <div class="card-content-wrapper"> + <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 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-hdd-rack-fill"></i> Device Issues (Without Backup)</h5> - <div class="card-content-wrapper"> - <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-device"> + <div class="card-body"> + <h5> + <i class="bi bi-hdd-rack-fill"></i> Device Issues (Without + Backup) + </h5> + <div class="card-content-wrapper"> + <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 class="col-lg-4 col-md-6"> - <div class="info-card btc-type-pitfall" id="card-pitfall-estate"> - <div class="card-body"> - <h5><i class="bi bi-person-slash"></i> Lack of Inheritance Plan</h5> - <div class="card-content-wrapper"> - <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="card-body"> + <h5> + <i class="bi bi-person-slash"></i> Lack of Inheritance Plan + </h5> + <div class="card-content-wrapper"> + <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 class="col-lg-4 col-md-6"> - <div class="info-card btc-type-pitfall" id="card-pitfall-supply"> - <div class="card-body"> - <h5><i class="bi bi-truck"></i> Supply Chain / Bad Vendor</h5> - <div class="card-content-wrapper"> - <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"> + <div class="info-card btc-type-pitfall" id="card-pitfall-supply"> + <div class="card-body"> + <h5><i class="bi bi-truck"></i> Supply Chain / Bad Vendor</h5> + <div class="card-content-wrapper"> + <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 class="col-lg-4 col-md-6"> <!-- Spacer/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 --> + </div> + <div class="col-lg-4 col-md-6"> + <!-- Spacer/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 XI: Glossary (Renumbered) --> - <!-- ======================= --> - <div class="schema-container cat-glossary" data-section-id="section-glossary"> + <!-- ======================= --> + <!-- SECTION XI: Glossary (Renumbered) --> + <!-- ======================= --> + <div + class="schema-container cat-glossary" + data-section-id="section-glossary" + > <!-- Note: This becomes Section XI --> - <h2 class="section-title" id="section-glossary"><i class="bi bi-book-half"></i> // XI. 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> Key Terms Defined</h5> - <div class="card-content-wrapper"> - <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"> - View Glossary <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseGlossary"> - <dl> - <!-- Reviewed/Refined 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>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> The most secure way to hold Bitcoin, typically achieved using hardware wallets or fully 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; "Not your keys, not your coins."</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> The recommended standard for significant holdings.</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> Convenient for spending, but carries higher risk 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>). This cheatsheet focuses on non-custodial solutions.</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> Empowers the user but requires responsibility.</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> + <h2 class="section-title" id="section-glossary"> + <i class="bi bi-book-half"></i> // XI. 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> Key Terms Defined + </h5> + <div class="card-content-wrapper"> + <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" + > + View Glossary <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseGlossary"> + <dl> + <!-- Reviewed/Refined 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> + 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 + > + The most secure way to hold Bitcoin, typically achieved + using hardware wallets or fully 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; "Not your keys, not + your coins."</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 + > + The recommended standard for significant holdings. + </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 + > + Convenient for spending, but carries higher risk 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 + >). This cheatsheet focuses on non-custodial solutions. + </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 + > + Empowers the user but requires responsibility. + </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> - </div> <!-- /.row --> - </div> <!-- /.schema-container --> + </div> + </div> + <!-- /.row --> + </div> + <!-- /.schema-container --> - <!-- ========================== --> - <!-- SECTION XII: Further Resources (Renumbered) --> - <!-- ========================== --> - <div class="schema-container cat-resources" data-section-id="section-resources"> + <!-- ========================== --> + <!-- SECTION XII: Further Resources (Renumbered) --> + <!-- ========================== --> + <div + class="schema-container cat-resources" + data-section-id="section-resources" + > <!-- Note: This becomes Section XII --> - <h2 class="section-title" id="section-resources"><i class="bi bi-compass-fill"></i> // XII. 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> Recommended Links</h5> - <div class="card-content-wrapper"> - <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"> - Browse Links <i class="bi bi-chevron-down"></i> - </button> - </div> - </div> - <div class="collapse collapse-content" id="collapseResources"> - <h6>A. Recommended Software Wallets (Non-Custodial):</h6> - <ul> - <!-- Links updated to point to correct section IX cards where applicable --> - <li>Desktop: <a href="#card-compare-app-sparrow">Sparrow Wallet</a> (Feature-rich, Privacy/Node focus), <a href="#card-compare-app-electrum">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="#card-compare-app-bluewallet">BlueWallet</a> (User-friendly, versatile), <a href="#card-compare-app-muun">Muun Wallet</a> (Simple, Lightning focus), <a href="#card-compare-app-green">Blockstream Green</a> (Multisig options)</li> - <li>Multisig Coordinator: <a href="#card-compare-app-nunchuk">Nunchuk</a> (Mobile/Desktop)</li> - </ul> - <h6>B. Reputable Hardware Wallet Vendors (Buy Direct!):</h6> - <ul> - <!-- Links updated to point to correct section VIII cards --> - <li><a href="#card-compare-trezor">Trezor</a></li> - <li><a href="#card-compare-coldcard">Coldcard</a> (Coinkite)</li> - <li><a href="#card-compare-ledger">Ledger</a></li> - <li><a href="#card-compare-bitbox">BitBox</a> (Shift Crypto)</li> - <li><a href="#card-compare-jade">Blockstream Jade</a></li> - <li><a href="#card-compare-passport">Foundation Devices</a> (Passport)</li> - <li><a href="#card-compare-seedsigner">Seedsigner</a> (DIY Project)</li> - </ul> - <h6>C. Block Explorers:</h6> - <ul> - <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. Educational Resources:</h6> - <ul> - <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. 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> - <li><a href="https://cheatsheets.davidveksler.com" target="_blank" rel="noopener noreferrer">More Cheatsheets</a></li> - </ul> - </div> - </div> + <h2 class="section-title" id="section-resources"> + <i class="bi bi-compass-fill"></i> // XII. 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> Recommended Links + </h5> + <div class="card-content-wrapper"> + <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" + > + Browse Links <i class="bi bi-chevron-down"></i> + </button> + </div> + </div> + <div class="collapse collapse-content" id="collapseResources"> + <h6>A. Recommended Software Wallets (Non-Custodial):</h6> + <ul> + <!-- Links updated to point to correct section IX cards where applicable --> + <li> + Desktop: + <a href="#card-compare-app-sparrow">Sparrow Wallet</a> + (Feature-rich, Privacy/Node focus), + <a href="#card-compare-app-electrum">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="#card-compare-app-bluewallet">BlueWallet</a> + (User-friendly, versatile), + <a href="#card-compare-app-muun">Muun Wallet</a> (Simple, + Lightning focus), + <a href="#card-compare-app-green">Blockstream Green</a> + (Multisig options) + </li> + <li> + Multisig Coordinator: + <a href="#card-compare-app-nunchuk">Nunchuk</a> + (Mobile/Desktop) + </li> + </ul> + <h6>B. Reputable Hardware Wallet Vendors (Buy Direct!):</h6> + <ul> + <!-- Links updated to point to correct section VIII cards --> + <li><a href="#card-compare-trezor">Trezor</a></li> + <li> + <a href="#card-compare-coldcard">Coldcard</a> (Coinkite) + </li> + <li><a href="#card-compare-ledger">Ledger</a></li> + <li> + <a href="#card-compare-bitbox">BitBox</a> (Shift Crypto) + </li> + <li><a href="#card-compare-jade">Blockstream Jade</a></li> + <li> + <a href="#card-compare-passport">Foundation Devices</a> + (Passport) + </li> + <li> + <a href="#card-compare-seedsigner">Seedsigner</a> (DIY + Project) + </li> + </ul> + <h6>C. Block Explorers:</h6> + <ul> + <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. Educational Resources:</h6> + <ul> + <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. 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> + <li> + <a + href="https://cheatsheets.davidveksler.com" + target="_blank" + rel="noopener noreferrer" + >More Cheatsheets</a + > + </li> + </ul> + </div> </div> - </div> <!-- /.row --> - </div> <!-- /.schema-container --> - + </div> + </div> + <!-- /.row --> + </div> + <!-- /.schema-container --> + </div> + <!-- /container --> -</div> <!-- /container --> + <footer class="container text-center"> + <p id="footer-year"></p> + <!-- Footer text set by JS --> + </footer> -<footer class="container text-center"> - <p id="footer-year"></p> <!-- Footer text set by JS --> -</footer> - -<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/js/bootstrap.bundle.min.js"></script> -<script> -document.addEventListener('DOMContentLoaded', () => { - const footerYearEl = document.getElementById('footer-year'); - if (footerYearEl) { - // Updated Footer Text with Dynamic Year - footerYearEl.textContent = `Bitcoin Wallet Cheatsheet v2.2 - Secure Self-Custody Guide - © ${new Date().getFullYear()} David Veksler (Content Refined)`; - } + <script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/js/bootstrap.bundle.min.js"></script> + <script> + document.addEventListener("DOMContentLoaded", () => { + const footerYearEl = document.getElementById("footer-year"); + if (footerYearEl) { + // Updated Footer Text with Dynamic Year + 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}"]`); - const icon = button ? button.querySelector('.bi') : null; - if (button && icon) { + // 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}"]` + ); + const icon = button ? button.querySelector(".bi") : null; + if (button && icon) { const updateIcon = (isShown) => { - icon.classList.toggle('bi-chevron-up', isShown); - icon.classList.toggle('bi-chevron-down', !isShown); + 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')); + // 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)); - } - }); -}); -</script> -</body> -</html> \ No newline at end of file + collapseEl.addEventListener("show.bs.collapse", () => + updateIcon(true) + ); + collapseEl.addEventListener("hide.bs.collapse", () => + updateIcon(false) + ); + } + }); + }); + </script> + </body> +</html>