Repository navigation
Persist target allocations, verify Stellar submissions, and add user API keys - #205
Merged
github-actions[bot] merged 4 commits intoOct 6, 2026
Conversation
Code Review & Auto-Merge — @dorismaduegbunam 🚀Thank you @OTD-Aregbesola for your contribution!
Verified code changes and repository requirements. Merging pull request. |
This was referenced Oct 6, 2026
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
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.
Target allocations, oracle verification, and consumer API keys previously relied on placeholder or in-memory behavior. This change makes them persistent and validates submissions against the Stellar ledger.
submit_pricetransactions against the configured network and contract, with confirmation checks and bounded retries for transient RPC failures.The Stellar payload representation follows the existing six-argument
submit_priceinterface: SHA-256 of its canonical XDR argument vector. Related contract work: TRELLIS-STELLAR/Trellis-contracts#9. Verification requires a Stellar transaction reference; legacy payload signatures alone are not ledger evidence.Validation: 56 tests passed on the rebased branch, including existing rebalancing behavior. Two additional API key strategy tests passed with the upstream quota dependency isolated using its last valid configuration. All three migrations passed PostgreSQL smoke checks in PGlite, including rollback, restart persistence, unique replay indexes, and revocation.
Existing malformed quota configuration on main blocks the full TypeScript build and the direct API key strategy test suite. That unrelated configuration is unchanged. Scoped ESLint and diff whitespace checks passed; existing formatting in shared app and rebalancing code remains outside scope.
Closes #12
Closes #11
Closes #10
Closes #9