Scope

Coverage matrix

Exactly which middle-office fields Autonom signs today, per asset class. The point of this page is the unmarked cells: where there is no “covered” or “planned”, Autonom is not the right system and you should not infer otherwise from a clean dashboard elsewhere.

Field

Tokenized treasuries

BUIDL, OUSG, USDY, USTB

Tokenized commodities

PAXG, XAUT

Stablecoins

USDC, USDT, PYUSD

Private credit

Maple, Centrifuge, Goldfinch

Real estate

Tokenized buildings, REIT wrappers

NAV per token

Net asset value per token, signed at issuer-published cadence.

Stablecoins by design hold $1; we sign supply and reserves instead of NAV.

covered

—

covered

planned

AUM / on-chain supply

Total value of the underlying pool, signed.

covered

planned

Secondary market price

Last trade on a venue, separate from NAV.

For commodities and treasuries with a secondary market. Private credit and real estate generally lack a continuous secondary venue.

covered

planned

—

Realized yield (APY)

Trailing 30d or issuer-published annualized yield.

covered

—

planned

—

Holder count

Distinct addresses holding the token, across all deployed chains.

covered

planned

Cross-chain distribution

AUM split by deployment chain.

covered

planned

Per-holder tax lots

Cost basis and lot tracking at the holder level.

Belongs to the holder’s custodian or accounting system; not an oracle’s job.

—

Reserve attestation

Signed snapshot of the off-chain backing (gold bars, T-bills, USD).

For commodities and stablecoins, we republish issuer/auditor attestations. For treasuries, the fund structure is the attestation — we sign the fund’s reported AUM instead.

planned

covered

—

Reserve composition

Breakdown of the underlying pool by instrument and maturity.

planned

—

Audit / PoR proof

Cryptographic proof that reserves match supply (e.g. Chainlink PoR).

—

planned

—

Distributions / coupons

Per-event amount and ex-date, surfaced as CAF/DAF entries.

covered

planned

—

planned

—

Mint / redeem events

Issuer-side primary market activity.

Requires either transfer-agent integration or on-chain mint/burn indexing per token.

planned

—

Rebase / split events

Multiplicative supply adjustments tracked as CAF on the registry.

covered

—

NAV resets / rollovers

Fund-cycle NAV crystallizations and rollovers.

covered

—

planned

—

Loan-level performance

Per-loan IRR, current status, recovery, write-offs.

Requires loan-administrator integration. Not in scope.

—

Covenant compliance

Live tracking of loan covenants (DSCR, LTV, reporting timeliness).

—

Default & recovery data

Default events with recovery percentage and waterfall application.

—

Wrapper / jurisdiction

Legal wrapper (Reg D, Reg S, UCITS, etc.) and domicile.

Reference data, not enforcement. We tell you it’s Reg D — we do not check whether your purchase was Reg-D-compliant.

covered

Transfer restrictions

KYC allowlists, lockups, jurisdictional gates enforced at transfer time.

Enforced by the token contract. An oracle observes; it does not enforce.

—

Collateral eligibility

Per-asset acceptability and haircut for use as collateral.

Decided by each downstream consumer (perp DEX, lending protocol). We provide the inputs (NAV, freshness, divergence). The decision is theirs.

—

Occupancy & rent rolls

Tenant occupancy, rent paid, vacancy, lease terms.

—

Property appraisal

Independent valuation of the underlying property.

—

Why some columns are mostly empty

Private credit and real estate are not under-served because nobody wants the data — they're under-served because the data doesn't exist in a form an oracle can sign. Loan-level performance lives in a loan administrator's system. Property valuations live in appraiser PDFs. There is no public API to republish.

The honest position is that Autonom solves the verifiable reference data problem for assets that already have published, machine-readable data. That covers tokenized treasuries, commodities, and stablecoins today, and most of money-market-like private credit with issuer cooperation. Real estate and bespoke private credit require partnership work an oracle alone can't do.

What “covered” means

· Signed by an Autonom operator key
· Tagged with a kid and timestamp the consumer verifies
· Mirrored to the on-chain registry where the field supports it
· Has a documented freshness budget and goes stale visibly
· Cross-checked against at least one independent source when available

Full methodology →