# ERC-8330 returns to Review with a changed NAV aggregation interface

Canonical: https://forkbrief.com/news/ea1dc8bd-8d5f-41a7-9a82-b8c520fecc91
Published: 2026-10-30T04:49:47.312Z
Publisher: Fork Brief

The October 27 revision changes the proposed aggregate return layout and requires a fresh quorum at query time. An October 29 follow-up explains the compatibility consequence.

An [October 27 revision](https://github.com/ethereum/ERCs/pull/2116) returned proposed ERC-8330 from Last Call to Review and changed its optional net asset value aggregation interface. In an [October 29 follow-up](https://ethereum-magicians.org/t/erc-8330-subject-linked-nav-snapshot-oracle/28939/11), the discussion's author detailed a compatibility issue: `aggregatedNAV(bytes32,bytes32)` keeps its function selector even though the returned data layout has changed.

### The return layout changes

The [revised specification](https://github.com/ethereum/ERCs/blob/cc7f5495b4457cfdfd3b852df9d9c6718cfe2f24/ERCS/erc-8330.md) returns six values: `(nav, decimals, navBasis, valuationTimestamp, freshProviderCount, isValuationStale)`. It removes the former aggregate `isPublishStale` field and changes the aggregation interface's ERC-165 identifier.

That difference matters when decoding an older deployment's response. The specification says a client using the revised decoder can read the older publication-staleness flag as the new valuation-staleness flag and ignore the older trailing value. It therefore requires checking support for this revision's aggregation interface before decoding. A successful call alone does not establish compatibility.

### Freshness is checked when queried

Only eligible provider submissions whose publication time is within `maxSubmissionAge` of `block.timestamp` contribute to the aggregate. This window is separate from the stream's publication heartbeat.

The latest aggregation timestamp is the greatest valuation timestamp with a historical quorum of eligible submissions. Under the revision, that timestamp must also retain a fresh quorum when queried. Otherwise `aggregatedNAV` reverts, without falling back to an older valuation timestamp.

As submissions age out, the contributing set can shrink and its lower median can change while quorum remains. Once fresh quorum disappears, the aggregate becomes unavailable. Recent publication and recent valuation remain separate: a returned aggregate can still report `isValuationStale = true`.

The change concerns a Review-stage ERC interface, with aggregation optional. The document standardizes reported valuation data; it does not calculate NAV or establish an executable market price.

## Sources

- [ERC-8330: Subject-Linked NAV Snapshot Oracle: author follow-up, post 11](https://ethereum-magicians.org/t/erc-8330-subject-linked-nav-snapshot-oracle/28939/11) — Ethereum Magicians / redcoat, topic author
- [Update ERC-8330: Move to Review](https://github.com/ethereum/ERCs/pull/2116) — Ethereum ERCs repository
- [ERC-8330: Subject-Linked NAV Snapshot Oracle, Review revision at cc7f5495b4457cfdfd3b852df9d9c6718cfe2f24](https://github.com/ethereum/ERCs/blob/cc7f5495b4457cfdfd3b852df9d9c6718cfe2f24/ERCS/erc-8330.md) — Ethereum ERCs repository

- [Editorial policy](https://forkbrief.com/editorial-policy)
- [Request a correction](https://forkbrief.com/corrections)