Methodology

Methodology how a feed status and a feed verdict are computed

Every figure on FeedPlumb comes from public chain reads with fixed rules. This page states the rules, so you can reproduce any result.

Feed status on the boards

Fresh
The feed's last update is no older than 1.5 times its heartbeat.
Stale
The last update is older than 1.5 times the heartbeat. The heartbeat is the oracle's published one or, when none is published, the one FeedKit assumes (shown as assumedHeartbeatS in the data).
Reverting
latestRoundData() on the proxy fails, so no round can be read.
Source
eth_call on the feed proxy and its aggregator through public RPC endpoints. The snapshot file carries the time it was generated.

Feed Watch (health and incidents)

Feed Watch reads every feed about every 2 minutes and marks it stale when the last update is older than its heartbeat plus 10 minutes. It also flags deviations from a reference price, reserve drops, NAV moves and config or owner changes. The full rules are on Feed health.

Feed verdict (API)

Status
reverting if latestRoundData() fails; stale if block time minus updatedAt is more than maxAgeS (default 86,400 s, settable from 60 s to 30 days); otherwise fresh.
Pass
Only if the status is fresh, the answer is above 0, answeredInRound is at least roundId, and updatedAt is not in the future.
Warnings
A single-oracle quorum (minSubmissionCount below 2), fewer oracles than the maximum, or another proxy for the same pair that is fresher.
Not returned
The verdict does not return the feed's price value.

The verdict uses one time limit (maxAgeS) so callers can choose it; the boards use the heartbeat rule above. The two can differ for the same feed.

Proof bundles and receipts

Digest
A feedplumb-proof/v1 bundle carries the SHA-256 digest of its canonical JSON. Anyone can recompute it.
Merkle proof
Where a bundle has one, the leaf hash is combined step by step with the listed sibling hashes (SHA-256) and must equal the stated root.
Signatures
Answers are not signed yet. When signing starts, the public keys are listed on Signing keys. Check any record on the record checker.
Where to check
In your browser on /verify/, or with POST /verify/v1/bundle (0 credits).

What we do not check

Data sources per chain

RPC endpoints
ChainPublic RPC endpoints, in fallback orderOracle providers read
XDC Networkhttps://erpc.xinfin.network, https://rpc.xinfin.network, https://erpc.xdcrpc.complugin
Basehttps://mainnet.base.org, https://base-rpc.publicnode.comchainlink

Operational data from public blockchain sources. Nothing on this page is financial, legal or tax advice.