Regenerate data feeds bindings for 32-byte ids and batched reads - #187
Closed
Fletch153 wants to merge 12 commits into
Closed
Regenerate data feeds bindings for 32-byte ids and batched reads#187Fletch153 wants to merge 12 commits into
Fletch153 wants to merge 12 commits into
Conversation
The DON transmitter reads every feed's latest state each round to gate on deviation and heartbeat; single-feed reads would cost one consensus call per feed. latest_round now takes a Vec of ids and returns an Option<RoundData> per id. Page sizing is the caller's concern; the host's own budget and footprint limits bound oversized calls either way. The cache no longer cares about freeze on any read path: it holds state and serves it raw, exposing only the is_frozen flag. The proxy decides: every consumer read is prefixed with an is_frozen check that fails with the same FeedFrozen error as before. The check costs no extra ledger reads since every reader loads the feed_state entry holding the flag anyway. Freezing blocks consumer reads, never DON writes, so the transmitter keeps reading and writing frozen feeds. Self-upgrade wasm fixtures are rebuilt.
The mock cache derived its latest round from an injected round list with its own max-by-round-id logic, a transcription of cache behavior that could silently drift from the real contract. Tests now inject the exact RoundData the cache would return for latest_round, and the freeze flag is injected explicitly for is_frozen, so the mock holds answers rather than reimplementing cache logic.
Collaborator
Author
|
Superseded, regenerating directly on PR 162's branch |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Context
The cache readers now take a vector of 32-byte opaque ids and answer per id (chainlink-stellar #182 and #183). The Go bindings and the embedded deployment wasm still spoke the old single-id, 16-byte interface.
Changes
Testing
Notes