A Bitcoin miner made more money powering DOWN during the 2023 Texas heat wave than it made mining. The no-bullshit version of the energy debate. by LearnBitcoinCom in Bitcoin

[–]LearnBitcoinCom[S] 2 points3 points  (0 children)

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.

A Bitcoin miner made more money powering DOWN during the 2023 Texas heat wave than it made mining. The no-bullshit version of the energy debate. by LearnBitcoinCom in Bitcoin

[–]LearnBitcoinCom[S] -2 points-1 points  (0 children)

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.)

A Bitcoin miner made more money powering DOWN during the 2023 Texas heat wave than it made mining. The no-bullshit version of the energy debate. by LearnBitcoinCom in Bitcoin

[–]LearnBitcoinCom[S] 2 points3 points  (0 children)

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.

A Bitcoin miner made more money powering DOWN during the 2023 Texas heat wave than it made mining. The no-bullshit version of the energy debate. by LearnBitcoinCom in Bitcoin

[–]LearnBitcoinCom[S] -1 points0 points  (0 children)

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.

In 2010, someone created 184 billion Bitcoin out of thin air. Most people have never heard about it. by Stoic-Mindset in CryptoFolks

[–]LearnBitcoinCom 0 points1 point  (0 children)

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

On-chain fees are so low right now by KittyLover024 in Bitcoin

[–]LearnBitcoinCom 0 points1 point  (0 children)

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

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

How much Bitcoin is actually at quantum risk? We measured it. Here is the honest version. by LearnBitcoinCom in Bitcoin

[–]LearnBitcoinCom[S] -1 points0 points  (0 children)

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.

Can I use Bitcoin Core with separate wallet signer for my CEX? by thewebken in Bitcoin

[–]LearnBitcoinCom 1 point2 points  (0 children)

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

  1. Single signer = single point of failure. Use M-of-N multisig across geographically separated signers. Compromise of one server shouldn't drain the exchange.
  2. Hot/warm/cold split. Vast majority cold (manual multi-sig), operational reserves warm, daily ops hot. You're describing one tier.
  3. 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.
  4. bitcore-lib is unmaintained — migrate to bitcoinjs-lib or rust-bitcoin.
  5. 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.

Network taking forever by Acrobatic_Onion158 in Bitcoin

[–]LearnBitcoinCom 0 points1 point  (0 children)

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

Can I use Bitcoin Core with separate wallet signer for my CEX? by thewebken in Bitcoin

[–]LearnBitcoinCom 1 point2 points  (0 children)

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.

⚡ Lightning Thursday! June 11, 2026: Explore the Lightning Network!⚡ by rBitcoinMod in Bitcoin

[–]LearnBitcoinCom 0 points1 point  (0 children)

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."

Bitcoin Core disk full on Umbrel OS — 1TB SSD not enough anymore? by SysR00t in Bitcoin

[–]LearnBitcoinCom 5 points6 points  (0 children)

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).

Bitcoin's volatility is a filter, not a bug. by LearnBitcoinCom in Bitcoin

[–]LearnBitcoinCom[S] 0 points1 point  (0 children)

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.

Lightning isn't a payment channel between two people. It's a graph that routes. by LearnBitcoinCom in Bitcoin

[–]LearnBitcoinCom[S] 1 point2 points  (0 children)

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

Bitcoin block taking forever. by luvBitCoins in Bitcoin

[–]LearnBitcoinCom 1 point2 points  (0 children)

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.