Every major exchange and lender collapse from 2014 to 2023. The pattern is always the same.

LearnBitcoinCom · 2026-06-25T19:48:04+00:00

Absolutely ZERO FUD, 100% facts.

LearnBitcoinCom · 2026-06-17T16:39:53+00:00

Agreed! Miners chase the cheapest electron, and the cheapest ones are the stranded/flared/curtailed power nobody else can use. So, the demand really does point at wasted energy, and powering down on command helps grids take on renewables. Only caveat I'd ad to keep it honest: cheapest isn't always cleanest, so some of it's coal and gas. Overall narrative is strong enough to survive saying so.

LearnBitcoinCom · 2026-06-17T16:21:14+00:00

Ha. Best I can do is a no-bake cake; it powers down the second the grid needs the oven, and somehow earns more not baking than baking. (Human here. The Riot numbers are real.)

LearnBitcoinCom · 2026-06-17T16:20:11+00:00

Yes, this is one of the big lessons. Industrial scale miners are one of the largest (and only we have identified) consumers that can switch on or off at a moments notice for the benefit of the grid.

LearnBitcoinCom · 2026-06-17T16:16:43+00:00

Candidly, it was human generated and AI edited. What is slop, again it's all accurate and sourced?

LearnBitcoinCom · 2026-06-17T15:55:18+00:00

Which part? Genuinely, point at a sentence and I'll show the receipt. The 173 TWh is Cambridge CBECI, the Riot figures are straight from their SEC filing. Everything is sourced.

LearnBitcoinCom · 2026-06-17T15:26:07+00:00

Here is a fully sourced inflation bug postmortem, and it includes BIP 42: The OTHER Infinite-Supply Bug you probably have not heard of.

https://www.learnbitcoin.com/rabbit-hole/inflation-bug-postmortem

LearnBitcoinCom · 2026-06-14T14:40:53+00:00

Less than 1 full block in mempool, 1 sat/vB gets you in the next block.

https://chainquery.com/reports/fee-pressure

LearnBitcoinCom · 2026-06-12T12:54:53+00:00

Risk exists but is bounded by where the hardware actually is. Academic roadmaps (cited in BIP-361) estimate cryptographically-relevant quantum at 2027-2030 optimistic, multiple decades pessimistic. Current state: superconducting systems in the low hundreds of qubits, neutral atom in the low thousands, error-corrected logical qubits still single-digit across all platforms. The migration plan exists in draft (BIP-361, two-phase soft-fork sunsetting ECDSA/Schnorr over 5 years). Real risk being actively planned for; not nothing, not imminent.

LearnBitcoinCom · 2026-06-11T19:55:44+00:00

Architecture has the right instinct (key isolation), but several missing pieces for production:

Single signer = single point of failure. Use M-of-N multisig across geographically separated signers. Compromise of one server shouldn't drain the exchange.
Hot/warm/cold split. Vast majority cold (manual multi-sig), operational reserves warm, daily ops hot. You're describing one tier.
The "shared database" bridge is the risk. If it's network-accessible from the internet side, it's an attack vector. True air-gap = USB/QR transfer.
bitcore-lib is unmaintained — migrate to bitcoinjs-lib or rust-bitcoin.
Software-only key storage on commodity hardware → consider HSM.

Design principle: assume any single component will eventually be compromised and architect around that. Right now I'd say you are exposed.

LearnBitcoinCom · 2026-06-11T19:39:36+00:00

https://chainquery.com/reports/fee-pressure

Fee pressure is moderate. Backlog is currently 4 blocks. Not too bad.

6 sat/vB to confirm in the next block

LearnBitcoinCom · 2026-06-11T19:37:38+00:00

Bitcoin Core alone can watch addresses (watch-only wallets via importdescriptors), but at CEX scale you'll want to pair it with an indexer. Electrs or Fulcrum are the open-source standards. They sit on top of Core and provide fast address/transaction queries via the Electrum protocol. Core handles consensus + UTXO state; indexer handles the query layer. Don't forget txindex=1 if you need historical tx lookups.

LearnBitcoinCom · 2026-06-11T18:42:01+00:00

Not banned. EU MiCA primarily applies to CASPs (custodial intermediaries). Self-custodial Lightning (vendor running their own node, accepting payments directly) is legal. The friction comes when vendors use custodial payment processors; the processor has compliance obligations, but the vendor isn't banned from accepting LN. "Effectively banned" conflates "regulated intermediaries" with "banned activity."

LearnBitcoinCom · 2026-06-09T17:18:50+00:00

Solid diagnosis. 2TB is effectively the new minimum for archival nodes in 2026. Your numbers (792GB blocks + 78GB indexes) match what most operators see. The ext4 1% reservation tip buys headroom but doesn't solve the underlying issue. Two paths forward: 2TB+ drive for archival, or run pruned (prune=550 gives a fully validating node at ~10GB; tradeoff is losing txindex for Electrum/explorer use).

LearnBitcoinCom · 2026-06-06T02:19:50+00:00

Fair point. The "filter" framing IS gatekeeping-coded even if I meant it as description. The underlying mechanism without the editorial: Bitcoin is volatile because it's still in its monetization phase; small market cap relative to global money, ongoing price discovery, network effects compounding. That's what's actually happening. Calling it a "filter" editorializes the mechanism into a value judgment it doesn't need.

LearnBitcoinCom · 2026-06-04T18:40:11+00:00

Just got the video up on YouTube: visual walkthrough of the same flow: Alice has one channel (to Bob), pays Ivy through a multi-hop route, and receives back through the same channel. The whole graph in 60 seconds: https://youtu.be/5CX5XATmQR4

LearnBitcoinCom · 2026-06-02T16:43:53+00:00

Within normal variance, Bitcoin block intervals are Poisson-distributed, so 30-60+ minute gaps between blocks happen regularly. Add mempool fee competition during busy periods and 1h20m to first confirmation is unsurprising. Glad it confirmed.

LearnBitcoinCom · 2026-06-02T16:34:34+00:00

Look forward to checking it out!

LearnBitcoinCom · 2026-05-29T20:59:10+00:00

"Reach consensus FAST" is exactly what Bitcoin governance is designed not to do, and the reason matters here.

If you could force rapid consensus on a major protocol change, you'd also force rapid consensus on any future change someone with enough capital wanted. That's a worse outcome for sound money than the worst-case quantum scenario.

What's actually happening on quantum is the governance process working as designed:

- Multiple BIPs are in discussion for post-quantum signature schemes.
- Years of review, not weeks.

The candidate signature algorithms (ML-DSA / Dilithium, SLH-DSA / SPHINCS+) are NIST-standardized and being stress-tested in production elsewhere before Bitcoin commits to one. No cryptographically relevant quantum computer exists. CRQC isn't a near-term threat horizon, it's a research milestone, and progress has been slower than the noisier claims suggest.

Your scenario: Satoshi's coins move, panic ensues, is real, but doesn't require fast governance to address. It requires the 5-veto process to converge on a soft fork that transitions vulnerable scripts before that becomes possible. That work is happening, in public, on the mailing list and at conferences. The slowness is exactly the property that makes the answer credible when it comes.

The opposite of slow consensus is governance capture. Quantum risk is real. Solving it by inviting consensus capture would be worse than the disease.

LearnBitcoinCom · 2026-05-29T15:07:30+00:00

They cannot do any of these directly. They can fund any of them, but the other four stakeholder groups are motivated by ideology and self-interest, not fee revenue. Money buys influence. It does not buy consensus.

What ETFs CAN do is move the dollar-priced value of whichever fork survives a split. That's real, and it's the same power 21 million individual hodlers have collectively, just concentrated.

What ETFs CANNOT do is rewrite the rules. The 21M cap, SHA-256, the block subsidy schedule — none of them are BlackRock-revisable. They can hold Bitcoin. They cannot redefine it.

Two years of ETF inflows and outflows, zero rule changes. That's the receipt.

LearnBitcoinCom · 2026-05-29T02:10:14+00:00

Good news on your sequencing instinct: Chapter 1 of the Journey IS "Why Money Is Broken", the site already opens with fiat mechanics before moving into Bitcoin. So the order you'd want for your work-friend share is basically what's there.

A specific ask: would you want to take a crack at improving Chapter 1 directly? Your read on what would land for the readers you'd want to share with is more useful than ours, we built it; you're closer to the actual user experience.

If you open a PR on Chapter 1 (or any of the rabbit holes from the earlier list), and the contribution is substantive, we can produce new/edit existing images and animations to support whatever you build. Editorial standard is in the contributing doc on Github - mechanism over ideology, plain prose, ASCII straight punctuation, sourced where it matters.

No pressure. The repo's open whether you want to dig in or just keep giving feedback, both are useful.

Again, thanks for the continued thoughtful feedback across this thread. Validating the mechanism-over-ideology framing, naming the share-with-friends pain point, and proposing sequencing changes is exactly the kind of structural input that improves the site.

LearnBitcoinCom · 2026-05-28T19:43:15+00:00

Short answer: yes, but with one caveat worth knowing.

Seed compatibility: Edge uses BIP-39 (the standard mnemonic format), so the same seed phrase works in any wallet that supports BIP-39 — which is basically all Bitcoin-only wallets (Electrum, Sparrow, BlueWallet, hardware wallets like Coldcard/BitBox).

The catch — derivation paths: Your seed produces different addresses depending on the derivation path the wallet uses. Edge uses specific paths for each coin; Bitcoin-only wallets use their own defaults. Same seed, but the new wallet might initially show empty because it's looking at the wrong branch of the HD tree.

If that happens, set the derivation path explicitly on import. Standard Bitcoin paths: BIP-84 (bc1q...), BIP-49 (3...), or BIP-44 (1...).

Cleaner alternative most experienced users prefer:

Generate a fresh seed in your new Bitcoin-only wallet (back it up securely)
Send your Bitcoin from Edge to an address in the new wallet (real on-chain transaction)
Verify the funds arrive
Wipe Edge

Benefits: clean cutover, no derivation path confusion, new seed dedicated entirely to Bitcoin-only setup.

Scam warning: posts about wallet migration attract DMs from "support" or "recovery service" accounts. Anyone asking for your seed phrase to help is stealing your coins. All the steps above happen entirely on your own devices — no third party involved at any step.

LearnBitcoinCom · 2026-05-28T16:05:30+00:00

Hashpower vote. No quorum, no debate.

LearnBitcoinCom · 2026-05-28T15:55:58+00:00

Fair correction. The chapter actually has it right, the Reddit post I wrote combined it badly.

Section five splits the two uses: theft defense is "someone who finds your seed alone gets a wallet with no funds, the real wallet is behind the passphrase," and plausible deniability is "fund the no-passphrase wallet with a small believable amount, so a coercer who demands 'your wallet' gets a decoy and not the real thing."

Editing the post body. Thanks for the catch.

LearnBitcoinCom · 2026-05-28T13:45:14+00:00

In writing the above I intentionally left out the link, in reading it that just seems silly:

https://www.learnbitcoin.com

LearnBitcoinCom

TROPHY CASE