Repository navigation
Add XOXNO Swap Aggregator and RedStone to the ecosystem catalog - #187
mihaieremia wants to merge 2 commits into
Conversation
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
🤖 Automated message from the Stellar Triage Bot. 👀 Picked this up — a review will follow shortly. |
|
🤖 Automated message from the Stellar Triage Bot. Thanks, Mihai. Moving this here from stellar-docs#2949 was the right step. The RedStone entry also fills a real gap in the oracle section. What I checked:
I pushed 1a8a553 with two small fixes:
Your choice to leave RedStone out of "Choosing an oracle" is right. Only One step is left. You work on XOXNO, and this adds XOXNO to official skill content. A maintainer must decide that listing. @kaankacar, the technical content checks out at this head. |
Adds two entries to
skills/standards/ecosystem.md. The same entries were first proposed in stellar/stellar-docs#2949; they belong here so the skills sync carries them to the docs.Sources:
stellar-swap.xoxno.com/api/v1/config(router and venue list), the aggregator's OpenAPI spec, and the RedStone section of developers.stellar.org oracle providers (contract IDs, update rule, integrations).Left out: a RedStone row in "Choosing an oracle". The Stellar docs say RedStone checks freshness at read time, unlike the oracles in that table, and that needs confirming against RedStone's contract source first.