Add Stellar DF cache write e2e scenario - #23208
Closed
Fletch153 wants to merge 1 commit into
Closed
Conversation
Fletch153
force-pushed
the
feature/DF-25510-stellar-df-cache-e2e
branch
2 times, most recently
from
August 10, 2026 21:03
eae5312 to
004b43d
Compare
Contributor
|
✅ No conflicts with other open PRs targeting |
- Deploy and configure the Data Feeds cache from the test tree via the chainlink-stellar generated cache client and deployer, permitting the (forwarder, workflow owner, workflow name) tuple to write the feed - Drive the stock stellarwrite workflow with a host-built XDR report payload, then assert the decoded answer and timestamp via latest_round - Make the write workflow cron schedule configurable for faster local runs - Pin chainlink-stellar to the integration branch carrying the cache bindings and embedded Data Feeds artifacts
Fletch153
force-pushed
the
feature/DF-25510-stellar-df-cache-e2e
branch
from
August 10, 2026 21:12
004b43d to
b08e27b
Compare
|
Collaborator
Author
|
Superseded by #23411, which builds on the embedded wasm artifacts upstream and a dedicated data feeds write workflow module. |
Collaborator
Author
|
Successor PR moved to #23412 (branch renamed onto this ticket). |
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 existing Stellar write test proves delivery to a stub receiver. This scenario is the Aptos-parity version for Data Feeds: the receiver is the production cache contract, so it exercises the cache's permission model (allowed sender, workflow owner, workflow name) and its report decoding, not just the forwarder.
The test deploys and configures the cache through the chainlink-stellar generated bindings client. The production deploy path is the Data Feeds changeset suite in chainlink-data-feeds, which this repo cannot import; the helper mirrors its operations for the local environment.
Changes
system-tests/lib/cre/features/stellar/stellar_cache.godeploys the cache with the deployer's constructor-args call, registers the feed admin, sets the feed config permitting the forwarder plus workflow identity, builds the XDR report payload, and readslatest_roundback.executeStellarDFCacheWriteTestdrives the stock stellarwrite workflow with the host-built payload (deterministic, so consensus nodes agree byte for byte) and asserts the decoded answer and timestamp on-chain. Registered in the Stellar suite alongside the existing read and write cases.Testing
Notes
feature/stellar-df-cache-e2e-v2(main plus cache/proxy bindings, scval and deployer additions, and embedded Data Feeds artifacts). It must be re-pinned when that work merges upstream properly.