Stellar Testnet only. No real money moves. What this means

Trust

Security

Stellar Split is a Testnet prototype. This page describes what is built today, including the gaps. It makes no claim of an audit or certification, because none exists.

Non-custodial by design

The app never holds your funds or your keys. Your key stays in Freighter. Every payment is signed there and goes straight from the person who owes to the person who is owed.

What each part can and cannot do

PartCanCannot
App (browser)Ask Freighter to sign a payment you reviewHold keys or sign for you
APIRefuse service, or record wrong data in the off-chain ledgerMove funds. It records a settlement only after Horizon shows a matching USDC payment with the reserved intent's memo
Database (Supabase)Store the off-chain ledgerBe read from the browser. The service role key is held only by the API, and the browser gets no database credential
Recorder keyRecord an x402 settlement on the contractMove tokens
AgentsRead balances and propose payments. Paying on their own, inside your limits, is the next stepHold a Stellar key in their runtime. They run in containers without one, and each agent's key stays on the host outside the container
x402 facilitator (when used)Censor a paymentSteal. It can only submit authorizations the payer signed

Stellar Assist: limits and approval

You set spend limits for an agent. Below a limit it can pay. Above it, it asks you first. The rule lives in the API, not in the agent, because we assume an agent can be manipulated by text it reads. Keys never enter the model's context. Today this is a design preview in the app, the Telegram checks are simulated, and agent payments are a stretch goal for the hackathon.

Supply chain checks

The repository includes automated checks in .github/workflows and /supply-chain: CodeQL, dependency review, OSV scanner, a check that GitHub Actions are pinned to a commit, a version guard against unapproved dependency versions, and Dependabot. They run on the project's code, which is open for you to read.

Known limits today

The full list is in the threat model and SECURITY.md.

Report a vulnerability

Report privately through GitHub: open a private security advisory. Please do not open a public issue. Include what you found, how to reproduce it, and the impact you expect. Our machine-readable policy is at /.well-known/security.txt.

In scope

Out of scope

Response targets

Safe harbor

If you act in good faith, stay in scope, avoid harming other people's data and give us reasonable time to fix the issue before you disclose it, we will not take legal action against you. We cannot speak for third parties such as Vercel, Supabase or Stellar, so follow their rules too.

No bounty

This is a hackathon project with no budget. We cannot pay rewards. We will credit you in the fix if you want.