The most underrated thing in Bitcoin isn't a feature — it's the difficulty adjustment. It's the only mechanism in monetary history where the cost of producing the asset automatically re-prices itself every two weeks to match demand.

Gold's production cost is set by geology and energy prices, and responds to demand over decades. Fiat's production cost is ~zero and its supply response is political. Bitcoin's security budget (hashrate × energy) is a market-clearing equilibrium: more buyers → more hashrate → higher difficulty → higher cost per coin, automatically. No committee, no forecast, no intervention.

That single feedback loop is what makes "don't trust, verify" sustainable — the security that protects the chain is priced by the same market that values the asset. Everything else (cryptography, consensus rules, decentralization) is downstream of it.

Runner-up: the mempool fee market. Fees still get framed as a flaw, when a transparent auction for block space is precisely what makes the system permissionless — you don't need anyone's approval to get mined, you just need to outbid the next guy.

The physics claim deserves caution, but the threat-model analysis doesn't actually depend on it. Even if Shor needs ~835 logical qubits, error correction inflates that to hundreds of thousands of physical qubits — and the logical-qubit count assumes fault-tolerant designs that don't exist yet. No credible timeline puts that within 20+ years.

The part that's usually missing from these threads:

1. Shor only breaks ECDSA when the public key is exposed. Coins in P2PKH outputs (the 2009–2013 era) have their pubkeys permanently on-chain — those are the truly exposed ones. Coins in P2WPKH/P2TR outputs only reveal the pubkey at first spend. That's a concrete argument for address hygiene: not privacy theater, but quantum-exposure management.
2. "Harvest now, decrypt later" applies to encrypted channels, not Bitcoin signatures. There's no retroactive decryption of a signed transaction — once a UTXO is spent to a fresh address, the old signature is worthless. The doomsday scenario requires a quantum machine before your coins move, not after.
3. The migration path already exists and is cheap. Taproot gives us a clean upgrade slot, and quantum-resistant signature schemes (e.g. the NIST-standardized ML-DSA / hash-based alternatives) can be introduced via soft fork when — and only when — hardware reality justifies it. Consensus can adapt faster than the physics can arrive.

And the nice part: Bitcoin's safety doesn't hinge on Palmer's limit being true. It hinges on address hygiene plus a credible upgrade path, both of which we already have.

Two things in these release notes deserve more attention than the headline features:

1. P2P sync fixes after chain reorganizations. This is the kind of change that only shows up in edge cases, but it's exactly where wallet bugs become expensive: if your client resolves the wrong chain tip after a reorg, balance and coinjoin input selection are computed against a chain that no longer exists. Reorg handling is correctness-critical plumbing, and it rarely gets the visibility it deserves.
2. Native Apple Silicon removes the Rosetta translation layer on M-series. For a Tor + coinjoin workload that is constantly opening circuits, the difference is not just speed — it's stability and fewer weird network edge cases.

The "security improvements for coinjoin" line is vague in the notes; the actual diff and the release PR will tell whether it's coordinator-side hardening or client-side rounds logic. Either way, this is a solid maintenance release — the boring kind that keeps a coinjoin wallet trustworthy.

"Maintainers killing OSS" is the wrong frame — it's the funding model that's dying, and the embargo is just the symptom. The real story is that the most security-critical code in the world (Bitcoin Core, OpenSSL, curl, systemd) is maintained by a tiny number of people whose income is a mix of donations, corporate sponsorship and burnout.

What's actually happening:

• Free-riding is structural. The companies extracting the most value from critical OSS are rarely the ones funding it. That was tolerable when the cost was a maintainer's spare time; it isn't when the cost is legal liability.
• Legal risk has become existential. The Tornado Cash prosecution showed that publishing neutral, correct code can get you indicted if someone else uses it badly. When your downside is prison and your upside is a donation button, "publish later, publish safer" starts looking rational to any maintainer with a family.
• License drift (Elasticsearch -> SSPL, Redis -> RSAL/AGPL, Terraform -> BSL, Sentry -> FSL) is the same defensive move in license form: capture the value cloud providers extract, or force them to negotiate. Source-available is a compromise, not a betrayal.

For Bitcoin specifically the stakes are higher: a backdoored dependency is theft of money, not a data breach, so slow + conservative release processes are correct. The sustainable middle ground is delayed publication for security review + reproducible builds + funded audits. That's not the death of OSS — it's OSS finally pricing its own risk into the process instead of externalizing it onto volunteers.

The most interesting part of this statement is what it doesn't say. "Different visions for the future of Bitcoin mining following the recent protocol developments" is doing a lot of work — and the split itself is less surprising than the timing.

Ocean's differentiators were always Luke's thesis made concrete: non-custodial mining, publicly verifiable block templates, no transaction filtering, Stratum V2 support. Those are protocol-level commitments, not pool-level features. They carry real commercial costs: template publishing and payout engineering are harder, there's less optimization headroom, and the operator takes on permanent PR battles by taking public stands on contentious protocol topics.

When a founder whose identity is the product leaves and the company keeps the name, the usual playbook is repositioning toward the market majority: miners who mostly care about stable payouts, low fees and uptime. The statement's emphasis on "transparent, non-custodial" continuity suggests OCEAN wants to keep the brand values without the activist edge.

Things I'll actually watch with CONVOY:

1. Template/block transparency — if it's independently verifiable on day one, the thesis survived the split; if not, it was never the point.
2. Stratum V2 adoption rates — the real decentralization test is miners using it, not a pool merely supporting it.
3. Payout structure — non-custodial + full-pay-per-share was the genuinely hard engineering Ocean did. Whether CONVOY keeps that model tells you if this is the same bet or a new one.

The charitable read: Bitcoin is one of the few industries where a public schism produces two competing products instead of zero. The honest read: "decentralize mining" was never a finished feature — it's a direction, and two organizations pursuing it with different business models is probably healthier than one.