Add Stellar DF cache write e2e scenario - #23208
Draft
Fletch153 wants to merge 28 commits into
Draft
Conversation
StellarDFCacheWrite: deploy and permission the DF cache via the generated bindings, inject a deterministic report payload into the stock stellarwrite workflow, and byte-verify the decoded round through latest_round after consensus write.
Fletch153
force-pushed
the
feature/DF-25510-stellar-df-cache-e2e
branch
from
August 4, 2026 13:39
f16aca0 to
eae5312
Compare
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
2 participants
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
StellarDFCacheWritesuite scenario: the real Data Feeds cache contract is the write receiver, and the assertion reads the decoded price back on-chain vialatest_round— Aptos-parity for Stellar.Context
The existing Stellar write test asserts only a test receiver's report count. This drives the full production write shape: DF-shaped XDR payload → consensus → forwarder → cache permission check → recorded round.
Changes
system-tests/tests/smoke/cre:executeStellarDFCacheWriteTest+ suite registration.system-tests/lib/cre/features/stellar: cache deploy/configure helpers (single funded chain handle for owner-auth), deterministic XDRVec<ReportEntry>payload builder, forwarder address accessor.deployment/cre/stellar: cache deploy/configure/read ForChain helpers mirroringreceiver.go.Testing
Test_CRE_V2_Stellar_Suite/StellarDFCacheWritepassed in 66.69s (reporttx f419…1704, decoded answer + timestamp byte-verified vialatest_round).go vetclean on all touched modules.Notes
chainlink-stellarpin must then be bumped — module resolution fails until then.HashTruncateName's hex string, matching what consensus stamps into report metadata.