We would like feedback on ERC-8330 — Subject-Linked NAV Snapshot Oracle, a draft ERC for publishing and querying provider-attributed Net Asset Value snapshots for application-defined subjects.
Update — July 09, 2026: ERC number has been allocated. The ERC remains in Draft status and may change based on review.
Formal ERC PR: ethereum/ERCs#1858
Spec file: ERCS/erc-8330.md
Periodic NAV for funds, private credit, real estate, infrastructure, commodities, and other illiquid or administratively priced assets differs from a continuous market-price feed. A consumer needs to know what the value represents, its denomination, when the valuation was measured, when it was published, who supplied it, which methodology was used, and whether either time is too old for the intended use.
Each stream is keyed by (subjectId, currency) and has one immutable configured NAV basis: per underlying unit, per share or token, or total subject value. Configuring the basis at stream level prevents providers from submitting incomparable interpretations into the same aggregation set.
The core interface provides:
- signed NAV with explicit decimal precision;
- provider and methodology attribution;
- distinct valuation and publication timestamps;
- one original provider submission per valuation timestamp;
- linear correction chains;
- administrative invalidation that preserves history;
- stream-wide and provider-specific latest-value queries; and
- independent publication-heartbeat and valuation-age status.
Invalidation is separate from correction because a compromised, revoked, or unavailable provider may be unable to correct a poisoned terminal snapshot. Invalidating a terminal correction restores its direct predecessor as current and allows a replacement correction, while retaining every historical record and invalidation event.
An optional aggregation interface selects the greatest valuation timestamp that currently satisfies quorum, normalizes provider values to common decimal precision, and returns the deterministic lower median. It also exposes eligible provider submissions and emits deviation alerts. Aggregation does not prove provider independence or valuation correctness.
Scope boundaries
ERC-8330 standardizes publication and query semantics. It does not:
- calculate or independently verify NAV;
- credential providers or validate methodologies;
- establish asset ownership or backing;
- guarantee liquidity or redemption rights;
- make NAV an executable market price; or
- ensure that a consuming contract checks staleness or aggregation results.
latestNAV deliberately exposes the raw latest current snapshot. Staleness-sensitive consumers should use latestNAVStatus, an aggregate, or a controlled adapter and evaluate both age signals.
Questions for review
-
Is immutable stream-level NAV basis the right safeguard against incomparable provider submissions?
-
Are provider-and-valuation uniqueness plus linear corrections sufficient for restatement history?
-
Is administrative invalidation necessary for compromised-provider recovery, and are predecessor-restoration semantics understandable to consumers?
-
Should publication age and valuation age remain separate mandatory signals?
-
Is the lower median the appropriate deterministic aggregation rule, especially for even provider counts and signed values?
-
Should aggregation remain an optional interface, or is it central enough to belong in the core?
-
Does the term “oracle” communicate the interface accurately given the explicit distinction between reported NAV and executable price?
Implementation status
A Solidity reference implementation and test suite is available in the reference repository.
An example UI suite is also available for non-normative exploration of the interface and its role in the broader titled-asset standards family.
The audited reference commit is caa9b05. It includes unit tests, Medusa property tests, deterministic aggregation, and invalidation coverage. The implementation has also been reviewed in an independent Verichains audit.
ERC-8330 is independently deployable and does not require a particular token or vault standard. It was introduced alongside five other standalone draft ERCs in the architecture discussion, but those interfaces are not dependencies.
Authorship
Chris Turner, David Hay (LinkedIn), Reagan Simpson, and Collins Musyimi.
Developed at Kula, which builds infrastructure for regulated virtual-asset and titled-asset use cases. Reference implementations are open-source; we are proposing ecosystem interfaces, not a Kula-only stack. We are open to additional co-authorship and community contribution beyond Kula.