Security model
Stellar Split is non-custodial. The app never holds funds or keys. Payments go from the debtor's wallet to the creditor's wallet, signed in Freighter. This page lists what each part can and cannot do today, on Stellar Testnet with no real money.
This is a hackathon project. The code has not been audited. Use Testnet accounts only.
Trust assumptions
| Component | Can | Cannot |
|---|---|---|
| Web app | Ask your wallet to sign messages and payments | Hold your key or move funds without your signature |
| API | Refuse service or record wrong data in the off-chain ledger | Move funds. It records a settlement only after Horizon shows a matching payment with the intent memo |
| Supabase service role key | Read and write the ledger | Reach the browser: only the API holds it |
| Group contract admin | Administer the Testnet contract (a single developer key) | Settle: the deployed contract is not used for settlement yet |
| Contract recorder key | Record an x402 settlement on the contract | Move tokens. Recorded hashes are not re-checked yet, so do not rely on contract records beyond Testnet |
| Agents | Act within membership and server caps | Read their key: it stays on the host, outside the agent container |
| MCP server | Use the agent token and, with a signer file, pay up to 25 per call | Pay terms that differ from the reserved intent |
Protections in the API
- SEP-53 sign-in with single-use, HMAC-signed challenges. Sessions are HMAC-signed and expire after 12 hours.
- Agent tokens are stored only as SHA-256 hashes and compared in constant time.
- Bodies containing a secret-key-shaped string are refused, before and after JSON parsing.
- Non-members get
404, so group ids cannot be probed. - Settlement intents lock the payer and creditor, so concurrent payments cannot overpay.
- Testnet only: the API refuses another network and checks the Horizon passphrase.
- Responses carry
Cache-Control: no-storeandX-Content-Type-Options: nosniff.
Your integration
- Never send, log or store a Stellar secret key. Sign in the wallet or on a host you control.
- Keep session tokens, agent tokens and
MCP_AUTH_TOKENserver side. - Verify a payment on Horizon yourself when it matters to you. See Integrations.
Report a vulnerability
Report privately through GitHub: open the Security tab of the repository and click Report a vulnerability. Do not open a public issue. Include what you found, how to reproduce it and the impact you expect.
| Step | Target |
|---|---|
| First reply | Within 3 working days |
| Triage and severity | Within 7 days |
| Fix or mitigation plan for high and critical | Within 30 days |
In scope: the Soroban contracts, the app, API and MCP server code, GitHub workflows and supply chain checks. Out of scope: bugs in Stellar, Soroban, x402 or other upstream projects, and Testnet funds. The full policy is in SECURITY.md and on the website.