Reading paths
Pick the route that matches what you need to decide.
Stellar reviewers
You have ten minutes and you want to know whether the Stellar work is real.
Ten-minute reviewSix things to read in order, two commands to run, the three files worth opening, and the whole list of what is deliberately not built.
The short version: MEMO_HASH is exactly 32 bytes and anchors settle on Stellar itself, and those two facts shape the entire design. The hub is enforced in the planner, the ledger keeps Stellar’s 7 decimal places, and reconciliation is a join on a watched account’s own payment stream rather than an index.
Investors
You want to know whether the market is real, whether the business earns, and whether the team can build it.
The problem
Why corridors cost so much: trapped capital, slow rails and manual reconciliation.
The market
The global opportunity: $31.6T of cross-border B2B payments, under 1% on stablecoins; then First market: Africa, where it starts.
The business
Business model: a ledger subscription from the first pilot, a take on routed volume, and revenue scenarios. Every figure there is a labelled assumption.
The proof
Evidence: what has run on Stellar testnet, and the prototype’s live mainnet payout, labelled as the prototype’s.
What's next
Roadmap: a signed anchor, the corridors in order, and what production hardening means.
Engineering leads
You want to know whether the system is correct under failure, and how hard it would be to run.
System overview
Architecture overview and the core model.
Money correctness
Ledger: double-entry, append-only, exactly-once external references, no-overdraft invariants, 7 decimal places.
Failure handling
Completeness
Reconciliation: one matcher, a vault check against the chain, and fees booked from the transaction that paid them.
Why it is built this way
The architecture decision records, twelve of them.
Anchors
You run a Stellar anchor and want to know what it takes to become a spoke.
The network
Hub and spoke: why one integration reaches every region.
The SEPs Corridor speaks
SEP anchor interface: SEP-1, 10, 12, 38 and 31, what Corridor checks, and what it needs from your stellar.toml.
What Corridor sends you
Partner interface: the normalised order lifecycle every provider is mapped to.
A full payout
Payout EUR → KES, end to end.
Off-Stellar partners
You run a payout rail that settles somewhere other than Stellar, in a currency no anchor serves yet.
The interface
Partner interface: six methods and a signed webhook.
Where you sit
Cross-chain inflows: how value reaches a spoke chain, and why the naira corridor is the one that needs it.
A reference implementation
Paj: offramp, onramp and webhooks, carried over from the prototype for the naira corridor.