DeFi 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.

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.

3. DeFi as a Laboratory of Delegation

Mon, 13 Apr 2026 13:00:00 +0000

Series opening: Self-Custody, But How Far?

In DeFi, an idea quickly turns into a permission, a risk rule, or a signature.

That is what gives DeFi its head start.

In many digital environments, ambiguity can last a long time. Actions remain diffuse, consequences are spread out, mistakes can be patched over. In DeFi, much less so. The distance between a market read, a recommendation, a click, an approval, and an execution is short.

A dashboard is not just an interface. It can shape how risk is seen. A wrapper is not just a service. It can reframe what counts as safe. An agent is not just an assistant. It can monitor, propose, prepare, trigger, or — within certain bounds — act.

That is why DeFi sees earlier than most sectors what delegation becomes once it stops being an abstract convenience and takes the form of real permissions.

The protocol no longer sums up the system

We still talk too easily about “protocol risk,” as if the protocol alone were enough to describe the object.

It no longer is.

Between the user and the protocol there now sits an entire software environment: specialized interfaces, dashboards, wrappers, copilots, treasury tools, research layers, monitoring tools, coordination services, and in some cases already execution agents.

The point is not to cast suspicion over every one of these objects. The point is to see that they redraw the map of trust. Even when the base protocol is solid, the surrounding environment can become the main place where the problem reappears: what we see, what we understand, what we think we understand, and what we are being nudged to do.

What AI changes materially

This is not just a conceptual shift. It is a material one.

AI dramatically lowers the cost of producing software layers around protocols: dashboards, assistants, wrappers, analysis tools, micro-services, orchestration layers. Builders ship faster, test faster, iterate faster. In many cases, that is genuinely good news.

But the cost of verification, qualification, and prudent integration does not fall at the same pace.

So the issue is not that tools are being built with the help of AI. The issue begins when the cost of producing a service falls much faster than the cost of understanding it, reviewing it, and integrating it well.

At that point we do not just have more software. We have more surfaces of trust to evaluate.

Vibe coding: not a scandal, a reveal

The term is often used too loosely. It is better handled with care.

Not every AI-assisted build is vibe coding in the strong sense. Not every tool built quickly is unserious. And it would be absurd to accuse any specific dashboard, service, or project without evidence.

What the phenomenon does reveal is more structural: an environment in which access layers, analysis layers, orientation layers, and sometimes already execution layers can be produced very quickly — an environment in which apparent fluidity can improve faster than the community’s capacity to judge what has actually been reviewed, understood, bounded, and owned.

The issue is not the builder’s moral failure. The issue is the acceleration of the context in which the user has to exercise judgment.

Two protocols that make the problem legible

Money League and Polaris are not used here as two more protocols to “watch,” nor as stabilized objects.

In both cases, these are still developing systems whose public shape can evolve. They are therefore being treated with caution, on the basis of their current presentation, as provisional figures rather than fixed models. Polaris in particular may well end up confronting the question of an agentic layer more explicitly than it does today.

These two cases matter because they make the same problem legible in sharply different ways.

Money League presents itself as a permissionless infrastructure for launching and coordinating decentralized stablecoins, with a modular architecture, shared incentives, and above all an explicit thesis about agentic money: prediction markets inside the monetary loop, proof of agent competence, agents as stabilizers, and the horizon of an inter-agent economy settled in fully onchain assets.

Polaris, by contrast, presents itself as an onchain, immutable, trustless stablecoin operating system centered on a tightly bounded monetary core, internal yield mechanisms, and a modular extension logic.

The value of the comparison lies in that gap. Money League helps us think about how far agentivity can climb into monetary infrastructure. Polaris reminds us that before any system becomes more powerful, someone still has to decide what must remain bounded, legible, and politically bearable.

Money League: pushing the agentic horizon further

Money League matters because it pushes a hypothesis many still prefer to keep at the edge: the agentic layer can rise all the way into money itself.

In its public imaginary, agents do not stay at the margins. They enter the loops of stabilization, forecasting, coordination, and management. Its strength is that it makes this horizon visible without hesitation. Its limit, for our purposes, is that it says more about the sovereignty of the system than about the practical sovereignty of the person doing the delegating.

Polaris: returning to the question of constitution

Polaris is, in that sense, a useful counterpoint.

Its public interest does not begin with spectacular agentivity, but with a more constitutional architecture: an immutable core, limited stewardship, and a small number of adjustable parameters constrained inside coded bounds.

Its strength is to remind us that a system does not become more legitimate simply because it automates more. It becomes more intelligible when it knows how to distinguish what must be delegated, what can be adjusted, and what has to be withdrawn from ordinary variation.

What they show together

Taken together, these two cases make a tension visible that DeFi will meet more and more often: how far should agentivity be allowed to rise, and at what point should the constitution of the system be reinforced instead?

This is no longer just a UX question. It is monetary, institutional, and operational.

Morin: no local limit abolishes the systemic problem

This is where Morin helps us avoid two symmetrical naïvetés.

The first would be to believe that more design, more limitations, and more explicit permissions are enough to solve the issue.

The second would be to conclude, conversely, that the mere presence of another layer makes everything suspect.

Morin forces us to hold two truths together.

Yes, we need limits. Yes, we need bounded permissions. Yes, we need legible architectures.

But no local bound, no elegant module, no isolated proof of integrity abolishes the ecology of action. A system can be well designed at the local level and still produce unexpected systemic effects: mimetic behavior, routines of overconfidence, new dependencies, procyclical coordination, misread incentives, collective blind spots.

So the question is not only: was the action authorized? It is also: what does the multiplication of these actions produce inside an environment populated by tools, dashboards, agents, and users who are not all seeing the same world?

Verifiability: a valuable aid, not a substitute for judgment

It is perfectly natural that calls for sovereign AI and verifiable AI resonate in web3. They speak a familiar language: control, integrity, proofs, the reduction of blind trust.

That direction matters. It can make certain delegations more legible, more attestable, more contained.

But the hierarchy of problems has to remain intact.

Verifiability does not replace common sense. It does not decide for us what should have been delegated in the first place. It does not guarantee that systemic effects will be desirable.

Proofs, logs, limits, action policies, and cryptographic primitives can improve the integrity of certain operations. They do not relieve us of defining the mandate, accepting the limits, or answering for the uses.

Control, integrity, measure

What is rising in web3 is not illegitimate. The point is to keep the order of problems clear.

Sovereign AI

Addresses the question of control: where the system runs, who depends on whom, what data leaves the perimeter, and which permissions are actually in play.

Verifiable AI

Addresses the question of integrity: what can be attested, reviewed, proved, or reconstructed.

But measure remains decisive

Neither of these directions removes the need to answer the harder question: what should be delegated, within which limits, and with what possibility of taking back control? Mathematics and cryptography can make certain operations more attestable; they cannot replace judgment, responsibility, or the ecology of action.

A minimal grid for evaluating an assisted or agentic DeFi tool

Before using a dashboard, wrapper, copilot, agent, or third-party service, it is worth running it through a simple filter.

1. What kind of thing is it?

A protocol, an interface, a third-party tool, an agent, or simply a visualization layer?

2. How far does it intervene?

Does it inform, recommend, prepare an action, or actually act?

3. What permissions does it require?

Does it touch a wallet, messages, private data, automations, onchain execution, or external calls?

4. What bounds are explicit?

Amounts, action types, confirmations, delays, allowlists, sandboxing, functional scope?

5. What is actually verifiable?

What can be reviewed, understood, audited, or reconstructed?

6. Is it reversible?

Can you cut the tool off without losing access to the protocol, to the underlying risk, or to your essential capacity to act?

7. Who is responsible for what?

The protocol, the builder, the operator, the user? If the answer is blurry, so is the trust model.

What this series was trying to show

The argument can be stated simply.

Crypto learned how to defend assets against capture. It is now discovering that it must learn to defend, with the same rigor, attention, judgment, organization, and the capacity to act.

The problem will be solved neither by nostalgia nor by acceleration for its own sake.

It calls for more legible protocols, better-bounded tools, less magical architectures, more responsible builders, and users less inclined to confuse new power with quiet abdication.

It also asks for something harder: the willingness to accept that no local proof, no elegant automation, no isolated instance of cryptographic integrity can ever fully replace wisdom about systemic effects.

That is where the most serious continuation of crypto’s promise may now lie.

Not only in protecting what we own. But in learning not to surrender too quickly what still allows us to act.

1. The Next Frontier of Self-Custody

Mon, 13 Apr 2026 11:00:00 +0000

Series opening: Self-Custody, But How Far?

We learned not to leave our assets with custodians. We have not yet learned not to hand our judgment too quickly to new intermediaries.

Crypto began with an intuition that looked technical at first and turned out to be much larger: wherever an intermediary can be removed from the equation, it is usually better to learn how to live without it.

From that intuition came wallets, habits, slogans, and forms of caution. Not your keys, not your coins did more than teach a generation of users to distinguish convenience from control. It changed the way they moved through the digital world.

What has not happened yet is the extension of that discipline to our own faculty for judgment.

We know how to ask where the funds are, who controls permissions, where the points of capture lie. We are far less used to asking where the model runs, what data it sees, how much of our work it absorbs, what it prepares on our behalf, what it saves us from doing, and what kind of dependence takes shape as it becomes hard to do without.

The center of gravity has moved. For years we talked about empires of data. We now have to talk about empires of delegation.

What has actually changed

Web2 mostly captured traces: our clicks, our preferences, our social graphs, our attention.

This moment adds a more intimate layer. AI enters our notes, archives, queries, reading habits, summaries, work routines, information triage, draft formulations, preparatory judgments, and in some cases already parts of action itself.

It is no longer just a tool. It becomes an environment — sometimes a work environment, sometimes a mental one.

And once a tool becomes an environment, the question changes. The point is no longer just whether it is useful. The point is what it reorganizes in us: how we read, rank, remember, anticipate, and decide.

For a web3 reader, that shift is decisive. Trust minimization no longer concerns only assets, contracts, or execution rails. It reaches something harder to preserve: discernment.

A deeply crypto contradiction

This is not really about hypocrisy. The problem is more uncomfortable than that — and more revealing.

Crypto has always been drawn to tools that produce an edge: more speed, more clarity, more informational asymmetry, more capacity to explore, compare, and execute. It makes perfect sense that the space would be among the first to embrace persistent copilots, augmented workflows, agentic layers, and systems that preserve context while compressing time.

So the contradiction is not moral. It is structural.

Two legitimate demands are colliding. On the one hand: do not depend on a trusted intermediary. On the other: gain speed, clarity, and processing power through systems that keep getting stronger.

The first built a culture. The second is beginning to rearrange its habits.

No slogan will resolve that tension for us.

The age of setups

That is why the current fascination with AI setups deserves to be taken seriously.

One builder runs Claude through Telegram. Another has agents pass task state through .md files. A third organizes memory in Obsidian, plugs in search tools, ties the whole thing into coding or research workflows, and starts the day with the sense that the machine has already been working through the night.

None of this is scandalous in itself. But all of it says something precise about the present.

We are no longer looking only for answers. We are looking for continuity.

We want systems that preserve context, reconnect scattered fragments, surface what must not be forgotten, reorder notes, watch what needs watching, prepare the ground, and make us feel that part of the work has already been done before we even sit down.

That promise is powerful. It is also exactly where sovereignty has to be rethought.

The question is no longer only whether a tool is spying on us. We also have to ask what it is taking over inside our relation to the world: memory, monitoring, pre-sorting, classification, recombination, the first movement of discernment. These operations look secondary — until we realize they already shaped a decisive part of the way we act.

Morin, or the useful bad news

This is where Edgar Morin becomes newly useful.

Morin forces us to think together what we would rather keep apart: autonomy and dependence, local power and systemic effects, service rendered and gradual dispossession. Applied to AI, the lesson is severe but clarifying: a tool of augmentation can become an infrastructure of relinquishment without ever ceasing, locally, to be useful.

The danger does not necessarily arrive as a visible catastrophe. More often it settles in under the appearance of comfort.

You notice quickly when you left your funds with a dubious custodian. You notice later when you have outsourced too much of your reading, your memory, your sense-making, or the preparation of your decisions.

Cognitive dependence rarely looks like coercion. More often it looks like help that has become second nature.

The issue is not only the models. It is also the surrounding software.

The problem cannot be reduced to frontier models, major labs, or the opposition between local and cloud.

It also concerns the environment AI is helping to proliferate around protocols: dashboards, wrappers, research tools, specialized assistants, monitoring layers, coordination services, micro-products built quickly — sometimes carefully reviewed and robust, sometimes not.

We need to be precise here. Using AI to build software is not, in itself, a problem. Not every AI-assisted build is vibe coding in the strong sense.

The issue begins elsewhere: when the cost of producing a service falls much faster than the cost of reviewing it, understanding it, and qualifying it.

At that point we do not just have more tools. We have more surfaces of trust to evaluate.

And in web3, where a dashboard, an interface, or a copilot can shape a risk reading, an allocation, a signature, or an execution path, that shift matters a great deal.

What this first piece wanted to make visible

The question, then, is not whether AI is compatible with web3 culture. It already is — almost too well.

The real question is more awkward: can crypto extend to cognition, organization, and action the same demands for sovereignty it learned to formulate for assets?

We now know where the fault line runs. A culture of self-custody that never asks what it is handing over to cognitive intermediaries may end up missing the most important stage of its own development.

The next piece starts from there: how to recover a discipline of delegation firm enough to matter and simple enough to use.

Intro: Self-Custody, But How Far?

Mon, 13 Apr 2026 10:00:00 +0000

Crypto taught itself not to leave assets in someone else’s hands. The next question is whether it can bring that same discipline to judgment, organization, and eventually to action itself.

Why this series

Crypto proved something essential long before most of the digital world was ready to hear it: when you can remove an opaque intermediary, you usually should.

That instinct gave us wallets, habits, slogans, and architectures. Over time it gave us something larger than tooling: a culture. Self-custody. Trust minimization. Resistance to capture. An insistence on clear permissions and visible points of control.

And yet something is shifting as AI becomes ordinary.

The same circles that learned to distrust intermediaries around assets are now increasingly willing to hand over their notes, reading habits, research workflows, contextual memory, preparatory judgments — and soon parts of their ability to act — to systems they do not fully understand and do not really control.

So the problem is no longer just data. It is delegation.

That is the real turn. Crypto already knows how to ask the right questions when money is involved: who controls what, who holds the keys, where the capture points sit, which trust assumptions are being accepted.

What remains uncertain is whether that rigor can be extended to thought, to organization, and to the conduct of action.

What these essays are after

We learned self-custody for assets.

We still have to learn it for judgment.

That is the thread running through these three pieces.

The first names the contradiction: we are not only living in the aftermath of Web2 and its empires of data. We are moving into a world where empires of delegation are beginning to take shape.

The second tries to recover a workable discipline. AI is no longer just an answer engine. It is becoming a work environment, a contextual memory, an organizational layer, and in some cases already a preparation for action.

The third explains why DeFi is one of the first places where this question can no longer be postponed. Sooner or later, every delegation shows up as a permission, a limit, a risk, or an architecture.

Edgar Morin is the quiet philosophical thread behind the series. Not as borrowed authority, but as a way of reading the moment: hold together autonomy and dependence, local power and systemic effects, genuine service and gradual dispossession. In other words, learn how to think in a complex environment without pretending that a local fix will settle the whole matter.

What this series does not promise

Not a universal stack. Not a new form of digital purity. Not a lazy indictment of AI.

It aims at something more useful: a way of telling apart what can be delegated, what should remain under direct control, and what we should now demand from the tools we let into our practice.

The three pieces

1. The Next Frontier of Self-Custody

The diagnosis: what AI is actually changing inside a culture that thought it already knew what digital sovereignty meant.

2. Delegate Without Handing Yourself Over

The practical and philosophical core of the series: how to distinguish assistance from delegation, and delegation from abandonment — then recover a discipline strict enough to matter and simple enough to live with.

3. DeFi as a Laboratory of Delegation

The proving ground: dashboards, wrappers, agents, vibe coding — and then two contrasting cases, Money League and Polaris, that make the problem impossible to miss.

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.

Pharos Is Becoming the Stablecoin Observatory This Market Has Been Missing

Fri, 20 Mar 2026 00:00:00 +0000

Pharos Watch

What started small is turning into something much more important

I first came across Pharos when it was still a very early stablecoin dashboard that @TokenBrice had started building almost on the side, alongside everything else he was working on, while learning Claude Code.

At the time, it was easy to see it as an interesting side project.

What was harder to see then, but feels much clearer now, is that it was also the early shape of something the market genuinely needs.

Not just another dashboard.

Not just another interface for checking prices, market caps, or whether a peg is still holding.

Something closer to an observatory: a way of looking at stablecoins that makes the market easier to understand on its own terms.

Stablecoins have scaled faster than the tools used to understand them

The stablecoin market has become far more important than the analytical layer built around it.

That gap is starting to matter.

For a while, people could get by with rough intuition, a few scattered dashboards, some issuer docs, and a general sense of which assets felt solid and which ones did not.

That kind of workflow is no longer enough.

Not because there is too little data, but because there is too much of it, too unevenly organized, and too rarely assembled into a coherent picture.

What’s still missing isn’t raw information so much as a way of reading stablecoins as fully-fledged monetary systems: with their dependencies, their constraints, their blind spots, and their particular failure modes.

That’s precisely where Pharos is beginning, in my view, to earn its place.

Most stablecoin analysis still happens in pieces

Even now, most people analyze stablecoins through a workflow that is more improvised than they would probably like to admit.

A broad dashboard.

A Dune query.

A few issuer materials.

A thread on X.

Some half-formed conviction that one coin is safer, cleaner, or more decentralized than another.

Then those fragments get stitched together mentally and passed off as analysis.

That approach was always somewhat fragile.

It looks even weaker now that the market has become larger, more layered, and more systemically relevant.

Because stablecoin risk is no longer reducible to a simple question like: is it on peg right now?

It also lives in liquidity quality, dependency chains, blacklist and freeze exposure, redemption credibility, concentration risk, contagion channels, and the practical conditions under which exit is actually possible.

Once you start looking at the market that way, surface monitoring is not enough anymore.

You need tools that help make underlying structure visible.

What Pharos changes is not just the amount of data, but the way the problem appears

That, to me, is the most important thing about Pharos.

Its value is not simply that it gives you more information. Plenty of products can do that.

What matters is that it starts to reframe the problem in a way that feels much closer to how the market actually works.

It makes stablecoin structure easier to see.

And that is a very different thing from building one more analytics interface.

Most dashboards still leave the conceptual work to the user. You look at one chart, then another, then another, and you do the synthesis yourself.

Pharos is starting to do something different. It tends to turn a fragmented reading into something more structured, more continuous, closer to a genuine situational overview of the stablecoin world.

That is why it feels like more than a tool.

It feels like the early formation of a category.

It makes dependency risk much easier to read

One of the hardest things about stablecoin analysis is that apparent stability often hides upstream fragility.

A stablecoin can look perfectly fine while quietly depending on another stablecoin, on centralized collateral, or on a redemption mechanism that only reveals its weakness under stress.

If your workflow is too shallow, or too scattered, that kind of dependency is easy to miss.

Pharos helps make it much harder to miss.

And once that layer becomes more visible, you stop reading stablecoins as isolated units. You start reading them as constructions built on top of other constructions.

That is a much more serious way of understanding where fragility may actually sit.

Shifting the focus: from the peg to the exit

This matters just as much.

A peg is useful information, but it is not the same thing as monetary robustness.

The question that really matters, especially under stress, is whether you can exit — through what route, with what depth, with what slippage, and under what operational constraints.

Can you redeem?

Can you move size?

Can you unwind without discovering that the liquidity profile was thinner or more conditional than it looked?

That is where stablecoins stop being mere price objects and start revealing themselves as monetary instruments with different structural properties.

Pharos helps frame them that way.

And that shift in framing is important.

Because a stablecoin that looks stable on screen may still offer a very poor exit when conditions deteriorate.

Treating censorship exposure as a central element

This is another area where a lot of market commentary still feels strangely incomplete.

When a stablecoin can be frozen, blacklisted, or operationally constrained across multiple chains, that’s not a secondary detail.

What matters is not only what the token tracks, or how it is collateralized, but also what kinds of control can be exercised over it.

That includes technical restrictions, issuer discretion, dependence on centralized rails, and more broadly the permission architecture surrounding the asset.

Pharos appears to treat this reality as part of the main analytical framework, not as a footnote.

That, again, is the right approach.

Seeing the pressure build before the break

One of the real tests for a tool like this is whether it helps people see stress before a breakdown becomes obvious to everyone.

Not after the event, when the narrative has already formed.

Before.

When pressure is still building in ways that are easy to ignore.

When liquidity starts thinning.

When a dependency that looked manageable becomes more dangerous.

When concentration rises or exit routes quietly narrow.

That is where an observatory becomes more than a dashboard.

It becomes a way of detecting pressure while it is still forming.

And as the market becomes more layered, that function becomes more important.

Giving memory back to a market that forgets quickly

This matters more than it may seem at first.

Most dashboards track what is alive, active, in circulation. They’re naturally oriented toward the present market.

Pharos also tracks what failed.

That is important because stablecoin markets are often much more forgetful than they should be. Patterns that were already visible in previous failures tend to return in slightly altered form and get discussed as if they were new.

A market with weak memory tends to misread recurring risk.

So this is not just archival work. It is part of analytical discipline.

Remembering failed designs, broken pegs, and past stress dynamics is part of what makes present structures easier to interpret.

In that sense, memory is not supplementary. It is part of market intelligence.

Stablecoins no longer belong to one simple category

This is perhaps, in depth, the main reason a project like Pharos is becoming important right now.

Stablecoins no longer constitute a homogeneous category.

They are diverging across reserve models, collateral types, governance systems, chain environments, reference units, and use cases.

That means older, flatter ways of talking about the category are becoming less useful.

It is no longer enough to ask:

Which stablecoin is biggest?

More and more, the better question is:

What kind of monetary system does this design actually produce?

That question is harder, but it is also much closer to the real substance of the market.

It pushes attention away from rankings and toward structure.

Away from surface metrics and toward monetary form.

Why I no longer think of Pharos as just a useful dashboard

That is why I no longer see Pharos as just another useful stablecoin dashboard anymore.

The description isn’t wrong. It’s just become too narrow.

What it is becoming — or what it seems to be moving toward — is the stablecoin observatory this market has been missing.

Not because it replaces everything else.

It does not.

@DefiLlama still matters.

Dune still matters.

Issuer documentation still matters.

X still matters too, in its own chaotic way.

But Pharos is beginning to occupy a different place in that ecosystem.

It is trying to make the market legible as a field of monetary designs: structures with distinct dependencies, constraints, and failure modes.

That is what makes it interesting.

And that is why I think it deserves close attention.

Why this function will matter more and more

This function should only grow in value in the period ahead.

As stablecoins become more central to crypto infrastructure, and more varied in design, the need for a serious analytical layer will grow with them.

If the category expands beyond a handful of dominant dollar wrappers into a broader field of synthetic assets, commodity-linked instruments, protocol-native monetary designs, and institutionally issued stablecoins, then the old workflow becomes even less adequate than it already is.

At that point, access to price data is trivial.

What matters is the ability to read structure.

To see where fragility is being displaced.

To understand whether stability is robust, conditional, borrowed, or mostly cosmetic.

To know what really sits underneath the surface.

That is why Pharos feels timely.

Not because it is one more useful tool.

But because it may be one of the first serious attempts to build the layer of understanding this market increasingly requires.

What feels most interesting now

At this stage, the most interesting thing may not be only what Pharos already does.

It may be what it points toward.

If stablecoins are becoming a more complex monetary environment, then they will need better ways of being observed, compared, and understood as systems.

That is where Pharos appears to be heading.

And that is why it is worth watching closely.

DeFi 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

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

3. DeFi as a Laboratory of Delegation

In DeFi, an idea quickly turns into a permission, a risk rule, or a signature.

The protocol no longer sums up the system

What AI changes materially

Vibe coding: not a scandal, a reveal

Two protocols that make the problem legible

Money League: pushing the agentic horizon further

Polaris: returning to the question of constitution

What they show together

Morin: no local limit abolishes the systemic problem

Verifiability: a valuable aid, not a substitute for judgment

What this series was trying to show

1. The Next Frontier of Self-Custody

We learned not to leave our assets with custodians. We have not yet learned not to hand our judgment too quickly to new intermediaries.

What has actually changed

A deeply crypto contradiction

The age of setups

Morin, or the useful bad news

The issue is not only the models. It is also the surrounding software.

What this first piece wanted to make visible

Intro: Self-Custody, But How Far?

Why this series

What these essays are after

What this series does not promise

The three pieces

1. The Next Frontier of Self-Custody

2. Delegate Without Handing Yourself Over

3. DeFi as a Laboratory of Delegation

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

Pharos Is Becoming the Stablecoin Observatory This Market Has Been Missing

What started small is turning into something much more important

Stablecoins have scaled faster than the tools used to understand them

Most stablecoin analysis still happens in pieces

What Pharos changes is not just the amount of data, but the way the problem appears

It makes dependency risk much easier to read

Shifting the focus: from the peg to the exit

Treating censorship exposure as a central element

Seeing the pressure build before the break

Giving memory back to a market that forgets quickly

Stablecoins no longer belong to one simple category

Why I no longer think of Pharos as just a useful dashboard