Chainlink · Chainlink aggregators

JTRSY.nav

JTRSY NAV

0x0C2e4Df738e99e8db80012f5bb2a303f3f48Ca74Copy address

217 round(s) by 18 transmitter(s), 0 at minAnswer or maxAnswer, 0 gap(s) above the heartbeat, liveness LIVE, posting path replayed

Family

chainlink-aggregator

Chain

Ethereum mainnet (1)

Guard

min and max

bound scale

0

kind

min_max

max answer

maxAnswer()

min answer

minAnswer()

threshold percent

1e-7

max silence seconds

100800

moves above threshold

97

silences

0

at bound posts

0

clamped posts

0

override flags

0

reference moves

0

unguarded reference moves

0

log addresses

0x009b8b4D648cFCC813ecB70db0f31ce305DD4B32

Mechanism

Chainlink Data Feeds (NAVLink, Proof of Reserve): an EACAggregatorProxy in front of one OCR aggregator per phase. A round is written by an OCR transmit of the network's transmitter set (a quorum of node operators signing the issuer's or auditor's figure), never by an issuer key; the aggregator clamps nothing but rejects a median outside minAnswer..maxAnswer, so an answer exactly on either bound is the range limit, not the market (class D, aggregated). Rounds are read from AnswerUpdated on every phase aggregator with the transmitter taken from NewTransmission of the same transaction (the OCR2 and the OCR1 layout both carry it in the second data word); the feed directory's heartbeat (plus one hour of grace) bounds the silence between rounds and its deviation threshold classifies the moves. Left out on purpose: M NAV (0xC28198Df, M^0), a high-frequency feed with over 76,000 rounds whose aggregator emits NewRound without a transmitter. The proxies' AggregatorConfirmed events are swept as notices; none was found on these proxies through the explorer, so the phase history is the log_addresses list read from phaseAggregators().