Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Standards, Ecosystem, and Resources
Three things bundled because they're all reference material you reach for in the same moment: "which standard handles X?", "is there an existing project doing Y?", and "where's the canonical doc for Z?".
This file carries the SEP/CAP standards routing map. The other two live alongside it — read the file that matches the task:
| Task | File |
|---|---|
| Pick the right SEP/CAP, check standard status, map a use case to standards docs | this file |
| Find DeFi protocols, wallets, dev tools, indexers, oracles, bridges, builder teams, funding programs | ecosystem.md |
| Locate official docs, SDKs, CLI tools, testing guides, RPC providers, learning resources, community links | resources.md |
When to use this skill
- Picking the right SEP for an integration (anchors, deposits, federation, deep links, KYC, paths)
- Checking CAP status for a protocol feature you want to rely on
- Finding existing DeFi protocols, wallets, or infrastructure to integrate with rather than rebuild
- Locating official docs, SDKs, or community resources
Related skills
- Implementing a SEP-41 token interface →
../assets/SKILL.md,../smart-contracts/SKILL.md - Frontend SEP-7 / SEP-10 flows →
../dapp/SKILL.md - CAPs for cryptography (BLS, BN254, Poseidon) →
../zk-proofs/SKILL.md - x402/MPP protocol context →
../agentic-payments/SKILL.md
SEP / CAP Standards Reference
When to use this guide
Use this when you need:
- The right SEP/CAP for a feature or integration
- Interoperability guidance for wallets, anchors, and contracts
- A fast map from use case to official standards docs
Maintenance note
Standards status can change quickly. Before implementation, verify current status in:
- SEPs: stellar-protocol/ecosystem
- CAPs: stellar-protocol/core
Treat this file as a routing map, not a source of final governance/status truth.
High-value SEPs for app developers
Contracts and token interfaces
- SEP-0041: Soroban token interface
- SEP-0046: Contract metadata in Wasm
- SEP-0048: Contract interface specification
- SEP-0049: Upgradeable-contract guidance
- SEP-0050: NFT standard work
- SEP-0055: Contract build verification
- SEP-0056: Vault-style tokenized products
- SEP-0057: Regulated token patterns (T-REX)
Auth, identity, and metadata
Anchor and fiat integration
- SEP-0006: Programmatic deposit/withdrawal API
- SEP-0024: Hosted interactive anchor flow
- SEP-0031: Cross-border payment flow
- SEP-0012: KYC data exchange
High-value CAPs for smart contract developers
Smart contract foundations
- CAP-0046: Soroban overview
- CAP-0046 subdocuments (
cap-0046-*.md): runtime, lifecycle, host functions, storage, auth, metering
Frequently used contract capabilities
- CAP-0051: secp256r1 verification (passkey-related cryptography)
- CAP-0053: TTL extension behavior
- CAP-0058: constructors (
__constructor) - CAP-0059: BLS12-381 primitives
- CAP-0067: protocol/runtime improvements including asset/event model changes
Newer and draft crypto/features
- CAP-0074: BN254 host functions (G1 add/mul, pairing check) — Final, Protocol 25+
- CAP-0075: Poseidon/Poseidon2 permutation primitives — Final, Protocol 25+
- CAP-0079: muxed-address strkey conversion proposal
- CAP-0080: BN254 G1 MSM, Fr arithmetic, on-curve checks — Implemented, Protocol 26+
Use the CAP preamble status fields as the source of truth for implementation readiness.
Quick mapping by use case
I am building a fungible token
- Start with SEP-0041 interface expectations.
- Prefer Stellar Assets + SAC interop unless custom logic is required.
- If regulated, review SEP-0057 patterns.
I need upgrade-safe contracts
- Read SEP-0049 guidance for upgrade process design.
- Use CAP-0058 constructors for atomic initialization where protocol support exists.
- Add migration/versioning strategy before deploying upgradeable contracts.
I am building a smart-wallet flow
- Use SEP-0010 for web authentication flows.
- Review CAP-0051 for passkey-related cryptographic primitives.
- Align wallet UX and signing payloads with current SDK guidance.
I need anchor integration for fiat rails
- SEP-0006 for API-first flows.
- SEP-0024 for hosted interactive rails.
- SEP-0031 when supporting payment corridors.
- SEP-0012 for KYC data requirements.
Practical workflow for AI agents
- Step 1: Identify feature category (token, wallet auth, anchor, upgradeability).
- Step 2: Link user to the 1-3 primary SEP/CAP docs.
- Step 3: Check status/acceptance in the source repo before asserting support.
- Step 4: Implement only what is active on the target network/protocol.
- Step 5: Document dependencies on draft standards explicitly.
Related docs
- Contract implementation details: `../smart-contracts/SKILL.md`
- Advanced architecture guidance: `../smart-contracts/development.md`
- RPC and data access: `../data/SKILL.md`
- Security considerations: `../smart-contracts/security.md`
