No one will ever get their PhD in CSS, because they won’t be able to format the white paper.

Wishing for unfilled blocks, an empty mempool, is wishing for #Bitcoin to fail. Full blocks and market fees are the expected outcome of Bitcoin’s success.

A lot of the #Bitcoin arguments lately have been about path dependence. That is, what path future history will take. I find these arguments hollow. The path of future history is incredibly hard to predict. Social systems are reactive and dynamic. Volatile in the short term. If you believe in the eventual outcome, aim for that, and let future history figure itself out. So, would dropping the OP_RETURN policy limit “send a message” to shitcoiners? Maybe? But I say, who cares? If you have a technical argument, I want to hear it. Thinking about incentives (behavior) is fine. But then extrapolate to the end. What does the end state look like? Because this is what matters. The long, long term. Having low time preference means focusing on the horizon. Not short-term politics.

Why do I have to talk to the deli worker? Why isn’t there a kiosk like Panera bread? This is not hard, people. We have the technology.

We’re at an inflection point in AI. Those who fail to adopt are being left behind, in real time. But there’s good news for laggards. Future tools will be better, helping them close the gap.

2017: consensus wars (chain splits) 2025: policy wars (network splits) It’s gonna be OK. #Bitcoin

The results of the Milgram experiments were shocking.

S U P E R C Y C L E View quoted note →

Jimbo’s take on the Bitcoin policy/inscription debate: * Witness Data (inscriptions): Already prunable! Like OP_RETURN, it avoids permanent data bloat for non-archival nodes. * Fees/Full Blocks = Success: High fees aren't failure, they mean Bitcoin is in demand. Get used to it if you believe in Bitcoin’s success. * Market Over Policy: Fee market naturally prices out inefficient uses over time. Let it work. Stop trying to centrally plan block space via Core policy changes. * Core should be Consensus ONLY: Bitcoin Core should focus exclusively on consensus rules. Stop the bikeshedding over non-consensus policy (like OP_RETURN limits) within Core development. * Balkanize Policy: Node operators deserve choice! Let them pick mempool/relay policies like Linux distros. Embrace complexity/responsibility as the price of freedom. * Decentralize More: Block building/template construction (Stratum V2+) also belongs outside Core, just like hashing hardware and wallets. * Trust Emergent Order: Bitcoin self-regulates via incentives. Stop the central planning hubris; trust individual choices & the protocol's design. Current debates are opportunities to push more functions out of Core. #Bitcoin

Gold has doubled in fiat price over three years. Imagine being impressed by this. #Bitcoin

S U P E R C Y C L E View quoted note →

Trustworthy Loyal Helpful Friendly Courteous Kind