Loading...
This diabolical plan doesn't stop at the platforms. Starmer's plan also requires manufacturers like Apple and Google to build content-filtering software directly into devices sold in the UK, unlockable only by proving you're an adult, with fines and criminal liability for noncompliance. The state isn't regulating an app anymore, but is reaching into the hardware as well. As history has shown many times before, once that capability exists; the facial scans, the ID uploads, the device-level gates, it does not stay quietly confined to the original justification. Infrastructure built for one emergency is infrastructure available for the next, and the one after that.
That’s not to say genuine outliers don’t exist but if you really think about it, projects like WikiLeaks, Signal, or Bitcoin would never get funding from Silicon Valley VCs without significant compromise or redirection away from their original missions, which are very much antagonistic to those of the powers that be.
If the U.S. Treasury wants to expand its reserve to meet the "one million coin" target, but cannot spend tax dollars or print credit to buy them, the only remaining mechanism is to seize them. This turns federal law enforcement agencies (the DOJ, the IRS, and the FBI) into state-sanctioned bounty hunters. If the state needs pristine collateral to hedge against its own collapsing $39 trillion debt, it no longer has to mine it with energy. It can "mine" it by aggressively targeting the private keys of its own citizens under the guise of civil forfeiture.
The stablecoin is the company scrip of the surveillance state; accepted everywhere within the system, worthless outside it, and increasingly the only monetary form the system will permit. The warmth of collectivism, delivered through the infrastructure of control. This is the monetization of serfdom.
SpaceX is set to begin trading today, June 12, 2026, at a price that implies a $1.75 trillion valuation the largest IPO the stock market has ever seen. With a wave of other AI-adjacent companies expected to follow in the back half of the year, the valuations being thrown around have left me genuinely dizzy.
An example that immediately comes to mind would be Cathie Wood's ARK funds, which have collectively destroyed roughly $13 billion of investor capital while collecting close to $1 billion in fees , with $16 billion still under management, because the story is more compelling than the numbers. Carvana, despite well-documented and largely undisputed fraud , still carries an $80 billion market cap and has minted several new billionaires.
Most major industries and companies as we know them wouldn't exist in their current form without government subsidies, govt grants, the Federal Reserve's quantitative easing programs, and government contracts. We used to call heavy state involvement in industry socialism but apparently it's the in thing now. Layer the stock market on top of that, and you get a system that performs the appearance of decentralized capital allocation and genuine price discovery while functioning quite differently underneath.
Here's a thought experiment, if you held 10 Bitcoin and had the option to put it into this IPO, would you do it or would you hold the Bitcoin? Now ask yourself the same question about Anthropic or OpenAI when their turn comes. The opportunity cost is the same.
The cypherpunk premise is that freedom technology should keep working after any specific human walks away from it. That premise is easy to repeat and difficult to honor while you are shipping a product. Every shortcut that consolidates code, keys, infrastructure, or coordination authority into one team becomes a shortcut the adversary will follow back to its source. The state can route around your cryptography by routing through your operations team. The state has to find the room where your operators sit and convince those operators that continuing is more expensive than stopping. Most of the time it succeeds, because most of the time the room exists, the people are reachable, and the cost of stopping falls on users who have no seat at the table.
If White Noise stopped shipping tomorrow, the Marmot protocol would continue. Anyone could pick up the specifications and build a compatible client. MLS is a published cryptographic standard maintained by the IETF. Nostr transport is operated by hundreds of independent relays run by people I have never met. Sound cryptography sits in the IETF standards and decentralized transport runs across hundreds of relays, with open specifications anyone can read, and the messaging system stays resilient under pressure on any individual team or jurisdiction that decides private group messaging is too dangerous to permit. Work I do on White Noise is operational contribution to a system that runs without me, and that kind of work is the only kind in freedom technology that compounds over time.
The AI hype is a monetary story; it is a mechanism for directing printed capital toward politically approved sectors, for creating the illusion of productivity growth to justify continued debasement, and for offering retail investors the opportunity to serve as exit liquidity for the fourth or fifth time in a single generation.
The retail investor who participates is not entering a marketplace, but they are entering a casino in which the chips are denominated in a currency whose supply is controlled by the house. SpaceX at $1.75 trillion, OpenAI at $850 billion, Anthropic at $965 billion; are not prices discovered by the voluntary interaction of informed buyers and sellers assessing the discounted value of future productive output. They are prices produced by years of artificially suppressed interest rates, filtered through the concentrated capital of state-adjacent institutional investors, validated by the narrative requirements of a national security establishment with a strategic interest in AI supremacy, and finally presented to the retail public as investment opportunities.
SpaceX is being valued at approximately 94–107 times its trailing 2025 revenue. For context, Nvidia, the most important hardware company of the AI era, with dominant market share, exceptional margins, and proven profitability, trades at approximately 24 times sales. Apple, the world's most profitable consumer technology company, trades at roughly 8 times sales. SpaceX, at 94–107 times sales and reporting a $4.94 billion net loss, is being priced as though its future cash flows are not merely assured but extraordinarily large.
This system has a coherent foundation in economic theory. In a genuine free market, the interest rate, the price of time, emerges from the interaction of time preferences: savers who prefer future consumption to present consumption, balanced against entrepreneurs who can demonstrate that their productive plans will generate returns sufficient to compensate savers for their patience. The price of capital, thus set, carries real information about relative scarcity and productive opportunity. It guides investment toward genuinely valuable uses and disciplines speculation by making it costly.
This only works because three things line up. Nostr gives you an identity and an inbox that nobody can revoke. Bitcoin over Lightning lets you pay a dime instantly with no account, card, or middleman. And the AI does the research the second your sats land. No one piece carries it alone. Your npub is the login, the zap is the checkout, and the agent is the payoff, all inside one note. This is what these three were supposed to do together, and Jamie is the first bot to actually pull it off at this level.
You're mid-thread. Someone makes a claim. You know a podcaster covered this, you just can't place who, or when, or which of 400 episodes. Or you want the real read on a macro move or a news story, straight from people who actually study it. Not the loudest reply guy.
For years I helped build Wasabi Wallet. The work was good and the cryptography was sound. WabiSabi advanced Bitcoin privacy research in concrete ways and the wallet shipped on schedule, processing massive transaction volumes that made Bitcoin blockchain activity anonymous for everyone who used it. The chain analysis firms knew our name and they could see our outputs on every block and the math defeated them anyway. I am proud of what we built. I am also clear-eyed about what we built wrong, and what we built right turns out to be the part that is still alive today.
The error was architectural, and naming it precisely is the only honest place to begin. We built the client with care and shipped its source openly, and we wrote the WabiSabi paper and published the cryptography. The coordinator was where the discipline broke down. The wallet talked to one coordinator that our company ran, and for years that company was the only operator running one at meaningful scale. A WabiSabi paper sat openly on the internet alongside the published cryptography and the reference implementation under a permissive license, yet the operational layer remained a single team in a single jurisdiction. What we shipped was open-source software whose privacy guarantee terminated at machinery our company operated, and the machinery our company operated was where the adversary aimed.
For years I helped build Wasabi Wallet. The work was good and the cryptography was sound. WabiSabi advanced Bitcoin privacy research in concrete ways and the wallet shipped on schedule, processing massive transaction volumes that made Bitcoin blockchain activity anonymous for everyone who used it. The chain analysis firms knew our name and they could see our outputs on every block and the math defeated them anyway. I am proud of what we built. I am also clear-eyed about what we built wrong, and what we built right turns out to be the part that is still alive today.
For years I helped build Wasabi Wallet. The work was good and the cryptography was sound. WabiSabi advanced Bitcoin privacy research in concrete ways and the wallet shipped on schedule, processing massive transaction volumes that made Bitcoin blockchain activity anonymous for everyone who used it. The chain analysis firms knew our name and they could see our outputs on every block and the math defeated them anyway. I am proud of what we built. I am also clear-eyed about what we built wrong, and what we built right turns out to be the part that is still alive today.
For years I helped build Wasabi Wallet. The work was good and the cryptography was sound. WabiSabi advanced Bitcoin privacy research in concrete ways and the wallet shipped on schedule, processing massive transaction volumes that made Bitcoin blockchain activity anonymous for everyone who used it. The chain analysis firms knew our name and they could see our outputs on every block and the math defeated them anyway. I am proud of what we built. I am also clear-eyed about what we built wrong, and what we built right turns out to be the part that is still alive today.
The error was architectural, and naming it precisely is the only honest place to begin. We built the client with care and shipped its source openly, and we wrote the WabiSabi paper and published the cryptography. The coordinator was where the discipline broke down. The wallet talked to one coordinator that our company ran, and for years that company was the only operator running one at meaningful scale. A WabiSabi paper sat openly on the internet alongside the published cryptography and the reference implementation under a permissive license, yet the operational layer remained a single team in a single jurisdiction. What we shipped was open-source software whose privacy guarantee terminated at machinery our company operated, and the machinery our company operated was where the adversary aimed.
A more honest version of the protocol-first question is whether other teams could implement against our work at reasonable cost, and there the record is mixed. BTCPay Server and Trezor both built implementations that interoperated with our coordinator, which is more than nothing. The problem was that building those implementations was harder than it should have been and maintaining them was harder still, because the specification was thin in places where the reference implementation carried implicit knowledge and the protocol surface kept moving with our internal priorities. When zkSNACKs shut down, Trezor stopped offering the feature in their software and BTCPay stopped maintaining their implementation. Independent existence had been achieved on paper. Independent sustainability had not. The implementations existed because heroic engineers at heroic companies absorbed the cost of doing something the protocol made artificially expensive. Once the social gravity of our team disappeared, the calculation flipped and the implementations stopped.
What I have described is the shape of a single point of failure inside an otherwise open system. From the inside, while you are building, the shape stays invisible because the work is hard and shipping anything is an achievement and the next sprint is always about another feature in the wallet. The wallet feels like the product because the wallet is what users open. A coordinator runs quietly in a server room and most users barely think about it. Protocol specifications exist as documents in a folder. Day to day you iterate on the application while letting the operational layer stay where it has always been, and over time the company running that layer becomes the system in everyone's mind including your own. Architectural drift happens silently and the price gets paid years later.
The price arrived. Regulators noticed that one company ran one coordinator that mediated nearly all of the meaningful CoinJoin activity on the network. A small team of people in one jurisdiction had become the operational chokepoint for a privacy feature that the broader Bitcoin community depended on. When pressure landed on that team, the company shut the coordinator down and the privacy feature stopped working through that pathway. The client kept compiling, the WabiSabi paper kept being readable, and within days other operators picked up the protocol and ran their own coordinators. The wallet still connects to one coordinator at a time, but those coordinators now advertise themselves through Nostr events, so discovery has been pulled out of the company and into a decentralized lookup layer that anyone can publish to. Wallet sync has gone the same direction: balance and block filters now come straight from the Bitcoin peer-to-peer network, with no centrally operated sync server in the path. The empirical kicker is that volumes on community coordinators today exceed what our company ever processed at the height of our operation. The system that emerged from our absence is healthier than the system we used to run. Every part of the architecture that had been protocol-shaped survived because it was protocol-shaped. Only the layer that had been operator-monopolized died with the operator, and the death cleared the way for something better than what stood in its place.
The cypherpunk premise is that freedom technology should keep working after any specific human walks away from it. That premise is easy to repeat and difficult to honor while you are shipping a product. Every shortcut that consolidates code, keys, infrastructure, or coordination authority into one team becomes a shortcut the adversary will follow back to its source. The state can route around your cryptography by routing through your operations team. The state has to find the room where your operators sit and convince those operators that continuing is more expensive than stopping. Most of the time it succeeds, because most of the time the room exists, the people are reachable, and the cost of stopping falls on users who have no seat at the table.
What I learned, expensively, is that the order in which you do the work determines whether you survive the adversary's first serious move, and the cost at which other teams can implement determines whether the survival is real. Build the application first and the protocol decays into documentation that other teams glance at but never implement, while your library decays into a wrapper around your own internals. If you ship a protocol whose specification is thin and whose true behavior lives in the reference implementation, the third-party implementations will exist and then die, because no one will sustain the heroic effort of reading your source code and guessing at your conventions once your team stops being there to ask. Only when the protocol is documented thoroughly enough that another team can implement against the specification alone does the contract become cheap enough for other teams to build against it and keep building against it. The moment a second implementation exists at reasonable cost, you have a system the adversary can damage only by attacking every implementer at once, which is an attack budget most adversaries cannot sustain. Libraries belong second because libraries are how you make the protocol cheap for other developers to adopt, abstracting the hard parts of cryptography and networking and state management into interfaces application developers can use without becoming specialists in any of those domains. Applications belong third because applications are the surfaces that touch users, and surfaces should be plural. Many applications competing on user experience over a common protocol is what a healthy system looks like. One application acting as the on-ramp to a privately operated coordinator is what a target looks like.
This discipline inverts the order that feels natural while you are working. The natural order builds the application first because the application is what proves the idea while attracting the early users whose feedback shapes the next iteration. Protocol-first work writes the specification before there are users and refuses to ship features in the application that the specification cannot describe, accepting that few people will read the specification at the start. Libraries follow because the moment the specification is real, you owe other implementers the tools to build against it. The application arrives third because the application is the easiest part once the layers underneath are honest. Inverting the natural order is uncomfortable. The reward is that the system survives you.
Marmot is the application of this discipline to private group messaging. The Marmot Protocol specifies how to combine MLS, the IETF-standardized cryptographic protocol for secure groups, with Nostr as the transport. Six Marmot Implementation Proposals, MIP-00 through MIP-05, each define one layer of the system: how identity works, how groups form, how new members join, how messages travel, how media gets encrypted, and how push notifications reach mobile devices while keeping metadata away from Apple and Google. Four of those proposals are mandatory for any compatible implementation. Two are optional extensions. Each specification is public and versioned, with a public threat model alongside it. All of them were written before there were any users.
A library layer exists alongside the protocol, and after a relatively short development period the inventory is already substantial. The Marmot Development Kit is the Rust reference implementation, with native bindings published for Kotlin, Python, Ruby, Swift, and Web/WASM, so application developers can call into the protocol from whatever language and platform they target. Beyond the bindings, four genuinely independent implementations of the protocol have appeared: marmot-ts in TypeScript, marmot-cs in C#, Marmot support added to Quartz, the existing Kotlin Multiplatform Nostr library used by the Amethyst Android client, and the original MDK in Rust. Storage adapters for Sled and Redb sit alongside an LMDB option, giving implementers a choice in how they persist MLS state. Specialized tools have shown up around the edges, including a notifications server, a diagnostic tool for Nostr identities, a test harness for MLS proposal and commit scenarios, and several CLIs and bot frameworks built by people who have no formal relationship to the protocol authors. The list keeps growing because the specification is cheap enough to build against that contributors keep building.
White Noise occupies the application layer. White Noise is a chat client that uses the Marmot protocol through the MDK library to provide secure private messaging over Nostr. A Rust core crate powers a Flutter mobile app, and the Rust crate is itself frontend-agnostic, so command-line interfaces, desktop clients, and other applications can be built against the same core. What I care about is the Marmot protocol. White Noise is the application I am putting work into because someone has to build a reference client and I am positioned to help, and I would be perfectly content with a different Marmot client becoming the one people use most, as long as the protocol is what they end up using. The application matters to me only as a means by which the protocol reaches more people, and any other application that does that job is a friend doing work I want done. Around a dozen independent applications have already been built on Marmot by contributors with no formal relationship to the protocol authors, including a Flutter mobile app, a terminal UI client, a desktop helper that turns the protocol into a control surface for local AI agents, a peer-to-peer multiplayer game, a private family video sharing app, and several encrypted messengers built by independent teams. Amethyst, the major Android Nostr client with hundreds of thousands of installs, added Marmot support directly to Quartz, the existing Kotlin Multiplatform Nostr library that powers it, and ships interoperably with everything else on the network. Scramble built an equivalent Marmot implementation in C# on .NET from scratch. These two cases are the strongest possible evidence that the discipline is working as intended: independent teams reading the specification and shipping their own implementations that stay interoperable with the rest of the system without coordination from the protocol authors. The list spans hobby projects, agent infrastructure, niche specialized tools, and mainstream Nostr clients that already serve large user populations.
If White Noise stopped shipping tomorrow, the Marmot protocol would continue. Anyone could pick up the specifications and build a compatible client. MLS is a published cryptographic standard maintained by the IETF. Nostr transport is operated by hundreds of independent relays run by people I have never met. Sound cryptography sits in the IETF standards and decentralized transport runs across hundreds of relays, with open specifications anyone can read, and the messaging system stays resilient under pressure on any individual team or jurisdiction that decides private group messaging is too dangerous to permit. Work I do on White Noise is operational contribution to a system that runs without me, and that kind of work is the only kind in freedom technology that compounds over time.
Nostr itself is the standing proof that this strategy works. Its protocol is a small set of Nostr Implementation Possibilities, the original specification published by fiatjaf and extended by contributors he has never met in person. The protocol belongs to whoever implements it. Anyone can run a relay, anyone can build a client, and the network is the union of whatever those independent parties happen to have running at any given moment. Independent teams have built clients in different languages targeting different platforms with different design philosophies, and they all interoperate because the specifications are public, the events are signed, and the relays are dumb enough to be replaceable. When a relay operator gets pressured, the network routes around them. When a client team gives up or sells out or pivots to advertising, users move to another client and bring their identity and their social graph with them because both of those live in the protocol layer where they cannot be taken away. Protocol-first design is what makes Nostr resistant to the failure modes that killed every previous attempt at decentralized social media. Adversaries who break something break only locally. The network as a whole stays up because the network as a whole has no single point an attacker can break.
The contrast with the systems Nostr competes against is sharp and instructive. Federated social protocols whose identity model depends on the server you signed up with create a chokepoint at every server operator. Encrypted messaging platforms with one company running the infrastructure create a chokepoint at that company, and the chokepoint doubles when the same company is also the only place to get the application. Privacy-preserving wallets with one coordinator create a chokepoint at the coordinator. The pattern is consistent and the lesson is consistent. Real protocols paired with plural implementations and distributed operators produce a system that absorbs the loss of any participant while keeping the property that mattered. Drop any of those three conditions and the system acquires a kill switch, which an adversary will sooner or later reach for.
For anyone building freedom technology, the practical discipline reduces to a small set of habits that are easier to state than to follow. Write the specification first, even when it feels premature. Publish the threat model alongside the protocol so other implementers can reason about what you are claiming. Resist the temptation to ship features in your application that the specification cannot yet describe, because every such feature is a coupling that pulls users toward your application and away from the protocol. Make it easy for other teams to build against your work by writing libraries with stable interfaces alongside clear documentation that honestly acknowledges the parts still in motion. Treat your own application as one implementation among many, even when it is the only one that exists yet, because the day a second one ships is the day your work becomes durable. Invite people in. Answer their questions. Help them build the libraries you wish existed. The goal is to make the protocol cheaper to adopt than to ignore.
I write this with full awareness that Marmot has yet to prove anything. The protocol and the implementations are both still young, and the test that matters is whether the system survives the kind of pressure that broke the previous attempt. Whether we will pass that test remains open. I do know what the architecture has to look like for the test to be passable, and I know what the architecture looks like when the test is unpassable, because I built the unpassable version myself and watched it fail under intense, sustained regulatory pressure that found exactly the chokepoint our architecture had handed it. The lesson cost me years. I would rather it cost no one else the same.
The work I want to see is more protocols and more libraries and many more applications. The work I want to see less of is single-vendor stacks that look decentralized on the marketing page and have a phone number in the back room for a prosecutor to call. Freedom technology has always been a contest between architectures and adversaries, and the architectures that survive are the ones an adversary cannot find a person to call about. The order of operations is protocol first, library second, application third. That order produces systems that outlive their founders. The reverse order produces systems whose founders outlive the systems. I have written enough of the second kind to recommend that we all try to write more of the first.
A single dollar invested in Bitcoin in 2015, when it traded at approximately $300, would be worth roughly $303 by late 2025 at prices around $91,000, a 30,000% gain that included multiple drawdowns of 60–80% along the way, among them a 76.9% collapse in 2022. The S&P 500, the instrument into which most retail savings are directed through pension mandates, index funds, and the default investment architecture of the modern employment contract, delivered an average annualized return of 9.96% from 1928 to 2025, with inflation-adjusted returns falling to 6.69%. It does not sit in a chain of hypothecated claims in which your entitlement ranks behind derivative counterparties in the event of systemic failure. When you hold Bitcoin in self-custody, you have allodial title with zero counterparty risk. There is no Fed governor who can dilute your position by expanding the monetary base nor BlackRock proxy vote that overrides your economic interest.
The retail investor who buys SpaceX at $1.75 trillion, OpenAI at $850 billion, and Anthropic at $965 billion is not investing. They are basically making a prediction about the Federal Reserve's future willingness to maintain the monetary conditions that justify those valuations. In the event that they are right, they may earn nominal returns; but if they are wrong or the monetary policy shifts, as it often does, they will absorb the full brunt of the mean reversion. To be clear, this isn’t investment advice about encouraging or discouraging investment into these companies, but it’s an honest assessment of the mechanics and structure of modern capital markets and the incentives that drive them. These incentives and the structure are not designed to create a free market and thus the retail investor is screwed from the jump.
The result is a market that no longer allocates capital efficiently. It allocates capital according to the incentives created by monetary policy, which is another way of saying that, according to the political and institutional priorities of the central bank and its principal beneficiaries. Capital flows not to the most productive use of real resources but to the assets that benefit most from continued monetary expansion; long-duration growth stories with no near-term earnings requirement, entities with implicit government backing, and insiders positioned to extract liquidity from the public at valuations only achievable under conditions of artificially depressed discount rates.
For anyone building freedom technology, the practical discipline reduces to a small set of habits that are easier to state than to follow. Write the specification first, even when it feels premature. Publish the threat model alongside the protocol so other implementers can reason about what you are claiming. Resist the temptation to ship features in your application that the specification cannot yet describe, because every such feature is a coupling that pulls users toward your application and away from the protocol. Make it easy for other teams to build against your work by writing libraries with stable interfaces alongside clear documentation that honestly acknowledges the parts still in motion. Treat your own application as one implementation among many, even when it is the only one that exists yet, because the day a second one ships is the day your work becomes durable. Invite people in. Answer their questions. Help them build the libraries you wish existed. The goal is to make the protocol cheaper to adopt than to ignore.
For anyone building freedom technology, the practical discipline reduces to a small set of habits that are easier to state than to follow. Write the specification first, even when it feels premature. Publish the threat model alongside the protocol so other implementers can reason about what you are claiming. Resist the temptation to ship features in your application that the specification cannot yet describe, because every such feature is a coupling that pulls users toward your application and away from the protocol. Make it easy for other teams to build against your work by writing libraries with stable interfaces alongside clear documentation that honestly acknowledges the parts still in motion. Treat your own application as one implementation among many, even when it is the only one that exists yet, because the day a second one ships is the day your work becomes durable. Invite people in. Answer their questions. Help them build the libraries you wish existed. The goal is to make the protocol cheaper to adopt than to ignore.
For anyone building freedom technology, the practical discipline reduces to a small set of habits that are easier to state than to follow. Write the specification first, even when it feels premature. Publish the threat model alongside the protocol so other implementers can reason about what you are claiming. Resist the temptation to ship features in your application that the specification cannot yet describe, because every such feature is a coupling that pulls users toward your application and away from the protocol. Make it easy for other teams to build against your work by writing libraries with stable interfaces alongside clear documentation that honestly acknowledges the parts still in motion. Treat your own application as one implementation among many, even when it is the only one that exists yet, because the day a second one ships is the day your work becomes durable. Invite people in. Answer their questions. Help them build the libraries you wish existed. The goal is to make the protocol cheaper to adopt than to ignore.
For anyone building freedom technology, the practical discipline reduces to a small set of habits that are easier to state than to follow. Write the specification first, even when it feels premature. Publish the threat model alongside the protocol so other implementers can reason about what you are claiming. Resist the temptation to ship features in your application that the specification cannot yet describe, because every such feature is a coupling that pulls users toward your application and away from the protocol. Make it easy for other teams to build against your work by writing libraries with stable interfaces alongside clear documentation that honestly acknowledges the parts still in motion. Treat your own application as one implementation among many, even when it is the only one that exists yet, because the day a second one ships is the day your work becomes durable. Invite people in. Answer their questions. Help them build the libraries you wish existed. The goal is to make the protocol cheaper to adopt than to ignore.
This discipline inverts the order that feels natural while you are working. The natural order builds the application first because the application is what proves the idea while attracting the early users whose feedback shapes the next iteration. Protocol-first work writes the specification before there are users and refuses to ship features in the application that the specification cannot describe, accepting that few people will read the specification at the start. Libraries follow because the moment the specification is real, you owe other implementers the tools to build against it. The application arrives third because the application is the easiest part once the layers underneath are honest. Inverting the natural order is uncomfortable. The reward is that the system survives you.
This discipline inverts the order that feels natural while you are working. The natural order builds the application first because the application is what proves the idea while attracting the early users whose feedback shapes the next iteration. Protocol-first work writes the specification before there are users and refuses to ship features in the application that the specification cannot describe, accepting that few people will read the specification at the start. Libraries follow because the moment the specification is real, you owe other implementers the tools to build against it. The application arrives third because the application is the easiest part once the layers underneath are honest. Inverting the natural order is uncomfortable. The reward is that the system survives you.
This discipline inverts the order that feels natural while you are working. The natural order builds the application first because the application is what proves the idea while attracting the early users whose feedback shapes the next iteration. Protocol-first work writes the specification before there are users and refuses to ship features in the application that the specification cannot describe, accepting that few people will read the specification at the start. Libraries follow because the moment the specification is real, you owe other implementers the tools to build against it. The application arrives third because the application is the easiest part once the layers underneath are honest. Inverting the natural order is uncomfortable. The reward is that the system survives you.
This discipline inverts the order that feels natural while you are working. The natural order builds the application first because the application is what proves the idea while attracting the early users whose feedback shapes the next iteration. Protocol-first work writes the specification before there are users and refuses to ship features in the application that the specification cannot describe, accepting that few people will read the specification at the start. Libraries follow because the moment the specification is real, you owe other implementers the tools to build against it. The application arrives third because the application is the easiest part once the layers underneath are honest. Inverting the natural order is uncomfortable. The reward is that the system survives you.
What I learned, expensively, is that the order in which you do the work determines whether you survive the adversary's first serious move, and the cost at which other teams can implement determines whether the survival is real. Build the application first and the protocol decays into documentation that other teams glance at but never implement, while your library decays into a wrapper around your own internals. If you ship a protocol whose specification is thin and whose true behavior lives in the reference implementation, the third-party implementations will exist and then die, because no one will sustain the heroic effort of reading your source code and guessing at your conventions once your team stops being there to ask. Only when the protocol is documented thoroughly enough that another team can implement against the specification alone does the contract become cheap enough for other teams to build against it and keep building against it. The moment a second implementation exists at reasonable cost, you have a system the adversary can damage only by attacking every implementer at once, which is an attack budget most adversaries cannot sustain. Libraries belong second because libraries are how you make the protocol cheap for other developers to adopt, abstracting the hard parts of cryptography and networking and state management into interfaces application developers can use without becoming specialists in any of those domains. Applications belong third because applications are the surfaces that touch users, and surfaces should be plural. Many applications competing on user experience over a common protocol is what a healthy system looks like. One application acting as the on-ramp to a privately operated coordinator is what a target looks like.
Freedom technology has always been a contest between architectures and adversaries, and the architectures that survive are the ones an adversary cannot find a person to call about. The order of operations is protocol first, library second, application third. That order produces systems that outlive their founders.
S t u d ? d e r s
S t u d ? d e r s
de meilleurs portefeuilles,
Moreover, the expected value calculation for a solo miner is not purely monetary. The coins earned through solo mining arrive from coinbase, from the protocol itself, not from a KYC'd exchange, not from a compliant intermediary, and definitely not from a transaction that has been reported to any financial authority. In a world of Travel Rules, Chainalysis flags, FinCEN proposals, and exchange reporting mandates, that privacy premium is real and growing. Non-KYC coins are not just preferable but they are increasingly economically distinct. You are not merely buying a “lottery ticket” for $200,000. You are buying a “lottery ticket” for $200,000 in untraceable, self-sovereign sound money, earned by doing the work that secures the network.
Bitcoin home mining is the same BitTorrent architecture applied to money. Every home miner is a distributed defender of the monetary network. Every Bitaxe on a desk is a node in a resilient mesh that has no single point of failure and no single point of regulatory capture. For example a home alarm system protects one household at a time, but a distributed mining network protects the monetary infrastructure of a civilization. When we talk about Bitcoin storing and transmitting trillions of dollars in value, the security architecture is not optional. It is essential, but unfortunately right now, that architecture is dangerously centralized.
Ludwig von Mises’ regression theorem holds that money's value traces back to its earlier commodity use, that monetary goods carry a lineage of exchange. Apply this to Bitcoin and a striking distinction emerges: mined coins and purchased coins are not the same monetary good.
When hashrate is distributed across ten million home miners, the adversary has ten million targets. There is no phone call that reaches them all and no single regulator has the budget or the jurisdictional authority or capacity to take them down. The network becomes, in the truest sense, resistant. Just as sound money emerges from voluntary exchange and real work rather than central bank decree, a sound monetary network emerges from voluntary, distributed participation rather than corporate delegation. Friedrich Hayek's insight about the impossibility of central planning, that no single entity can aggregate the dispersed knowledge of millions of individual actors, applies with equal force to mining. No corporation can replicate the resilience that emerges from millions of individual decisions to plug in a miner.
Jason Lowrey's 2023 MIT thesis, Softwar, reframes Bitcoin’s proof of work (PoW) algorithm in a fundamentally different way. His core insight is that proof-of-work is not merely a consensus mechanism but it is a form of electro-cyber power projection, a way for individuals and institutions to project real-world power into the digital domain by burning physical energy. In Lowrey's framework, Bitcoin mining is structurally analogous to bearing arms or fortifying a home: it is the digital equivalent of the individual's capacity for self-defense.
Bitcoin makes these arrangements concrete. A two-of-three multisignature setup can split keys between buyer and seller, with a third key held by an arbiter. If the trade finishes smoothly, buyer and seller release the funds together. If trouble arises, the arbiter joins one side and the funds move with two signatures. No one person has unilateral control. That is already a better structure than the ordinary platform model where a company takes the money and writes the rules.^14^
Puzzle: MTktMS0yMC0xNS0xOS04LTktLy0xOS05LTctMTQtMS0xMg==
Solo mining, whether via home hardware or rented hashpower pointed at your own address, is one of the few remaining ways to acquire Bitcoin that is architecturally resistant to the surveillance infrastructure being built around it. Not because it is hidden or illegal, but because it operates at the protocol layer, below the compliance layer that regulators are constructing.
When individual actors rationally delegate security to large institutions, the equilibrium is captured and corrupted. The only stable decentralised equilibrium requires that individual participation be accessible, affordable, and actively chosen. Your marginal hash makes the network marginally more resilient. That resilience is a public good that benefits every Bitcoin holder.
The Attention Economy Is Working Against Bitcoin The mainstream media’s relationship with Bitcoin is predictable: bear versus bull, price rising versus price crashing.
Within the Bitcoin community itself, the narratives are still polemic: KYC versus non-KYC, Core versus Knots. These framings are engineered for attention. Content on these topics generates a brief spike of outrage or excitement, then the audience clicks away, and the cycle resets.
Polarity doesn’t encourage deep thought or nuanced discussion.
Because Bitcoin has no founder in the traditional sense, no Steve Jobs or Sam Altman for journalists to profile, traditional media fills the gap with criticism: Trump’s shitcoinery, lost wallets in a landfill, scams, and seizures. Any story with a human face attached to failure travels far.
Within the industry, the counter-narrative is more positive but totally faceless. Institutional adoption, policy developments, and new technologies — these are stories that attract systems thinkers, engineers, and developers. People with a GitHub account or a toolbox in the garage. That is the demographic that already knows about Bitcoin. The 95% who are not yet in the space do not think this way, and headlines aimed at systems thinkers simply do not reach them.
They can manipulate price volatility, but they cannot manipulate the long-term secular trend due to the impossibility of inflating the supply of Bitcoin.
Amidst the noise of charts and market chaos, there is an untouchable technical reality where the power of manipulators is reduced to zero: they cannot stop the heartbeat of the protocol.
<img src="
Unfortunately, the country has moved beyond its illustrious history of a global empire and even beyond the remnants of where the promise of future economic growth could offset the ever-increasing pile of national debt. Where the UK is now requires more severe action, (or a productivity miracle, if the politicians could imagine and support such a thing), so the idea of not simply taxing the billionaires but taxing anything that moves (weirdly similar to a recently unearthed Peter Mandelsson comment) may plug the immediate hole in public finances, but will ultimately destroy the nation.
In the name of Jesus I pledge allegiance to the Legion of Life, Love and Freedom In the name of Jesus thy kingdom I am seeking In the name of Jesus my life’s been given meaning In the name of Jesus I’m grateful to be breathin’ In the name of Jesus I suffer through the seasons In the name of Jesus I’m finding rhyme and reason In the name of Jesus I’m thankful for my beatings In the name of Jesus I’m praying for your healing In the name of Jesus I bless the poor and needy In the name of Jesus you can use my gifts freely In the name of Jesus I know my wife will feel me In the name of Jesus I always keep it real G In the name of Jesus I banish all the evil In the name of Jesus I’m rebuking all the demons In the name of Jesus I’m laying down my pieces In the name of Jesus you all my cousins, nieces In the name of Jesus I’m straightening the creases In the name of Jesus I go to mountains, beaches In the name of Jesus I practice what He preaches In the name of Jesus we all are God’s creatures In the name of Jesus all with different features In the name of Jesus take heed of what He teaches In the name of Jesus love thy neighbor dearly In the name of Jesus resentment will not fill me In the name of Jesus your bullets shall not kill me In the name of Jesus God has made me willing In the name of Jesus I’m feeling all these feelings In the name of Jesus whole inspiration in me In the name of Jesus love is what I’m bleeding In the name of Jesus God is who we’re meeting In the name of Jesus, my brother, till you meet us. Amen.
Identity that resists transfer also resists theft-and-resale. The same property cuts in both directions. The keyholder stays the keyholder, until they either lose the key or hand it to enough people that the signature stops meaning anything specific. Both of those outcomes degrade the identity without transferring it. The protocol carries no rule against selling accounts. The math already refuses.
Look at the systems where account sales function smoothly. A Twitter handle changes hands through the platform's authentication system: the seller hands over login credentials, the buyer rotates the password and recovery email, and Twitter henceforth treats the buyer as the account. The platform is the source of truth. An Instagram account sale works the same way, with the added wrinkle that Meta will sometimes reclaim handles it considers stolen, which buyers price in as risk. A domain name transfers through the registrar updating records that the entire DNS system treats as authoritative. Each of those sales is enforceable because a third party with operational control of the namespace can lock the previous owner out.
Every other social platform hosts a thriving black market for aged accounts with established reputations. Nostr stays empty of one, and the reason traces to the cryptographic shape of the system. Policy and enforcement have nothing to do with it. The original holder of an nsec keeps the option to reappear forever, and any buyer who tries to price around that option arrives at a number too low to interest the seller.
When Satoshi described eliminating trusted third parties, the target was financial intermediaries: banks, payment processors, governments with monetary authority. A trusted third party is any entity whose behaviour you must rely on but cannot verify or constrain. Bitcoin eliminates financial trusted third parties through cryptographic proof and distributed consensus, but the smartphone you use to access Bitcoin is itself governed by trusted third parties:
The implications for Bitcoin users are direct. If your device is a surveillance instrument, then your Bitcoin wallet, including its keys, its balances, its transaction patterns, its Lightning payment history, operates inside a surveillance instrument. The cryptographic integrity of your keys is intact, while the operational security of how you use them is not.
The most consequential threat on the horizon is not app-level censorship. It is identity verification baked directly into the operating system, in other words KYC at the device level, enforced before any app can be installed or used.
For Bitcoiners, the trajectory points to a world in which running a Bitcoin wallet on a mainstream smartphone requires first authenticating your identity to Google or Apple, who relay that information to the wallet developer, who is then legally required to apply KYC procedures before allowing the app to function. Pseudonymous Bitcoin use on a mainstream OS becomes technically impossible not because of any flaw in Bitcoin's protocol, but because the device enforces identity before the protocol can be accessed.
While you may run your own node, hold your own keys; you do all of it on a device that reports your location to Google every few minutes, routes your app installations through a duopoly that has demonstrated willingness to remove Bitcoin wallets under regulatory pressure, and is architecturally incapable of resisting an OS-level identity mandate when one arrives, as one now demonstrably is.
We see individuals on the ground as the key economic unit of transformation.
If you are smarter than the regulator and you are not afraid of the system, you are—for all practical purposes—free.
Even the Lightning Network, while significantly more private than on-chain movements, leaves traces in the form of channel balances and routing nodes. Protocols like Cashu driven by the tireless work of Calle and Fedimints driven by the likes of Fedi, have resurrected Chaum’s vision to provide a much-needed privacy layer.
Even the Lightning Network, while significantly more private than on-chain movements, leaves traces in the form of channel balances and routing nodes. Protocols like Cashu driven by the tireless work of Calle and Fedimints driven by the likes of Fedi, have resurrected Chaum’s vision to provide a much-needed privacy layer.
