Three commitments. One arc.
Each initiative graduates the previous one. The wedge earns the trust the second initiative needs to underwrite risk; the underwriting earns the legitimacy the third initiative needs to publish a standard. None of them launch out of order.
Routescore
A decision-support workbench for decentralised finance.
Routescore scores the swap route a user is about to take against four alternatives in real time. It surfaces the cost of the route, the MEV exposure, the historic sandwich rate of the pool, and the tail-risk band of the scenario. It does not execute the trade. The user keeps custody, the user takes the decision, the user gets back a signed record of why.
The product is read-only and non-custodial by construction. The cron that produces the underlying scanner data is published every night with a version-controlled methodology and a hash of the manifest. The benchmark page renders the methodology and the live numbers side by side so that any reviewer can verify, months later, that the answer they were given was honest.
Routescore is the wedge. Its job is to be useful enough that real people pay for it, while the public artefacts it produces — the MEV Loss Index, the open quote-diff scanner, the oracle dependency map — earn the institutional trust the next initiative needs.
Cover Bonds
Parametric refunds for the harms we already measure.
When Routescore has been measuring an exposure for long enough that the loss distribution is empirically known, the next step is to underwrite against it. A user pays a small premium each cycle; if the measured harm crosses a published threshold, the user receives an automatic refund. No claims process. No discretion. The methodology that defines the trigger is the same methodology Routescore publishes on the benchmark page.
We are deliberately deferring this initiative until the underlying measurement has been audited in public for at least eighteen consecutive months. The whole product depends on the methodology being trusted by counterparties we do not yet have. Until that trust exists, the product cannot exist.
The first three covers will be MEV exposure, bridge failure, and restaking slashing. Each has a measurement engine inside Routescore today and a buffer simulator that has already been tested in shadow mode.
Open Standards
A neutral standards body for measurable risk.
When the measurement is trusted and the underwriting is trusted, the obvious next step is the rule book. Phase 3 is the institution we want Empyrean to become — the place that publishes the open methodology every other protocol can adopt, audits the protocols that adopt it, and runs the marketplace where third-party underwriters can sell cover on the same rails.
We are deliberately walking toward this position. We are not declaring it now. The legitimacy of a standards body is earned in the years before it exists, not assigned at incorporation. Phase 3 is the test of whether the previous two phases have done their work.
When it arrives, it looks like this: protocols publish Empyrean-compatible risk metrics; users see the compliance grade before they deposit; underwriters bid on the same parametric covers using the same data feed; Empyrean is the clearing layer, not the monopoly.
Each phase needs a different shape of person.
Phase 1 needs measurement engineers, design partners, and the kind of operator who can ship a public artifact every week without flinching. Phase 2 needs underwriters. Phase 3 needs the institutional architects who have done this work before for slower industries.