Governance on Arem

Polaris: A Rare Discipline

Mon, 04 May 2026 00:00:00 +0000

A DeFi protocol is rarely judged on its presentation, but almost always on how it performs under stress. There is, however, a category of intermediate situations — prior to deployment — that are worth highlighting because they are rare: a team formulates, challenges, and corrects its own architecture before a governance issue forces it to do so (such as an attack, an attempt to hijack governance, or governance inertia). Polaris has just completed this review. Polaris is a pre-launch decentralized stablecoin protocol, inheriting from the Liquity lineage and proposing a stewardship architecture in place of conventional governance. This article aims to describe the review in detail, identify what it brings to the table, and outline what remains to be observed to ensure the promise is fulfilled.

A Legacy

Polaris isn’t starting from scratch, and its quality stems in part from the rigor with which the protocol addresses this legacy. The core engineering team is the development team behind Liquity v1 and v2 — the team that secured over $2 billion in TVL without a single exploit, through Luna, FTX, and SVB. The initial research was developed at Liquity AG by Robert Lauko, now a Research Advisor. Laurens Kessenich (PhD in Physics from ETH Zurich) leads protocol architecture and modeling. Robert Mullins, after building the business development team at Jumper/LI.FI, leads operations and partnerships. Brice brings his accumulated experience from Liquity, ParaSwap, the DeFi Collective, DeFiScan, Pharos Watch, and Aave’s GHO Liquidity Committee — where he had flagged structural conflicts of interest to the community two years prior. This lineage is not an argument from authority; it is a foundation. It gives the project a point of reference with past failures that few protocols can draw upon so explicitly.

In Path to the North Star, Brice traces the lineage of decentralized stablecoins: SAI, DAI, LUSD, BOLD, and now pUSD. Each link in the chain has learned something that the next one tries not to repeat. Wisdom is the prerequisite for ambition: one does not propose a new architecture without having understood why the previous ones failed. This approach — understanding failures before proposing solutions — is what sets Polaris apart from yet another pre-launch project, and what makes its current move worth watching.

A Discipline

On March 3, 2026, Polaris published Stewardship, not Governance. The article brings together two things: a direct critique of the state of DeFi governance in 2026 — “there is no defending governance in 2026” — and the proposal of a third way between pure non-governance à la Liquity v1 and professionalized governance à la Aave. The core of the protocol is immutable. A limited stewardship layer governs what cannot be automated or purely incentivized: admission to StablecoinOS, CDP parameterization, treasury positions, and — a crucial point at this stage — a gauge emissions budget of 25% of POLAR over four years, voted on per epoch.

Five weeks later, on April 13, Sustaining the Ecosystem: pETH & pUSD Flows opens with this sentence: “we went back to the drawing board.” The admission is explicit. The team saw, within its own architecture, that the gauge emissions channel — even when carefully configured, even when bounded by stewardship — inherited the “governance picks winners failure mode” that stewardship was precisely meant to avoid. This is a complete overhaul of the incentive layer, which removes gauges, bribes, and weight wars and replaces them with a contract-enforced mechanism for self-distribution in hard assets.

The technical elegance is real and reveals discipline. A team that sees a latent capture channel in its own architecture, articulates it publicly, and eliminates it at the cost of a pre-deployment overhaul is doing something that neither Maker, nor Aave, nor most established protocols do. The capacity for self-restraint is likely, in 2026, the rarest quality in DeFi. It is not verified by pre-launch promises; it is verified by what is left out.

What Flows is Changing

Four elements are being overhauled simultaneously, and it is their combination that gives the system its value.

The game’s currency is changing. Incentives are no longer distributed as governance tokens (POLAR) but as hard assets (pETH and pAssets) derived directly from the protocol’s revenue. The consequence is political rather than merely economic: there is no longer a governance instrument to monetize, so no more trading of governance tokens is possible. The capture token has been removed. Any new issuance of POLAR now requires a pETH burn via the conversion mechanism, which closes the economic loop upon itself.

The allocation logic reverses the incentive structure. Allocation shifts from a vote per epoch to a self-executing formula: the share of Flow received by a contract is equal to its share of whitelisted pETH or pUSD. Integrators no longer lobby for incentives; they attract users to increase their share. The system rewards “capture and usage” rather than “lobbying, visibility, and vested interests”. This reversal is not cosmetic: it changes who speaks, who holds sway, and what the public conversation around the protocol is made of.

In concrete terms: under the gauge model standardized by Curve — and replicated by Polaris’s Stewardship v1 — a third-party protocol seeking emissions must accumulate veTokens, rent votes via Convex, or pay bribes on Votium or Hidden Hand. An entire political economy has developed around this — BD teams specializing in lobbying, dashboards tracking profitability per bribe, and voter alliances. Under Flows, these layers disappear by design: an integrator seeking a significant share cannot buy or lobby for it; they must attract users, because their share is mechanically proportional to their share of whitelisted pETH or pUSD. The public conversation shifts from “who votes for whom” to “who offers the best experience.”

The scope of stewardship shrinks radically. Under normal conditions — and this is the key point — “stewards have nothing to do.” Only three moments call for their intervention: admission to the whitelist, adjusting the weight during a revenue-share negotiation, and removing a disloyal actor. Residual power is extremely limited, and it no longer has a continuous channel for extraction. The burden on stewards shifts from an obligation of constant presence — which produces the spiral of exhaustion documented in most DAOs — to an event-based presence.

Founder dilution becomes automatic. POLAR generation is now entirely tied to the pETH→POLAR conversion, at a self-regulating rather than fixed rate. The more the protocol grows, the more the team is diluted. This asymmetry is explicitly acknowledged: “either it works, founders get diluted; no traction, no dilution.” With a structural nuance: each unit of dilution corresponds to a concrete improvement in the protocol — pETH burned, floor price raised, ETH released as yield. This is what distinguishes Flows from traditional issuance models, where token inflation and protocol health are decoupled. Here, dilution is not a cost to bear in order to make the system work — it is a sign that it is working.

Taken together, these four shifts eliminate several channels of capture simultaneously. And they demonstrate something worth noting in a broader debate: it is possible to substantially reduce a protocol’s governance without falling into pure ungovernance. Polaris offers an alternative to radical ungovernance, accepting a minimal layer of orchestration.

What Remains to Be Observed

Rigorous observation involves identifying where capture (which never disappears) has shifted. After deployment, not before.

The whitelist as a point of residual power. Brice acknowledges this in Flows: “Whitelists can be lobbied without vigilance. Any system with a human-controlled whitelist is subject to influence.” The power to admit or reject an integrator remains a real power. When asked about the initial composition of the Flow whitelist, the team clarified that the first wave would be limited to pETH-side pUSD/pGOLD CDPs and the pUSD/pGOLD-side Stability Pool — an internal bootstrap with no third-party admission at launch. This configuration eliminates the most obvious gray area of a stewardship deployment by not involving any discretionary admission decisions at launch. The question will therefore arise starting with the first third-party integrator vote.

The team highlighted two points on this subject. First, post-bootstrap admission will operate “through case law and process”, without a predefined framework. This is defensible — a rigid, predefined framework is itself susceptible to capture, and case law allows for learning on a case-by-case basis — but it means that the initial votes will set a precedent. Whoever steers them will have a lasting influence. On the other hand, and this is a stated principle, “responsible disclosure should happen on any proposal”: a clear commitment to publish any relevant links in voting proposals. This commitment is worth a great deal if upheld. It is missing in most established DAOs today.

The declarative obligation of revenue-share commitments. The Deceiver scenario — an integrator who negotiates a weight of 1.0 in exchange for a revenue share, then fails to honor the commitment — is addressed through social expulsion, not cryptographic enforcement. The team’s response is straightforward: “declarative, enforced by stewardship kicking out violating actors.” The guarantee is social and economic, not technical: an ejected Deceiver loses permanent access to Flow, which is a high cost for a temporary gain. This is defensible — demanding a cryptographic guarantee here would amount to demanding something that neither Aave, Maker, nor Liquity provide — but it depends entirely on the vigilance of the stewards and the existence of community dashboards to detect breaches quickly. To be documented over time.

Stress management. The hardcoded minimum of 30% allocated to the Stability Pool is fair: this is what maintains solvency. When asked about the course of action to take when a stress event mechanically compresses pUSD Flows for all recipients, the team clarified a point worth mentioning: there is no manual override. “No manual override is needed to face it” — the SP-first allocation is automatic; the compression of other allocations is a direct consequence of the drop in revenue, and the stewards have no button to press in real time. The system manages the crisis through its very structure, not through human decision-making. This is conceptually more radical than it seems, and it aligns with the Structure Over Trust doctrine: under stress, stewards aren’t asked to arbitrate — we arbitrated at deployment by hardcoding the minimum SP, and the mechanics do the rest.

The role of stewardship under stress thus shifts from arbitration to learning: “we’re definitely keen on learning from such episodes and helping the stewardship to step up from one to the next”. The relevant question is no longer “how will discretion be exercised?” but “how does the experience of one episode inform the next?”. A system of documented lessons learned — what the trigger conditions revealed, how the integrators were informed, what worked or didn’t work in communication — remains a useful subject for longitudinal observation, without this time carrying the enforceable nature of a discretion review.

Dilution contingent on success. The founders’ programmed dilution mechanism is elegant, but conditional: “either it works, founders get diluted; no traction, no dilution.” If the volume of pETH→POLAR conversions stagnates, dilution stagnates as well. The initial concentration does not dissipate according to a schedule — it dissipates through flow. This does not invalidate anything, but it means that the effective decentralization of governance remains a hypothesis to be validated over time, not an ex ante guarantee. The team is considering a periodic report — monthly or quarterly — on stewardship activity, and explicitly lists the metrics to track: number of vePOLAR lockers, percentage of delegated votes, percentage of active votes, concentration. This is exactly the type of data that external cross-sectional observation can capture and codify over time.

Why the Team’s Approach Matters Beyond Polaris

Regardless of what Polaris becomes on mainnet — and there will be stressful periods; there always are — the act of self-correction from Stewardship v1 to Flows is, in itself, a contribution to the ecosystem. It demonstrates that a DeFi team can formulate, challenge, and correct its own architecture before it is put to the test by market forces. That may not sound like much; in practice, it’s a quality few projects have demonstrated. Maker didn’t do it. Neither did Aave. Most established protocols wait for an event to reveal a flaw before naming it — and then the urgency of the rescue overshadows all reflection. Polaris does the opposite: it names, it corrects, it publishes, even before anything is launched.

If Polaris fails tomorrow, the gesture remains valid. If Polaris succeeds, the gesture becomes a lesson. In both cases, what deserves to be documented now is not a bet on the outcome, but the discipline that makes the outcome observable. The quality of an architecture is not measured by the absence of residual tensions — there are always some. It is measured by the precision with which these tensions are named by those who build them, and by the clarity they offer to those who observe them.

Structurally, this is the same movement that has occupied me since Coherence is the Scarce Good: what matters is not the verdict, but the grammar that makes the verdict possible. Polaris has just written a page of that grammar. It remains to be seen whether the writing holds up under pressure.

Observational article. No position held in Polaris as of the date of publication. Testnet 2, which carries the Flows architecture, was launched on May 7, 2026. Monitoring will continue in the coming months, as the protocol approaches the mainnet and the first stewardship votes take place.

Coherence is the scarce good

Sat, 02 May 2026 00:00:00 +0000

On April 18, 2026, an attacker drained 116,500 rsETH from the cross-chain bridge of Kelp DAO. Roughly $292 million.

Not because of a bug. Because of a decision that stayed invisible.

Kelp had chosen a 1-of-1 DVN configuration, a single verifier, against the explicit recommendations of its own infrastructure provider. That choice never made it into a proposal, a public debate, or any record before the incident happened.

Two days later, Arbitrum’s Security Council froze $71 million.

The debate started immediately. On one side, those who saw this as proof that nothing in crypto is truly decentralized. On the other, those who saw an emergency intervention against a state-level actor as not just legitimate but necessary.

Both positions are coherent. Both miss the point.

Because what happened here doesn’t begin with the hack. It doesn’t begin with the freeze either.

It begins at the moment a structuring decision can be made without ever being seen.

DeFi doesn’t break because of bad code.

It breaks because some decisions stay invisible until it’s too late.

And as long as those decisions stay invisible, every crisis will keep pushing the ecosystem toward an impossible choice between emergency centralization and principled inaction.

What becomes scarce

Decentralized organizations have solved two major problems. They aggregate capital with unprecedented efficiency. They aggregate preferences through sophisticated voting mechanisms.

But they have built almost nothing for a third aggregation, even though it may be the most decisive: the aggregation of intelligent work over time.

That work exists everywhere. It takes the form of research, discussions, technical trade-offs, disagreements, intuitions. It flows through multiple channels and then disappears. Each new session starts where the previous one left off, with no usable trace in between.

Intelligence gets produced. It doesn’t accumulate.

This flaw stayed invisible for a long time, for a simple reason: intelligence used to be scarce.

It isn’t anymore.

AI has tipped intelligence into abundance. What’s now in short supply isn’t analysis or code. It’s the capacity to hold together what’s already been produced.

Intelligence is becoming abundant. Coherence is the bottleneck.

This shows up in different but converging diagnoses. Aragon observes that the volume of decisions grows faster than available attention. Twyne points at the absence of cumulative memory and continuity in the work of agents.

Three observations. One shared limit.

Coordination distributes tasks. It doesn’t produce continuity.

And in that gap, something deeper is shifting. If a structuring decision can be made without being visible, without being documented, without being challengeable, then the system that contains it is not decentralized in any strong sense.

We didn’t decentralize power. We decentralized its interface.

This shift produces very concrete effects. It favors those who control the context, those who hold informal memory, those who can act without making their decisions legible.

Kelp is not an anomaly.

It’s a system revealing how it actually worked, at the moment it failed.

Aragon, the art of not governing

In this landscape, Aragon offers one of the most advanced architectures.

Their starting point is clear: onchain governance frameworks, in their current form, have not given organizations a reliable way to act with precision. Their answer is to shift the central primitive. The proposal is no longer what structures the system. The permission is.

With OSx, governance becomes an architecture of rights. Capabilities are defined explicitly, then distributed and recombined through modules.

The decisive step comes with the notion of policy. Proposals are reserved for genuinely new decisions. Everything else, recurring payments, predictable allocations, repeatable configurations, is codified as executable rules.

Evan Aronson’s formula puts it precisely: “Policy design is an art of not governing.”

This isn’t about reducing governance. It’s about relocating it. A decision is no longer a one-off event. It becomes a rule that’s both binding and executable, with no need for ongoing intervention. I’ve worked through this intuition philosophically in an earlier piece on gentle power; Aronson gives it its technical form.

With Linked Accounts, Aragon pushes the logic further by making the purpose of fund flows explicit. Organizational structure stops being implicit. It becomes legible inside the system itself.

This work is substantial. It introduces a kind of legibility that was missing.

But that legibility operates in a deterministic frame. It assumes the relevant actions can be anticipated, that rules can be defined in advance, that behaviors can be bounded.

Anything that escapes that frame stays out of view. Upstream technical trade-offs, informal decisions, the ongoing production of meaning, anything that doesn’t stabilize into a rule remains invisible.

Aragon makes decisions executable. It does not make their formation visible.

Twyne root-archetype, the grammar of agents

This is where root-archetype steps in, the agent governance layer Twyne uses internally and has released under an open license.

With root-archetype, the move is to introduce, on top of application code, a layer that produces nothing directly but defines the conditions of production themselves. Roles, memory, handoff protocols, shared constraints. Everything that gives shape to continuity in collaborative work.

The gesture is simple. Its effects run deep.

A session no longer starts from scratch. Context carries over. Knowledge stops evaporating between contributions.

Intelligence starts to compose itself.

Released under an open license, this model is meant to become a primitive. It offers a minimal grammar from which an ecosystem can structure itself.

The symmetry with Aragon is clear. Aragon codifies decision on the capital side. Twyne root-archetype codifies the grammar of work on the agent side. One structures what gets decided, the other structures what makes decision possible.

But neither of them makes visible how those two dimensions interact.

Twyne itself, the credit-delegation primitive the team is building, illustrates precisely why this layer is missing. The safety of a credit primitive depends on upstream decisions: parameter choices, oracle picks, verifier setups. Exactly the kind of decisions that, when they stay invisible, become tomorrow’s exit conditions. What happened at Kelp is of that exact nature, which is what makes the legibility question anything but theoretical.

The missing layer

This is where the problem becomes legible.

Neither Aragon nor Twyne root-archetype makes visible how decision, capital, and production hold together over time.

That invisibility is exactly what made Kelp possible.

What’s missing isn’t another tool. It’s a layer.

A system that makes structuring decisions visible before they produce irreversible effects.

We can name it plainly: an Organizational Observability Layer.

A layer of this kind doesn’t just trace outputs. It represents how an organization actually functions. It connects actors, human and agent, with their tasks, their dependencies, their decision points. It holds the memory of choices, alternatives, disagreements. It formalizes handoffs. It exposes constraints. It sustains a transversal watchfulness.

Making the actual functioning of a system visible is becoming a strategic capability.

Today, contributing too often means just adding work. In an organization with such a layer, contributing means modifying a shared state.

It’s what turns a succession of initiatives into a cumulative process.

It also clarifies a distinction that often gets blurred. Coordination answers who does what. Coherence answers a more demanding question: does the system, as a whole, still make sense?

Current tools improve the first. The second still has to be built.

The false alternative

The debate that opened after the Arbitrum freeze reveals exactly where we are.

Should we intervene or not? Should we accept emergency centralization, or hold strict fidelity to principle?

The questions are legitimate. They just arrive too late.

They assume the incident has happened and that we now have to pick between two flawed options. They never ask what made the incident possible in the first place.

Had Kelp’s DVN configuration been visible, documented, challengeable before it shipped, the choice could have been different. Or owned. Or constrained.

In any of those cases, it would have lived in a shared space.

Every incident of this kind is a failure of visibility before it is a failure of security.

Recognizing this doesn’t remove the risk. It moves the ground on which the risk has to be addressed.

Decentralization no longer plays out solely in the ability to react. It plays out in the ability to make decisions visible before they become irreversible.

That’s a third path. Not a compromise. A reframing.

The natural slope

Building such a layer comes with real tensions.

Over-formalization can rigidify the system. A too-clean representation can hide misalignment, unless it makes explicit room for dissent.

But the deeper risk lies elsewhere.

Any layer of legibility creates an asymmetry. Whoever sees more than others has an advantage. Without an explicit mechanism, that asymmetry drifts toward capture: by a central team, by a vendor, by an external actor.

What isn’t held as a commons becomes a point of control.

Holding a coherence layer as shared infrastructure is the only regime that doesn’t take care of itself. Every other regime emerges without effort.

A political stake

Coherence is not a technical problem. It is a political choice.

It determines who can see, who can understand, who can challenge. Today, those dimensions stay largely implicit, and therefore default-controlled by whoever already occupies a central position.

This is a call on our vigilance, in the same direction I proposed in a public grammar of risk.

Engaging with a protocol shouldn’t be limited to assessing its code, its tokenomics, or its formal governance. It should include a simpler, more demanding question: how are structuring decisions made visible?

That is the dimension Kelp lacked. And it is the dimension that will determine how robust the systems to come actually turn out to be.

To close

Aragon and Twyne root-archetype have laid down essential bricks.

One on decision and capital.

The other on production and memory.

But the layer that would let those two articulate is still to be built.

Without it, every crisis will keep forcing a choice between centralization and powerlessness.

With it, structuring decisions become visible before they become irreversible.

We haven’t failed to build decentralized systems.

We have failed to make them legible.

That legibility, that coherence, is what is now genuinely at stake. And what remains to be invented.

Transversal Watchfulness

Thu, 23 Apr 2026 00:00:00 +0000

A crisis reveals what an economy is willing to pay for—and what it leaves out of the frame. DeFi’s April 2026 sequence—the USR depeg and the Kelp exploit—brought into view a structural asymmetry that few analyses have taken the time to name.

Days before Kelp DAO, a depeg hit the stablecoin USR. Users who were alerted early enough got out. That early signal came from Pharos Watch, a stablecoin observatory launched two months earlier by an independent developer, self-funded, who recently opened a public donation page simply to keep the project running.

That observation raises a question Kelp only made sharper: who pays for DeFi to keep making sense of itself?

What protocols fund—and what they don’t

The picture is more nuanced than it first appears.

Over the past two or three years, DeFi has learned to fund part of its own security layer. LlamaRisk has been an Aave service provider since 2024, with an annual budget of around one million dollars in AAVE, vested against KPIs. Chaos Labs operates under a similar model. These are professional risk providers, paid by the very DAOs they analyze.

Since February 2026, the Ethereum Foundation has structured a partnership with the Security Alliance (SEAL) to fund a security engineer dedicated to combating drainers. The ETH Rangers program, which closed in April 2026, funded six months of stipends for seventeen security researchers working on public goods.

Serious startups exist as well. Blockaid, which published Kelp’s technical post-mortem and an open-source DVN audit script, raised 83 million dollars from Ribbit Capital, Google Ventures, Sequoia, and Greylock. Its clients include Coinbase, MetaMask, and Uniswap.

Some core contributors, banteg among them—whose reading of LayerZero’s deployment code became a reference during the crisis—draw salaries from major protocols.

So the ecosystem has learned to pay some of its watchers. But it pays them conditionally—and that condition draws a sharp line.

Servile watchfulness, transversal watchfulness

Every paid structure mentioned above shares one defining property: it serves an identified payer.

LlamaRisk looks at Aave because Aave is paying. Chaos Labs follows the same logic. Blockaid protects Coinbase and MetaMask under commercial contracts. SEAL operates with targeted sponsorship from the Ethereum Foundation. The work these actors do is serious and valuable. That does not make them independent observers. Their mandate is defined by whoever signs the check.

Alongside this servile watchfulness runs another function, rarer and more exposed: transversal watchfulness. The kind that observes several competing protocols without belonging to any of them. That maps the system as a whole rather than acting as a vendor to a single actor. That can call out a problem affecting a potential payer without jeopardizing its own economic survival.

The distinction is easy to state: servile watchfulness serves an identified payer. Transversal watchfulness observes the whole without belonging to any. The first is funded. The second is not.

Two structures carry this function almost alone in 2026.

Pharos Watch, mentioned above, tracks 205 stablecoins across every major chain. Its founder, TokenBrice, recently stated publicly that he funds the tool out of pocket and is aiming to transition to community funding via Giveth by the end of 2026.

DeFiScan, maintained by the DeFi Collective, produces an independent evaluation of DeFi protocol decentralization based on a formalized framework. It operates as a non-profit, funded through Giveth and open contributions.

To these, add a handful of researcher-practitioners who publish analysis alongside their primary engagements, and a scattered layer of independent editorial observers.

This transversal layer is structurally fragile. It rests on the personal persistence of a few founders. By definition, it cannot sell services to what it observes without becoming servile itself. And the ecosystem has yet to build mechanisms capable of funding it without capturing it.

What Weick called sensemaking

In the 1970s and 1980s, organizational sociologist Karl Weick studied collective disasters—the Mann Gulch fire of 1949, the Bhopal catastrophe of 1984—to understand why groups facing ambiguous situations lose their ability to act coherently. His answer fits in one word: sensemaking. Organizational survival under stress depends less on computational power than on the capacity to build a plausible shared understanding of what is happening.

Weick showed that this function is not automatic. It requires structures capable of producing shared meaning independently of the particular interests of the actors involved. These are the structures that make collective sensemaking possible.

Pharos, DeFiScan, SEAL, banteg, Tay, ZachXBT, LlamaRisk, editorial observers—each contributes to that function. Their coexistence, their ability to read one another, and the fact that their outputs are publicly verifiable make convergence toward a plausible shared account possible.

When these structures are missing, collectives move through crises blindly—not because information is absent, but because no one is responsible for making it collectively intelligible.

DeFi is, by design, a high-ambiguity environment: opaque composability, hidden dependencies, a proliferation of actors, no central authority. It requires sensemaking more than most technical ecosystems. And yet the economic structure it has built rewards the production of complexity handsomely, and the production of shared understanding barely at all.

The tension has been articulated recently by others. Gitcoin, which has carried the question of public goods funding in the Ethereum ecosystem for years, integrated sensemaking into its grants architecture starting in 2025. Their formulation, in recent research, goes further: when AI extends mediation from what we see to how we reason, the risk becomes existential. They pose the question at a civilizational scale. It arises at DeFi scale with the same force—only closer to home.

What both traditions converge on, each in its own way, is the same reality: a collective capacity to understand does not emerge on its own. It requires dedicated actors, maintained capabilities, stable funding—and, crucially, structural independence from the interests being observed. Without these, there is no shared understanding. There are only competing narratives.

Once the frame is set, the problem facing post-Kelp DeFi comes into focus. It is not that DeFi lacks watchfulness. It has developed plenty. It is that no mechanism exists to fund its transversal layer.

When Aave pays LlamaRisk a million dollars a year, it pays for risk analysis on Aave. That is legitimate and useful. But no one, in that equation, is paying LlamaRisk to publicly say something that might embarrass Aave when the moment calls for it. No one is paying for an independent structure to observe Aave and its competitors with the same lens. No one is paying to map dependencies that cut across protocols without belonging to any of them.

The standard objection to publicly funding this kind of function is that it would create political dependency. It would not. L2Beat, for years, has served as a reference for evaluating Ethereum rollups without being captured by any of them—precisely because it built structural independence: diversified funding, transparent methodology, and a stable team. That model exists. It is simply not generalized.

The standard libertarian objection—users who need this information should pay for it—runs into a well-known economic constraint: information goods behave like public goods (non-rivalrous, partially non-excludable), which prevents markets from producing them efficiently on their own. No one pays for watchfulness while it exists. Everyone regrets it once it disappears.

It must also be acknowledged that the ecosystem can coordinate when incentives align. Fluid’s response—together with Lido, ether.fi, 1inch, and KyberNetwork—to unblock aWETH positions stuck on Aave post-Kelp, processing more than 400 million dollars within hours, is a recent example. That operational coordination is real and valuable. It does not solve the problem raised here. Fluid coordinated with Lido because their users overlapped and their commercial interests converged. No one, in that configuration, was tasked with holding a perspective that might have challenged any of the parties. Coordination under aligned incentives works. Watchfulness without an economic mandate remains orphaned.

What this concretely asks for

A sustainable DeFi—one that lasts a decade rather than a cycle—will have to consolidate mechanisms that are only just beginning to emerge.

For mature DAOs. Aave, Uniswap, Lido, Sky sit on treasuries in the hundreds of millions of dollars. Setting aside a fixed fraction—well below one percent—as an endowment for public intelligibility infrastructure, with no service counterpart and no contractual capture, would be a technically trivial move. It has not yet been seriously put on the table.

For the commercial actors who depend on them. The emerging intelligence layers selling DeFi attention—dashboards, institutional analytics, paid risk platforms—all rely on public sources (DeFiLlama, DeFiScan, Pharos, independent analysis blogs). In other ecosystems, it is standard practice to reinvest a fraction of revenue into upstream public goods. In DeFi, this norm remains informal at best.

For public goods funding programs. Gitcoin Grants, Optimism RetroPGF, Octant exist—but are underutilized for transversal intelligibility infrastructure. Coordinating one or more dedicated rounds around this category would have outsized impact.

A concrete example is emerging right now, covering part of that terrain. TheDAO Security Fund, endowed with 170 million dollars, launched its first round via Giveth on April 21, 2026, with 500 ETH in matching funds for Ethereum and L2 security projects. Its announced scope (incident response, security research, on-chain investigation, security tooling, threat intelligence) covers the defensive layer of transversal watchfulness. It does not cover the analytical and editorial layer that produces meaning outside of incidents: independent mapping, non-technical observatories, public critical analysis. Still, this marks a first: a public goods funding mechanism explicitly targeting part of this space. Pharos and DeFiScan are eligible. Editorial observers likely are not. The signal matters: the ecosystem is beginning to acknowledge that it must fund what it does not directly consume.

For users. Pharos has a Giveth page. DeFiScan as well. SEAL accepts donations. Those who rely on these resources daily can support them directly—not as charity, but as informed self-interest. If these structures disappear, users will be left navigating only protocol-aligned narratives.

For the ecosystem as a whole. Cite your sources. Tag contributors. Acknowledge dependencies. Publicly recommend the free tools you rely on. Less material than the other levers, but not trivial. Recognition sustains volunteer motivation and helps lay the groundwork for a more formalized economy of attribution.

A sixth lever deserves to be made explicit. The coming temptation will be to outsource to artificial intelligence what humans have so far provided for free. Why fund Pharos when an LLM can scrape and summarize peg data? That logic accelerates the devaluation of functions whose value lies precisely in their human, situated, independent nature. An LLM can process data. It cannot hold a public position against the interests of a protocol it does not understand. Confusing the two will degrade DeFi’s epistemic layer more reliably than any exploit.

To close

A sustainable DeFi is not the one with the most sophisticated protocols. It is the one in which the collective capacity to understand what is happening is funded as seriously as the capacity to generate yield. That is not the case today. This gap is a systemic risk no dashboard currently measures.

The structures carrying this function—Pharos, DeFiScan, independent researcher-practitioners, and editorial observers such as the one behind this piece—will not hold indefinitely without material support. Every founder who burns out, every researcher who shifts to paid work, every independent observer who shuts down their blog creates another blind spot.

The question raised by the April 2026 events is not whether DeFi will survive Kelp or USR.

It is whether DeFi will equip itself with the material means to keep making sense of itself.

Without those means, the next crises will be navigated blindly—not for lack of tools, but for lack of people still holding them.

More Dashboards, Less Wisdom? The DeFi Paradox.

Tue, 07 Apr 2026 09:00:00 +0200

In a world saturated with dashboards, alerts, and metrics, the real issue is no longer how to see more. It is how to choose an exposure, what powers to tolerate, and how far we are willing to preserve freedom of action without sacrificing it to total visibility.

Omniscience Without Mastery

Our age combines an odd mixture of omniscience and impotence.

Signals proliferate, clues pile up, traces multiply, and yet our ability to turn them into something legible, ordered, and politically usable keeps slipping away. In DeFi, that condition becomes almost experimental. Everything seems observable. Flows are public, metrics are abundant, and interfaces for reading the system have multiplied at great speed.

But this apparent triumph of visibility leaves a harder question untouched: what do we do with a world we can inspect ever more closely without actually learning how to inhabit it better?

The Observability Stack — and Its Limits

The ecosystem has already built an impressive observational infrastructure. DeFiLlama, for example, does more than aggregate numbers: it defines its own metrics, distinguishes TVL from borrowed funds, and reminds users that net flows often say more than a badly interpreted stock variable. L2BEAT, meanwhile, has forced a rollup conversation centered on trust assumptions, decentralization stages, and residual powers. DeFiScan does something similar for DeFi protocols, explicitly acknowledging that a decentralization framework does not measure smart contract risk, nor economic risk in its entirety. This is real progress: DeFi is no longer short on ways of reading itself.

But that rise in visibility has exposed a newer difficulty. The problem is no longer simply that risk is poorly seen; it is that it is seen through a plurality of heterogeneous cuts, rarely commensurable and often in tension with one another. Each actor produces its own surface of intelligibility, its own method, its own way of ordering uncertainty. One tracks flows, another maps powers, a third watches code vulnerabilities, a fourth models credit dynamics, a fifth focuses on the fragility of a monetary subsystem. None of this is useless. But a pile of specialized readings still falls short of a public intelligence of risk.

A Reading Map

Reading DeFi now requires an order of operations. Not in order to collect tools, but to discipline judgment before action.

From Signals to Judgment

Read from top to bottom: start with power, then context, then failure, then risk design, then mediation, then money.

1Powers / Trust Assumptions

L2Beat DeFiScan

2Terrain / Market Context

DeFiLlama Dune GrowThePie

3Breaks / Failure Modes

ChainSecurity Forta Hypernative

4Risk Parametrization

Chaos Labs Gauntlet

5Credit / Vaults / Mediation

Block Analitica Credora CuratorWatch vaults.fyi Morpho

6Monetary Layer

Pharos Bluechip Stablewatch

The method is straightforward: power → context → failure → parametrization → mediation → money. The most common mistake is to reverse that order — to begin with yield, a polished dashboard, or the most visible metric, when the decisive questions are still questions of power and dependence.

The Missing Mediation: Toward a Public Grammar of Risk

At this point, a new requirement emerges. A mature ecosystem cannot rest on a scattered landscape of dashboards, frameworks, scorecards, and expert tools alone. It also needs a more legible mediation layer: a public synthesis capable of offering a common point of entry, making broad risk profiles comparable, and orienting judgment without pretending to exhaust reality. Not a magical score that crushes every difference into an opaque verdict, but an aggregation clear enough to guide and decomposable enough to remain honest.

In other words, DeFi probably needs more than a collection of specialized tools. It needs a public grammar of risk.

The Privacy Constraint

And this is precisely where a decisive limit has to be introduced. From an Ethereum point of view, the answer cannot be to celebrate ever more observation, ever more monitoring, ever more traceability, as though full transparency were the natural endpoint of a healthy system. In Why I support privacy, Vitalik argued in April 2025 that privacy is not a luxury but a safeguard of decentralization itself: whoever controls information already holds a form of power. The Ethereum Foundation framed the same idea in more institutional terms: privacy is the freedom to choose what you share, when you share it, and with whom.

So the right kind of legibility is not the kind that makes everything visible to everyone at all times. It is the kind that makes structures, dependencies, and powers more intelligible without abolishing users’ room for withdrawal, discretion, and autonomy.

That is why DeFi’s problem is not merely a tooling problem. It is an orientation problem.

A Doctrine of Exposure

A good craftsperson does not begin by choosing tools. They begin by clarifying their intention. In DeFi, that means choosing a doctrine of exposure.

You can look at ten dashboards, two decentralization frameworks, three audits, a handful of runtime alerts, and a synthetic rating layer, and still fail to clarify anything essential. Because these instruments do not observe the same layer of reality. One maps the terrain, another maps powers, a third watches for software failure, a fourth models credit or liquidation dynamics, a fifth tracks the stability of a monetary subsystem. A map is not a compass. And a stack of screens is not yet a doctrine of exposure.

So the real question is not: which tools should I use?

The real question is: what kind of actor do I want to be in this environment?

That sounds abstract, but it is deeply practical. Are you primarily seeking yield? Capital preservation? Strong exit liquidity? Maximum proximity to self-custody? Strictly reduced trust assumptions? Limited experimental exposure? Why? On what time horizon? Until that orientation is clarified, tools mostly serve to compensate for the absence of strategy. And they do it badly.

Simplicity, Trust Minimization, and Order of Reading

A second correction has to be added here, and it comes directly from Vitalik. Not every interpretive problem should be solved by adding more interpretive layers. Some should be solved by greater structural simplicity. In Simplifying the L1, published in May 2025, Vitalik argues that Ethereum should move toward an architecture that is easier to understand, audit, and maintain.

That argument is decisive for DeFi: a system that can only be inhabited through a permanent caste of analysts, curators, scorecards, and alerts is not yet a broadly intelligible system. Observability is useful, but it should not become a substitute for architectural sobriety.

This is also what restores real meaning to trust minimization. Stages, for Vitalik as for L2BEAT, are not just a technical taxonomy. They force a political question into the open: who can still override the code, under what conditions, with what legitimacy, and with how much reaction time for users?

Once the problem is framed that way, practice changes. A cautious depositor should not begin with yield. They should begin with power. Who can upgrade? Who can freeze? Who can redirect risk? Is there a real exit window? A user should not be looking merely for a “good product,” but for a regime of exposure compatible with their tolerance for dependence.

Where Practice Becomes Philosophy

The practical dimension becomes clearer at that point. Maturity does not mean watching everything. Maturity means being able to connect a signal to a possible action. A trust assumption that is too heavy should be enough to keep you out. Fragile exit liquidity should lead you to size down. Excessive complexity should push you toward a simpler, perhaps less profitable, but more legible system. A strong dependency on an interface, a multisig, a curator, or a freeze-enabled stablecoin should be enough to make you give up some yield in order to preserve some freedom.

And this is where practice finally becomes philosophy.

Because behind every doctrine of exposure lies an ethic of action. One can inhabit DeFi according to a speculative logic, where every signal is treated as tactical advantage. One can inhabit it according to a prudential logic, where the central task is to reduce avoidable blindness. One can inhabit it according to an ethic of autonomy, where the priority is to remain on the side of self-custody, privacy, simplicity, and legible power. And one can inhabit it according to a more ambitious institutional logic: helping build stronger forms of public judgment, better standards, more honest risk taxonomies, and more robust mediations between code and action.

That, it seems to me, is where the right reading of DeFi now begins. It does not merely need better tools. It needs a discipline of judgment capable of ordering signals without sacrificing Ethereum’s political ends: privacy, self-custody, censorship resistance, simplicity, open source, and minimized trust assumptions. The Ethereum Foundation now says this explicitly in its February 2026 DeFi position. Vitalik, for his part, provides the conceptual vocabulary for understanding why it matters: more legibility, yes — but not at the price of a more sophisticated form of dependence.

So the answer is neither fatalistic withdrawal nor dashboard superstition.

It is a doctrine of exposure.

Then a discipline of interpretation.

And behind both, a certain idea of freedom.

How Can an Open Collective Hold Together?

Sun, 22 Mar 2026 00:00:00 +0000

Why voting and incentives are not enough

A sound system of governance does not rest on voting mechanisms, incentives, or technical excellence alone. It also requires a legible direction, credible norms, forms of appropriation, and figures capable of embodying what they defend. The real question, then, is not only how decisions are made. It is this: how does a common order emerge that free participants can regard as legitimate, useful, and worth sustaining?

Beyond command: the problem of sustaining participation

We still tend to associate power with the ability to impose. To govern, on this view, is first to command, arbitrate, discipline. That picture is not always wrong. But it quickly becomes inadequate when what must be sustained is an open collective, composed of free, mobile, heterogeneous individuals who can withdraw more easily than they can be made to obey.

In such a setting, the central problem is not simply how to secure a decision. It is how to sustain participation over time. A collective does not hold together for long through constraint alone, or even through the mere convergence of interests. It holds when a shared direction becomes clear enough, just enough, and credible enough to be taken up by those who participate in it.

Gentle power: orient rather than compel

That is what the idea of gentle power makes it possible to think.

We can understand it as a form of government that seeks less to compel than to orient. It abolishes neither authority nor rules, but places them within a more demanding frame: a line must appear not merely acceptable, but worthy of being followed. Gentle power works through vision, example, shared norms, and the quality of institutions and relationships. It does not produce mere compliance; it seeks assent.

Gentle power vs. shallow influence

This is also what distinguishes it from influence in the shallower sense of the term. Marketing and storytelling can capture attention, sometimes even enthusiasm. They are not enough to found a common order. Gentle power does not simply aim to persuade an audience. It aims to make conscious cooperation possible: a form of cooperation in which members of a collective can recognize the reasons for acting as reasons they can genuinely make their own.

The distinction matters. Where influence often seeks effect, gentle power demands coherence. It rests less on what is proclaimed than on what is made visible, what is rewarded, what is tolerated, and the way rules are actually lived.

Implications (1): leadership

This changes, first of all, the meaning of leadership. From this perspective, leadership is not primarily a matter of concentrating authority or deciding faster than everyone else. It consists in giving an intelligible direction, setting criteria, and making the collective more capable of governing itself. Example becomes central here. A group places less trust in principles that are merely stated than in conduct it sees embodied.

Implications (2): legitimacy

It also changes the way legitimacy is understood. Legitimacy does not flow from procedure alone, even when procedure is flawless; nor does it arise from effectiveness alone. It emerges from a subtler alignment: between clear rules and intelligible decisions, between words and conduct, between a real possibility of participation and a just way of handling disagreement. A difficult decision is accepted more readily when it appears to proceed from a common world that can be understood, rather than from a simple balance of power.

Implications (3): endurance

And it changes the way a collective endures. Constraint may secure immediate execution; it rarely produces deep fidelity. For an organization to last, something else must take hold: the sense that it deserves time, attention, perhaps even a measure of renunciation. That is the point at which norms and values cease to be decorative. They become conditions of stability.

Why this matters for protocols and DAOs

This is especially important for protocols and DAOs. In such environments, coercion is structurally limited. One can leave a community, stop contributing, sell tokens, fork the code, or direct one’s attention elsewhere. A protocol therefore cannot rely, over time, on obedience. It must generate trust, legibility, a sense of fairness, and a form of attachment that is not purely opportunistic.

And yet many organizations are better at aggregating preferences than at articulating a common direction. They excel at managing technical variables, but struggle with deeper questions: what matters here? What kind of conduct do we want to encourage? What limits do we want to set? What deserves protection beyond immediate utility?

Where gentle power begins

Gentle power begins precisely there: in the capacity to form a shared sense rather than merely juxtapose interests.

Norms as operative architecture

That requires serious work on norms. Not abstract values filed away in a manifesto with no practical force, but operative standards: what is valued in exchanges, what is expected of central figures, what is built into rituals, tools, contribution mechanisms, and forms of recognition. Culture is not an optional layer. It is an essential part of the architecture of governance.

Narrative and play

This is why narrative and play matter here.

Narratives, when they are not reduced to exercises in communication, give shape to a shared experience. They connect the present to memory, ambition, and a certain idea of what the collective is trying to become. They help transmit landmarks, name tensions, and make choices more intelligible.

Play serves a related purpose. It creates a space in which rules can be learned, situations tested, roles explored, and the effects of an institutional design grasped without immediately hardening into rigid norms. In both cases, the point is not to entertain the collective, but to form it.

Risks and conditions of legitimacy

None of this should be romanticized. Gentle power can slide into a more palatable form of manipulation. The language of vision, values, or community can easily conceal quite conventional relations of power. That is why this form of power is legitimate only on one strict condition: those who orient others must themselves accept demanding standards of coherence, transparency, and contestability.

Structure still required

Nor can any organization rest on diffuse assent alone. It also needs rules, procedures, responsibilities, and, at times, sanctions. Gentle power does not abolish structure; it makes it finer and more inhabitable. It does not replace institutions. It raises the standard they must meet.

Time and political work

And this approach takes time. Forming a collective capable of sustaining a shared horizon, living through disagreement, and integrating difference without dissolving into fragmentation requires real political work. It requires pedagogy, spaces of translation, suitable formats, and a certain patience. Without that, the appeal to assent remains verbal.

What gentle power is (and is not)

Gentle power is therefore neither weakness nor vague moralism. It is a demanding hypothesis about how free beings may be guided. It reminds us that a collective becomes more solid when it learns to elicit forms of conduct rather than extract behavior. And in the end, the quality of an organization may be measured less by its capacity to constrain than by its capacity to make people willing.

Note

Note — This reflection stands at the intersection of several lines of thought: Spinoza on affects and the power to act; Tarde on imitation and the social circulation of conduct; Foucault on power as a productive relation; Charles Taylor on the social imaginary and on forms of recognition that make a common order livable. One distinction should nevertheless be kept clear: soft power, in the strict sense, belongs first to Joseph Nye, who defined it as a power of attraction rather than coercion.

Governance on Arem

Polaris: A Rare Discipline

A Legacy

A Discipline

What Flows is Changing

What Remains to Be Observed

Why the Team’s Approach Matters Beyond Polaris

Coherence is the scarce good

What becomes scarce

Aragon, the art of not governing

Twyne root-archetype, the grammar of agents

The missing layer

The false alternative

The natural slope

A political stake

To close

Transversal Watchfulness

What protocols fund—and what they don’t

Servile watchfulness, transversal watchfulness

What Weick called sensemaking

The funding blind spot

What this concretely asks for

To close

More Dashboards, Less Wisdom? The DeFi Paradox.

Omniscience Without Mastery

The Observability Stack — and Its Limits

A Reading Map

The Missing Mediation: Toward a Public Grammar of Risk

The Privacy Constraint

A Doctrine of Exposure

Simplicity, Trust Minimization, and Order of Reading

Where Practice Becomes Philosophy

How Can an Open Collective Hold Together?

Why voting and incentives are not enough

Beyond command: the problem of sustaining participation

Gentle power: orient rather than compel

Gentle power vs. shallow influence

Implications (1): leadership

Implications (2): legitimacy

Implications (3): endurance

Why this matters for protocols and DAOs

Where gentle power begins

Norms as operative architecture

Narrative and play

Risks and conditions of legitimacy

Structure still required

Time and political work

What gentle power is (and is not)

Note