Definition: Stellar Ecosystem Proposals (SEPs) are open-source specifications that describe how products and services in the Stellar ecosystem can interoperate. They provide shared integration patterns for applications, wallets, asset issuers, anchors, exchanges, and other service providers.
| Protocol documentation | SEP documentation |
|---|---|
| Directories | Stellar Ecosystem Directory |
SEPs and core protocol changes
SEPs define ecosystem-level standards and supporting interfaces. They are distinct from Core Advancement Proposals (CAPs), which propose changes to Stellar’s core protocol. A SEP does not itself change consensus or automatically force every Stellar application to implement it.
Examples
SEP-1 specifies the Stellar Info File, often published as `stellar.toml`. SEP-6 and SEP-24 define programmatic and hosted deposit and withdrawal flows. SEP-31 describes a cross-border payments API. SEP-9 and SEP-12 cover KYC fields and a KYC API; SEP-10 covers web authentication. These examples illustrate the range of coordination needed for services to work together.
How to use them
An implementation should check the current SEP text, status, version, and the support declared by the counterparties it will connect to. SEPs are community-authored and may be discussed or revised over time; naming a SEP in a product description does not by itself prove that a service is compliant or available.
Why they matter
Without shared formats and interaction rules, each wallet or provider could require a separate custom integration. SEPs give builders a common blueprint for recurring tasks while leaving service providers responsible for their own endpoints, policies, and user experience.
Related Terms
See Also
- How Do Crypto Bridges Work — And Why Are They Such a Hack Target?
- Why DAO Governance Votes Often Fall Short — and Why Protocols Still Use Them
- Elon Musk Helped Shape the Law That Would Govern His Own Stablecoin
- Tools – A curated list by CryptoGloss