Adapter registry

Model: hybrid. Anyone can deploy an adapter conforming to one of the five interfaces and register it. The registry does not gate what exists. It attaches discoverability and trust metadata so market creators and borrowers can make informed decisions.

AdapterInfo

enum AdapterType { ASSET, ORACLE, COMPLIANCE, LIQUIDATION, POSITION }
 
struct AdapterInfo {
    address adapterAddress;
    AdapterType adapterType;
    address registeredBy;
    bool verified;           // audit sign-off only
    bool deprecated;
    string auditReference;
    uint256 registeredAt;
    uint256 totalValueSecured; // TVL through markets using this adapter
}
 
struct AdapterMetadata {
    string name;
    string version;           // semantic version supplied by developer
    address developer;
    string category;
    string supportedAssets;
    string documentationURI;
    string repositoryURI;
    string auditURI;
    ReviewStatus reviewStatus; // UNREVIEWED, IN_REVIEW, APPROVED, REJECTED
    uint256 usageCount;
}

Use getAdapterInfo(adapter) for compatibility fields and getAdapterMetadata(adapter) for the developer-facing catalog record. Usage is reported by the configured protocol reporter, not by arbitrary callers.

Lifecycle operations

Review meaning

A Verified mark means governance reviewed the committed source, tests, dependencies, and assumptions against the verification policy. It is a time-bounded trust signal, not insurance, an audit guarantee, or a claim that the adapter is economically safe. A Rejected status records a review outcome and reason reference; the developer may fix the findings and submit a new review. A Deprecated status blocks new market selection but does not retroactively change existing markets.

Reference adapters