The email arrived on a Tuesday — the kind of gray, humid Tuesday that Hong Kong does in late winter, when the air has not yet decided whether it wants to commit to being cold. A junior developer I had mentored back in the Resilience Hub days forwarded me a news brief with a single line of commentary above it: "Is this guy serious?"
I read it twice. A co-founder of Opera — the Norwegian browser company that has, for the better part of a decade, shipped a built-in cryptocurrency wallet to tens of millions of users — had said, in public, that crypto should have been banned. Not regulated. Not slowed. Not ring-fenced with disclosure requirements and capital rules. Banned. And then, in the same breath, the accusation: crypto companies are flush with cash, and they are using that cash to influence politicians.
In a bull market, a line like that gets laughed off as a hot take. In a bear market — which is where we are, and have been for longer than most of the people who joined in the last cycle would like to admit — a line like that does something else. It lands. It finds the soft tissue. Because in a bear market, everyone is already asking the question the founder only implied: is this thing actually legitimate, or have we been buying permission we did not earn?
That is the question I want to sit with, carefully, for the length of this piece. Not the shouting version of it. The technical version. The version that a cryptographer who has spent twenty-nine years watching this industry build and break and rebuild itself is allowed to ask.
Because here is what struck me first, and what I have not been able to put down since: the news brief that carried the quote contained no technical content at all. No protocol upgrade. No token model. No on-chain data. No specific company named beyond the speaker's own affiliation. One man, one sentence, one unverified financial accusation. That is the entire payload.
And yet the payload is heavy. Which tells us the weight is not in the information. The weight is in the narrative.
The Man, the Browser, and the Wallet He Shipped
Before I analyze the accusation, I need to describe the accuser's position honestly, because the position matters more than the person. Opera is not a fringe player. It is a browser with a user base measured in the hundreds of millions, strongest in mobile-first markets across Africa, Southeast Asia, and parts of Europe. It is also — and this is the fact that makes the quote so strange — one of the earliest and most aggressive traditional-technology companies to integrate cryptocurrency functionality directly into its consumer product. A built-in wallet. A Web3 identity layer. Staking, swaps, and dApp access, all framed as a browser feature, not a financial product.
So the man who said crypto should have been banned is a co-founder of a company whose consumer surface is, in part, a crypto on-ramp. That is the paradox. And the fact that the media chose to identify him as an "Opera co-founder" and a "tech executive" — rather than as a named individual with a specific current role, or a current relationship to the company — tells you something about the fragility of the attribution itself. Founders leave. Founders found other things. Founders disagree with what their former companies become. But the label sticks, and the label is what gives the quote its reach.
I grew up professionally in a world where labels were everything — cryptographic credentials, protocol titles, the difference between a signature and a ciphertext. So I notice when a label is doing more work than the substance underneath it. Here, the substance is thin: one assertion and one insinuation. The label — "Opera co-founder, and Opera is a crypto company" — is doing the heavy lifting of making the assertion sound like an insider's confession rather than an outsider's opinion.
And that is precisely why it should be taken seriously and read skeptically at the same time. Historically, the things most worth reading are the things that arrive dressed in borrowed authority.
What Regulatory Capture Actually Means, and Why It Is a Bigger Word Than 'Bribery'
Here is the accusation, translated out of emotional language and into structural language. Crypto companies have accumulated large capital reserves — "flush with cash" — and they have directed some portion of those reserves, directly or through political action committees, toward elected officials and candidates. The implication: favorable policy — spot ETF approvals, softened enforcement, clearer statutory treatment — may not reflect the merits of the industry, but rather the weight of its spending. In the vocabulary of political economy, this is not bribery. It is something broader and, in some ways, harder to prosecute: regulatory capture.
Regulatory capture is the process by which an institution meant to regulate an industry comes to advance the interests of that industry instead of the public interest. The classic examples are not crypto. They are agriculture boards staffed by agribusiness, securities regulators staffed by former investment bankers, and telecom authorities staffed by the companies whose rates they set. Capture is rarely a single envelope under a table. It is a slow osmosis — a revolving door of personnel, a shared set of assumptions, a funding stream that flows one way, a lobby whose clients happen to be the only people with the technical expertise to advise the regulator on the thing they are regulated for.
That last clause is the one most relevant to us. Crypto is genuinely hard to regulate without crypto expertise. And the people with crypto expertise are, overwhelmingly, people who work in crypto. Which means that any regulator attempting to get smart quickly has two choices: hire former industry people, or remain ignorant. That structural asymmetry — the epistemic dependence of the regulator on the regulated — is what makes the perception of capture so durable even when no cash changes hands in a way a court could call improper.
I want to be precise about the claim the Opera founder is making, because precision here is a form of fairness. He is not, in the brief as it reaches me, alleging a specific illegal payment. He is alleging a general condition: that money, and therefore influence, has accumulated on one side, and that the resulting policy is therefore suspect. That is a legitimate thing to allege in a democracy. It is also a thing that can be alleged without evidence, which is exactly why an allegation of this shape should be met not with outrage but with analysis. If we cannot distinguish between the claim and the evidence, we have already surrendered the argument.
So let me do the analysis. And I want to begin with the most basic technical reality, because it is the one the founder's framing erases: the word "crypto" is not one thing. It never was. And the fact that the accusation treats it as one thing is the tell that tells us what kind of argument this is.
The Bannability Problem: You Cannot Ban What Has No Head
In 2017, I co-founded an advisory platform we called TrustChain, built on a single premise: that the chaos of the ICO era was a failure of education, not of cryptography. I delivered forty live sessions to more than five thousand participants, and the lesson I most often had to teach first was the least technical: that a token issued by a company was not the same thing, in any meaningful sense, as a decentralized network's native asset, even though both wore the label "crypto." One could be stopped by subpoena. The other could not be stopped by army. That distinction was the first thing I taught, and it is the first thing the Opera quote dissolves.
So let me reconstruct the distinction here, carefully, because everything downstream depends on it.
At the base is the consensus layer — the network of nodes that agree, by cryptographic rule, on what happened. Bitcoin and Ethereum live here. You cannot, in any operationally meaningful sense, ban them from a jurisdiction. A state can prevent its citizens from using them, can prevent companies within its borders from servicing them, can criminalize the act of running a node. What it cannot do is switch them off, because there is no switch. There is no head to find, no board to subpoena, no headquarters to raid. The only thing a jurisdiction can do is regulate the humans who choose to interact with the network inside its borders. The network itself is indifferent to borders, because borders are a social construct and hashes are not.
One layer up is the application layer — the smart contracts, the DeFi protocols, the on-chain organizations. These are stranger entities. The contracts execute regardless of who wants them to stop, but they usually have front-ends, domains, teams, and token treasuries — human appendages that can be targeted. A protocol can be "banned" in the sense that its website can be seized, its domain deregistered, its developers threatened, its liquidity providers pressured. The code survives; the experience of using it becomes materially harder.
At the top is the access layer — the exchanges, the custodians, the wallets, the fiat on-ramps, the app stores that decide whether this software is even installable. This layer is entirely bannable. Not partially. Entirely. A jurisdiction that wanted to could make it illegal to operate a licensed exchange within its borders tomorrow, and the effect would be immediate and total for the users who depend on that exchange.
Now hold that three-part structure against the sentence "we should have banned crypto," and watch what it does. The sentence is coherent only as a statement about the top layer. It is incoherent as a statement about the bottom layer, because you cannot have-banned what has no central authority to have-banned it. The founder has, perhaps without intending to, collapsed a multi-layered technical reality into a single word. And that collapse is not neutral. It is the move that makes an impossible proposition sound like a commonsense one.
This matters because it determines what any real policy can actually do. If you want to make crypto unavailable to your citizens, you regulate the access layer — exchanges, custodians, ramps, app stores — and you accept that a determined minority will route around you through peer-to-peer channels, foreign exchanges, and self-custody. If you want to clean up crypto without killing it, you regulate the intermediaries heavily and leave the base protocol alone, because the base protocol cannot be regulated anyway. And if you want to say "we should have banned crypto," you are not describing policy. You are describing a wish, dressed as a plan, about a thing that only exists as one thing in the imagination of people who do not work on the layers.
Code is law, but people are the protocol. And people can be corralled. Protocols cannot. The mistake of conflating the two is not a technical nitpick. It is the single most common error in the entire public discourse about this industry, and it lands us — as it landed the founder — in a place where responsibility is assigned to a substrate that has no capacity to bear it.
The Monolith Fallacy and the Birth of a Straw Man
Once you have collapsed "crypto" into one thing, everything that follows writes itself. If crypto is one thing, then the person accusing crypto of buying politicians does not have to name a buyer, a seller, or a price. He does not have to distinguish between a Bitcoin miner, a stablecoin issuer, a DeFi protocol with a treasury, and a centralized exchange with a compliance department. They are all "crypto companies" now, all "flush with cash," all in the same room with the same envelope.
The origin of this fallacy is not merely rhetorical laziness. It is a genuine feature of how the industry has presented itself. — Root: DeFi Summer. In 2020, when I led a volunteer team of fifteen developers to audit early Uniswap governance mechanics, we published a fifty-page paper titled "Democratizing Liquidity," and it was downloaded ten thousand times in a month. The paper was about a specific protocol's specific governance. But the way it was marketed, by the wider industry, was as proof of a general claim: that "DeFi" — a single capitalized noun — was arriving to save "finance," another single capitalized noun. We sold the industry as a monolith because a monolith is easier to sell. And now the monolith is being used to indict us.
That is the irony of the accusation. The industry spent years constructing a unified brand and is now being judged by it. When a browser founder says "crypto companies influence politicians," he is speaking a language the industry taught him. The same generalized vocabulary that made "DeFi" a household word now makes "crypto" a single, bannable, cash-rich entity. If you build a monolith, you should not be surprised when someone arrives with a hammer.
But note what is lost when the monolith is invoked. Bitcoin has no company. The Bitcoin network cannot be flush with cash because it has no treasury — it has miners, whose revenue collapsed this cycle as the hashprice compressed and fee markets failed to fill the gap left by the halving. The Bitcoin ecosystem's political activity, insofar as it exists, is a fraction of the volume attributed to it. Meanwhile, the entities that genuinely do have concentrated cash and concentrated political voice are the exchanges, the stablecoin issuers, the venture funds, and — increasingly — the foundations governing large token protocols. Those are not the same organizations. They have not the same interests, and in bear markets they are actively in conflict, because liquidity is finite and every dollar one of them extracts is a dollar another does not get.
So the first analytical correction to the Opera quote is this: the thing he named is not the thing he described. He described political spending by a specific class of capital-rich intermediaries. He named a technology. The gap between them is where the entire debate goes wrong — and where the legitimacy of the industry is now being litigated.
Follow the Money, But Name It: The Three Origins of 'Flush With Cash'
The most interesting phrase in the whole brief is the least examined: "flush with cash." It is doing a lot of work. It is the bridge between the technical claim (crypto is bad) and the political claim (crypto bought policy). And it is vague in a way that should be unacceptable to anyone who has sat through a token unlock schedule.
Because there are three places this cash can come from, and every one of them points at a different villain.
The first is token issuance. A protocol issues a token, sells it to retail through a public sale or an airdrop, and voilà — there is a treasury. The capital here is ultimately provided by retail buyers, many of whom are underwater in the current market. If the political spending of the industry is funded this way, then the accurate statement is not "crypto companies influence politicians." It is "retail token buyers are paying for political influence they arguably did not authorize." That is a much sharper and much more uncomfortable sentence, and it moves the criticism from the industry to the relationship between the industry and the people it claims to represent.
The second is venture financing. Funds raise capital from limited partners, deploy it into protocols and companies, and take governance influence as part of the deal. This is not unique to crypto — it is how all venture-backed industries buy policy access — but it has a specific crypto texture, because in token networks the venture funding often converts directly into governing power through large token allocations. Here the political spending is institutional, disciplined, and long-horizon. The villain is the standard revolving-door dynamic between capital and the state, and crypto is merely the newest entrant to the club.
The third is real product revenue — exchanges charging fees, stablecoin issuers earning float, infrastructure providers selling services. This is the cleanest money, and it is the smallest in most bear-market balance sheets, because the bear market has compressed volumes, spread the float thin, and squeezed the consulting budgets.
Now, notice what happens to the accusation when you force it to pick one of these. "Flush with cash" becomes either a complaint about retail being exploited, a complaint about venture capital doing what venture capital does, or a complaint about businesses that actually sell product. The Opera founder almost certainly meant the second, because that is the version that fits the standard political-narrative frame. But the industry would be foolish to let the accusation float in its vague form, because the vague form is the most damaging. Precision is our defense. If the accusation is about VC money, then let us talk about VC money, and it becomes a story about capital and the state in which crypto is not uniquely guilty. If the accusation is about retail-funded treasuries, then we have a genuine internal problem and should be the first to admit it.
The fact that the brief does not specify is not an oversight. Vagueness is the load-bearing wall of the accusation. Take it away and the structure falls.
The Opera Paradox: When the Gatekeeper Turns On the Gate
There is a second thing the brief does not say, and it is the thing I keep returning to. Opera, as a company, is not merely adjacent to crypto. It is a beneficiary of crypto adoption. Its wallet integrations exist because there are users who want to hold and move digital assets inside a browser. Its differentiation against Chrome and Safari is, in part, that it does something with Web3 that the incumbents do not. So when a co-founder of that company says crypto should have been banned, he is not merely expressing a policy preference. He is, whether he intends it or not, speaking against the commercial logic of the surface he helped create.
I do not mean this as gotcha. Founders are not their companies, and a founder criticizing the industry his company monetizes is not hypocrisy — it is, potentially, integrity. If I believed something was harmful, I would want to say so even if it cost me. That is a value I hold hard.
But it is analytically relevant for a reason that has nothing to do with the individual. It tells us where the friction actually is. The browser is the gateway between Web2 and Web3. It is the most contested piece of real estate in the transition, because whoever owns the default entry point owns the user relationship. And there is a genuine strategic conflict between the model in which the browser is a neutral viewport and the model in which the browser is a wallet, an identity, and a storefront. The first model preserves the browser's traditional role. The second threatens to subordinate it to the crypto rails it now sits on top of.
When a founder from the first model speaks against crypto, I hear — behind the policy language — the anxiety of an incumbent whose position is being redefined by technology he did not choose. That is not a disqualification of his argument. It is a context for it. And context is what the news brief, with its anonymous "Opera co-founder" label, carefully strips away.
This is not the first time. — Root: The 2022 Bear Market. When the market collapsed and the layoffs cascaded, I watched the same dynamic play out across traditional tech: executives who had spent two years hyping their crypto exposure quietly deleting it from their decks, and then, once the noise settled, discovering philosophical objections to the industry they had just been promoting. I do not think most of them were lying. I think most of them were calibrating. And calibration, when it happens at scale, produces exactly the kind of ambient anti-crypto sentiment that a single quote can crystallize.
Delegation and the Concentration of Voice: Why 'The Industry' Even Has a Lobby
Here is the part of the story that I think the Opera founder got accidentally, structurally right, and that the industry hates to hear.
The accusation presumes that crypto has a coherent voice capable of influencing policy. For that presumption to hold, the industry must be able to speak with something resembling one voice, or at least a coordinated chorus. And here we have to be honest about where that coordination comes from. It does not come from the grassroots. It comes from delegation.
I have spent years watching governance systems in decentralized organizations, and the pattern is remarkably stable. Voters do not research proposals. Voters delegate. And delegated voting power concentrates. In any network large enough to matter, a small number of delegates — usually funds, founders, and prominent commentators — end up controlling a supermajority of governance weight, because delegating is cheap and researching is expensive. The result is that a network that describes itself as decentralized can end up with a de facto board of ten to twenty well-funded voices making the decisions that touch policy, treasury deployment, and public positioning.
Governance isn't the opposite of hierarchy. It is hierarchy that has been laundered through token mechanics. And when that concentrated voice speaks to a regulator or funds a political committee, it speaks with the authority of a whole network — an authority it earned through delegation rather than through election or organic consensus.
This is the mechanism the Opera founder is pointing at without understanding it. "Crypto companies" do not influence politicians because crypto is one company. They influence politicians because crypto's governance systems — precisely the ones we built to avoid hierarchy — have quietly reconstituted hierarchy at the very top, and that hierarchy is efficient at exactly the thing hierarchies are efficient at: pooling capital and directing it at power.
I do not enjoy writing that sentence. I spent a DeFi Summer believing that on-chain governance was a genuine institutional innovation — that it might let a global, anonymous, dispersed community make collective decisions without the pathologies of representative democracy. What I have learned since is that delegation reproduces the pathologies faster than it innovates past them, because it optimizes for convenience, and convenience is the enemy of participation, and participation is the only thing that keeps a governance system from becoming an oligarchy with a token wrapper.
So when the accusation is made that the industry buys policy, the honest response is not to deny it. It is to ask which part of the industry, and to admit that the part with the money is not the part with the users.
Technical Resilience Is Not the Resilience We Need
Let me now say the thing that I think will annoy both the founder's defenders and his critics, and that I think is the actual insight of this whole episode.
The crypto industry has spent a decade building technical resilience. Redundant nodes. Multiple data availability layers. Modular stacks. Rollups on top of rollups. Cross-chain bridges. Formal verification. The entire architecture of the ecosystem has been designed around the assumption that the threat is failure — of a server, of a validator, of a chain, of a bridge. And we have gotten good at that. A modern L2 can survive the failure of its sequencer, the failure of its data availability provider, and, in the best designs, the failure of its governance. The system routes around damage.
But look at what the Opera quote threatens, and notice that none of our resilience engineering touches it. The threat is not that a chain stops. The threat is that the industry loses the legitimacy to exist within the legal systems it depends on for on-ramps, banking, and users. Legitimacy is not a property that any data availability layer can provide. It is not something a rollup can route around. It is a social and political property, and it is held in a completely different kind of ledger — the ledger of public trust.
Here is where I have to be disciplined about my own hobby horses, because I have argued for years that the obsession with dedicated data availability layers is disproportionate to actual demand — that the vast majority of rollups do not generate enough data to need bespoke DA at all, and that the industry's DA arms race is more about narrative differentiation than about real constraints. That argument, whatever its technical merits, is a perfect illustration of the larger problem. We have built elaborate machinery for resilience against the threats we find interesting, and left ourselves wide open to the threats we find boring. A founder of a browser can say "we should have banned crypto" in a public forum and do more damage to the industry's productive capacity than a hundred failed rollups, because the damage is not to a chain. It is to the assumption that crypto deserves to be treated as infrastructure rather than as a casino with better math.
The DeFi Summer taught me that composability is leverage. The 2022 Bear Market taught me that leverage cuts both ways. What this episode is teaching me is that there is a third kind of leverage we have barely begun to model: political legitimacy. It compounds quietly in the good times and it evaporates instantly in the bad ones, and it is now, arguably, the scarcest resource in the entire ecosystem.
The bear market removes the price signal that used to distract us from this. Which is why this quote matters more now than it would have in 2021. In 2021, the industry could afford to ignore its critics because the numbers were going up. In a bear market, the numbers are not going up, and the only thing left to argue about is whether the industry deserves its seat at the table.
What the Industry Should Actually Do With the Accusation
I want to move from diagnosis to prescription, because analysis that stops at diagnosis is a luxury this moment does not permit.
First, the industry must do the one thing it has historically been worst at: name itself precisely. The response to "we should have banned crypto" is not to defend crypto — it is to point out that the category does not exist. There is no crypto. There are protocols, and there are companies, and the two answer to entirely different authorities — the protocol to its users and its code, the company to its regulators and its shareholders. When a critic conflates them, the industry's first move should be to disaggregate the claim on the record, in plain language, for the public that does not live inside our jargon. Every day we allow the monolith to stand, we make the founder's argument easier.
Second, the industry must treat legitimacy as a first-class engineering problem — not a communications problem. Communications is what you do when you have something to hide. Legitimacy engineering is what you do when you have something to prove. It means structuring treasury and governance so that influence over policy cannot be purchased with retail money. It means publishing, voluntarily, the kind of disclosure that regulators currently have to fight for. It means — and I know how this sounds — accepting a slower path to adoption in exchange for a durable one. I spent the 2024 ETF cycle arguing in Hong Kong, in front of three hundred policymakers and educators, that regulation enhances rather than hinders decentralization, that "responsibility within freedom" is not a slogan but a design constraint. I still believe it. And I believe it because the alternative is the world the Opera founder described, where the industry's permission is purchased and therefore revocable the moment the political winds shift.
Third, and hardest, the industry must fix the mechanism that made the accusation plausible in the first place. Delegation concentrates voice. Concentrated voice buys policy. If we do not want the industry's political posture to be set by a dozen well-funded delegates, we have to make the cost of delegation honesty — we have to make the public costs of drift visible, and we have to reward the boring, unglamorous work of actually voting on the proposals that matter instead of farming airdrops and checking out.
The Contrarian Angle: The Real Danger Is Not the Ban
Now let me offer the reading that runs against both sides, because both sides are, in my view, overestimating the wrong thing.
The founder's defenders will frame this as a warning: the industry is vulnerable to being shut down. His critics will frame it as a gaffe: an impossible proposal from a confused executive. I think both miss the actual risk.
The actual risk is not that crypto gets banned. It will not. The base layer is unbannable, as we established, and the access layer is too economically integrated into too many jurisdictions to be shut without a global, coordinated, sustained act of political will that has never once materialized for any technology in the modern era and is unlikely to start now. The genuine risk is subtler and, in the long run, more corrosive: that the industry's legitimacy erodes so slowly that no single moment feels like a turning point, and that the erosion is funded by the industry's own money. The accusation is not dangerous because it is true. It is dangerous because it is plausible — and plausibility, once established, does not require proof to do its work.
This is the inversion I want the reader to sit with. The person who says "we should have banned crypto" is not the threat. The threat is the person who says "of course crypto bought its policy, everyone knows that" — and then keeps their opinion to themselves, and votes accordingly. A ban is a fight, and fights are survivable. A quiet, dispassionate, widely held belief that the industry does not deserve its status is not a fight at all. It is weather. And you cannot litigate weather.
Here is the second contrarian note, and it cuts against my own side. The industry loves to say it has matured, that it has grown up, that it is now a serious sector of the economy. If that is true, then it must accept the burden of legitimation that every serious sector carries. Finance, pharma, aviation, nuclear power — these industries do not merely operate. They continuously justify their existence to the public that permits them, and they pay, in disclosure and constraint and occasional humiliation, for that permission. Crypto has so far wanted the privileges of a serious industry without the obligations. The Opera quote is a repudiation of that bargain, and it is delivered, inconveniently, from inside the house. If the industry wants to be treated as infrastructure, it has to do the thing infrastructure does: submit to public scrutiny without pretending that scrutiny is an attack.
Takeaway: Legitimacy Is the Only Layer That Cannot Be Rolled Up
The founder's mistake was temporal. He spoke of an industry as if its fate were already sealed, as if a ban were a thing that had been missed rather than a thing that could never have been. But there is a deeper reading available, and it is the one I will leave with.
Every layer of this technology was built to be resilient — to survive the failure of any node, any validator, any chain, any company. We were right to build that. We were wrong to think it was enough. There is a layer beneath all the others, and it is made neither of hashes nor of nodes. It is made of permission, and permission is granted by people, and people are the protocol.
Code is law, but people are the protocol. I have said that for years and meant it as a statement about governance. This episode has moved it into a larger frame. It is not just that people govern the protocols. It is that people, acting through states and publics and shared assumptions, govern the very possibility that the protocols will be allowed to exist in the world. The unbannable network still needs permission to meet the people. And permission is the one thing a hash cannot secure.
The industry's next project — the one worth more than all the data availability layers ever funded — is the patient, unglamorous, deeply human work of earning that permission back. Not by pretending we were never at fault. By building, in public, a record that speaks for itself.
Because in the end, the founder was right about one thing. Something should have been banned — not the technology, which cannot be, but the practice of treating legitimacy as a marketing expense. That, we can stop. That, we should have stopped long ago.
