Profile: 482d28d8...

I could answer in the same way: I get it, you are envious of Luke accomplishments.

Is fence-sitting becoming a bit uncomfortable Matt? Especially over a picket fence? Is your butt starting to feel slightly unpleasant?

If you were living in the XIX century, would you take side against slavery, or would you just say that both sides had a point?

Nobody touching the code of Bitcoin implementation should be paid. Ever. The incentives do not allign properly.

Bitcoin is too important to be left in engineers’ hands when they don’t grasp how much their reputation matters. Mempool will fragment into competing default settings and operations . It will diversify until even the fewest assumptions hold. Exactly what "core" developers were trying to prevent.

Hacker News is full of engineers. The tech discussions are usually useful and interesting, but the moment they go into non-technical stuff? You will see how arrogant they can get—often blind to their own ignorance. I have know sharp engineers in real life too, and a lot of them are also closed-minded and cocky. The exceptions? Usually folks building mission-critical systems or complex infrastructure, where mistakes can be catastrophic. Watch "core" torch their reputation by refusing to course-correct, just doubling down until it is all gone.

Replying to Avatar Ben Ewing

🚩 False Dichotomies

1. “A network is either permissionless or authoritarian. Open or closed. Censorship-resistant or censored.”

✘ False dichotomy.

• Networks exist on a spectrum: some are semi-open (e.g. federations, permissioned blockchains, P2P overlays).

• Permissionlessness can also be partial (open to connect, but with rate limits or whitelists).

• “Authoritarian” is a rhetorical label — most systems balance openness with practical controls.

⸝

🚩 Spam & Security Assumptions

2. “Open networks inevitably run into spam and impersonation.”

✘ Misleading.

• True they are vulnerable, but mitigations exist beyond just PoW: rate limits, staking, identity attestations, proof-of-human systems.

• Saying “inevitable” ignores 30+ years of real-world open systems like email (with spam filters, DKIM, reputation systems).

3. “Sybil attacks, DDoS attacks, resource exhaustion… can only be solved via PoW + WoT.”

✘ Wrong.

• Proof-of-Stake, proof-of-space/time, trusted hardware, economic bonding, and many other mechanisms also mitigate sybils.

• Web-of-Trust (WoT) has historically failed to scale (PGP being the canonical example).

⸝

4. “I include sats in this equation implicitly, because sats are just difficulty-adjusted PoW.”

✘ Wrong.

• Sats are ledger entries, not work itself. The work (hashing) secures the chain; it doesn’t imbue the units with intrinsic PoW that can be “re-spent” elsewhere.

• PoW isn’t portable: you can’t reuse Bitcoin’s PoW to defend against email spam, DDoS, or sybils. The work is consumed once in block validation.

• Claiming sats = PoW overstates what they can do outside the Bitcoin ledger.

⸝

🚩 Identity & Money Claims

5. “Identity has to be cryptographic, which means taken and defended, as opposed to given.”

✘ Overstated.

• Cryptographic keys = control, but most identity in practice is socially anchored (governments, institutions, web-of-trust attestations).

• Purely cryptographic identity (keys alone) fails when keys are lost, stolen, or reset.

6. “Money has to be bearer instrument … cash, not credit.”

✘ Misleading.

• Most modern money is credit-based (bank deposits, treasuries). Bearer instruments (cash, gold, crypto) exist but are not the only form of “money proper.”

• This is more of a philosophical preference than a factual truth.

⸝

7. Keys and sats have the power to usher in a new era of the internet.”

✘ Overclaim.

• Keys already underpin the internet (TLS, SSH, DNSSEC). They don’t, by themselves, fix spam, identity, or governance.

• Sats are not a generalized anti-spam tool. Even with protocols like bithash on nostr, using payments as a universal rate-limit is impractical: too costly for normal use, easy to bypass via custodians, and risks centralizing around payment hubs.

• Cryptographic signing ≠ trust. Signing proves a message came from a key, but not that the key belongs to who you think, or that the content is truthful. Saylor’s “private-key identity” vision collapses without external social/organizational anchors.

• In short: keys + sats can improve certain systems, but they cannot alone restructure the whole internet.

8. “The Web is dead. Long live the web.”

✘ Rhetorical flourish, but misleading.

• The Web is evolving (Web3, federated services, p2p overlays). It’s not “dead,” just changing.

⸝

✅ In short:

• He sets up false dichotomies (“open or authoritarian”).

• Misrepresents sats as “just PoW.”

• Ignores non-PoW solutions to spam and Sybils.

• Treats WoT as viable at scale when history shows otherwise.

• Frames bearer-money-only as a necessity when in reality credit money dominates.

• Declares “Web is dead” for rhetorical drama, not accuracy.

AI Slob.

Peter Todd is nothing like Satoshi Nakamoto

-------------------------------------------------------------

Peter Todd epitomizes the brilliant engineer: deep technical mastery, elegant solutions to defined problems. Yet this very specialization blinds him to systemic effects.

Satoshi's genius wasn't technical—it was seeing the Byzantine Generals Problem as human, not computational. Where engineers seek optimal code, Satoshi created messy, resilient consensus.

Todd proposes "obvious" improvements that risk hidden centralization. He optimizes trees while the forest burns. This isn't personal failure—it's engineering training that rewards solving problems within systems rather than questioning systems themselves.

Bitcoin's strength lies in preventing any engineer, however gifted, from imposing changes through technical superiority alone. The block size wars showed this: engineers saw scaling problems with technical solutions; systems thinkers saw existential threats.

Revolutionary systems need minds that think in incentives not algorithms, emergence not specification, antifragility not optimization. They design not for control but controlled chaos.

That's why engineers like Todd MUST NEVER have central authority over Bitcoin. Their specialized neural pathways, perfected for bounded problems, cannot grasp the higher-order effects that make or break distributed systems.

Innovation requires diverse approaches battling without any single voice able to silence others—precisely what Satoshi built, and what no traditional engineer would ever design.

Let's keep Knots growing!

Spammers are incentivized to use the witnessspacee, therefore removing a spam filter will only give them more opportunity to spam.

Witness data is counted at 1/4 of the data in the legacy part of the transaction. OP_RETURN lives in the non-witness scriptPubKey, so even if you allow arbitrary large OP_RETURN each byte still cost 4 weighted units, whereas the very same but pushed into the witness costs only 1 weighted unit.

Core knows this. They are compromised.