Add data feeds cache, proxy, and common contracts - #161
Conversation
Soroban Contract Test Coverage92.57% line coverage — 18067 / 19517 lines hit
Per-Contract Breakdown
Full file-level coverage report |
|
The five failing Go CI checks (E2E, Go Unit Tests, Integration ×2, Coverage) are pre-existing on main with byte-identical failure signatures — not introduced here: deployment/adapters references CommitteeVerifierClient.GetAllSignatureConfigs, which is absent from the bindings at current main, so every Go job fails at build. All contract-side checks (test-contracts, formatting, generated code) pass. |
fe0b147 to
76ac73e
Compare
|
Note for reviewers: |
019b250 to
14b9721
Compare
Self-contained nested cargo workspace at contracts/data-feeds: cache (rounds, permissions, per-feed freeze), proxy, and shared ownable/upgradeable/token-recovery crates. Literal BytesN types at ABI positions; Bound carries explicit discriminants.
943fa11 to
099909e
Compare
Summary
contracts/data-feeds/as a self-contained nested cargo workspace.Context
Byte-identical port of the reviewed contracts from
data-feeds-stellar-integration(its PR #1), relocating them to live with the other Stellar contracts. The nested workspace keeps their soroban-sdk 26.1 / stellar-access 0.7.2 pins isolated from the root workspace's soroban-sdk 25.1 — no contract changes, and the root workspace build/CI is untouched (verified:cargo check --workspacedoes not descend into it).Changes
contracts/data-feeds/: data-feeds-cache, data-feeds-proxy, data-feeds-common crates with their own workspaceCargo.toml,Cargo.lock, andrust-toolchain.toml.Testing
cargo test --manifest-path contracts/data-feeds/Cargo.toml --workspace— 165 passed.Notes
*/test_fixtures/are inputs for the upgrade tests.cargo test+fmt --checkundercontracts/data-feeds/).