Registries

Registries are simple on‑chain catalogues. They publish a cryptographic fingerprint of every facet, oracle, router or factory configuration so the rest of the protocol can answer two questions at any moment: who published this item and has it been approved by the DAO? A registry never blocks a contract call. It only stores information that front‑ends, analytics, and governance can consult to verify the trustworthiness of the component.

Two-Path Model

All items first appear in the permissionless registries. Any address may submit an entry, and the transaction is final as soon as it is mined. Because no review is required, builders can deploy a new strategy facet and reference it in a live vault on the same day. Interfaces that prioritise safety treat these entries as experimental. They are meant to be hidden by default, and shown only when a user explicitly opts‑in to "unreviewed code".

When an item has been audited and a DAO vote confirms the findings, the identical identifier (the hash of its byte‑code or static config) is copied into the DAO‑approved registry. From this moment on nothing about the contract itself changes. Third‑party applications may surface it as part of the default “green list.” The DAO‑approved registry therefore acts as an overlay that labels existing items rather than re‑deploying or upgrading them.

The goal of this approach is three-fold:

• Innovation without delay. Developers can experiment freely in the permissionless track, gathering real‑world data before seeking formal approval.

• Clear safety signals. Users and integrators receive a binary indicator—approved or not—without having to parse audit reports on their own.

• Seamless upgrades. Passing from permissionless to DAO‑approved status involves a single registry write; vaults and shares are unaffected, so liquidity never migrates.

This arrangement keeps the core protocol fully permissionless while still giving frontends, dashboards, and institutional users a straightforward filter for risk.

Recommended use of registries in front-ends

• "Safe mode" – Show only facets whose hash appears in the DAO‑approved registry.

• "Developer mode" – Allow users to opt‑in to permissionless facets, displaying the risk associated with the facet.

• "Conflict check" – Warn when two facets in a vault export the same selector, using registry data to trace the overlap.