Stellar Toml and Well-Known Endpoints

[Baskarayelu]

Description:

Support Stellar ecosystem discovery: expose stellar.toml (or link) and optional .well-known endpoints for wallet/anchor integration.

Requirements

• If RemitWise has a Stellar domain: add GET /.well-known/stellar.toml (or redirect to hosted stellar.toml) with DOCUMENTATION, SIGNING_KEY, etc. as per Stellar docs
• Optional: GET /api/.well-known/openapi (or similar) for API discovery
• Document in README how to set up stellar.toml and what to put in it
• Low priority if no custom domain yet; create issue and document intended content

Acceptance Criteria

• stellar.toml or well-known documented/served
• README updated
• Optional OpenAPI discovery

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Austinaminu2]

@Austinaminu2 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi maintainer, I’d like to work on this issue.

I have experience working within the Stellar ecosystem and understand the importance of ecosystem discovery via stellar.toml and well-known endpoints for wallet and anchor integrations.

✅ Proposed Approach

• Add support for /.well-known/stellar.toml
  Serve static file or redirect to hosted stellar.toml
• Include required fields (DOCUMENTATION, SIGNING_KEY, etc.) following Stellar standards
  -Implement optional API discovery endpoint (/api/.well-known/openapi)
• Ensure compatibility with Stellar wallets and anchor discovery
  -Update README with:

1. Setup instructions
2. Example stellar.toml
3. Required configuration fields
4. Keep implementation flexible for projects without a custom domain yet

✅ Deliverables

• stellar.toml served or documented
• Optional OpenAPI discovery endpoint
• Updated documentation
• Clean, maintainable implementation

I’ll follow the repository’s contribution guidelines and submit a well-tested PR.
Thanks, looking forward to contributing 🚀

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Austinaminu2 to this issue.

[drips-wave]

Congratulations, @Austinaminu2! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @Austinaminu2: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are issued when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊