standards
Stellar standards, ecosystem, and reference. Covers SEPs (Stellar Ecosystem Proposals), CAPs (Core Advancement Proposals), and a quick map for picking the right standard for wallets, anchors, payments, deposits/withdrawals, federation, deep links, and KYC. Also bundles ecosystem references (DeFi protocols, dev tools, wallets, infra, community projects) and curated documentation links. Use when you need to know which SEP applies, or want a starting point for ecosystem integrations and official docs.
What this skill does
# 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?". ## 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`, `../soroban/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` --- # Part 1: 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](https://github.com/stellar/stellar-protocol/tree/master/ecosystem) - CAPs: [stellar-protocol/core](https://github.com/stellar/stellar-protocol/tree/master/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](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md): Soroban token interface - [SEP-0046](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0046.md): Contract metadata in Wasm - [SEP-0048](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0048.md): Contract interface specification - [SEP-0049](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0049.md): Upgradeable-contract guidance - [SEP-0050](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0050.md): NFT standard work - [SEP-0055](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0055.md): Contract build verification - [SEP-0056](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0056.md): Vault-style tokenized products - [SEP-0057](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0057.md): Regulated token patterns (T-REX) ### Auth, identity, and metadata - [SEP-0010](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md): Web authentication - [SEP-0023](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0023.md): StrKey encoding - [SEP-0001](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md): `stellar.toml` ### Anchor and fiat integration - [SEP-0006](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md): Programmatic deposit/withdrawal API - [SEP-0024](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md): Hosted interactive anchor flow - [SEP-0031](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md): Cross-border payment flow - [SEP-0012](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md): KYC data exchange ## High-value CAPs for Soroban developers ### Soroban foundations - [CAP-0046](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0046.md): Soroban overview - CAP-0046 subdocuments (`cap-0046-*.md`): runtime, lifecycle, host functions, storage, auth, metering ### Frequently used contract capabilities - [CAP-0051](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0051.md): secp256r1 verification (passkey-related cryptography) - [CAP-0053](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0053.md): TTL extension behavior - [CAP-0058](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0058.md): constructors (`__constructor`) - [CAP-0059](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0059.md): BLS12-381 primitives - [CAP-0067](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md): protocol/runtime improvements including asset/event model changes ### Newer and draft crypto/features - [CAP-0074](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0074.md): BN254 host functions proposal - [CAP-0075](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0075.md): Poseidon/Poseidon2 proposal - [CAP-0079](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0079.md): muxed-address strkey conversion proposal 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 1. Start with SEP-0041 interface expectations. 2. Prefer Stellar Assets + SAC interop unless custom logic is required. 3. If regulated, review SEP-0057 patterns. ### I need upgrade-safe contracts 1. Read SEP-0049 guidance for upgrade process design. 2. Use CAP-0058 constructors for atomic initialization where protocol support exists. 3. Add migration/versioning strategy before deploying upgradeable contracts. ### I am building a smart-wallet flow 1. Use SEP-0010 for web authentication flows. 2. Review CAP-0051 for passkey-related cryptographic primitives. 3. Align wallet UX and signing payloads with current SDK guidance. ### I need anchor integration for fiat rails 1. SEP-0006 for API-first flows. 2. SEP-0024 for hosted interactive rails. 3. SEP-0031 when supporting payment corridors. 4. 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: [`../soroban/SKILL.md`](../soroban/SKILL.md) - Advanced architecture guidance: [`../soroban/SKILL.md`](../soroban/SKILL.md) - RPC and data access: [`../data/SKILL.md`](../data/SKILL.md) - Security considerations: [`../security/SKILL.md`](../security/SKILL.md) --- # Part 2: Stellar Ecosystem This guide catalogs the major projects, protocols, and tools in the Stellar ecosystem. Use this as a reference when building on Stellar to find relevant integrations, examples, and community projects. > **Canonical directories** — For the most up-to-date project lists, check: > - [Stellar Ecosystem](https://stellar.org/ecosystem) — Official directory (searchable by country, asset, category) > - [SCF Projects](https://communityfund.stellar.org/projects) — Funded projects with status tracking > - [Stellar on DefiLlama](https://defillama.com/chain/stellar) — Live DeFi TVL data > > Treat project metrics/status as volatile. Validate latest activity and production readiness before taking dependencies. ## DeFi Protocols ### Lending & Borrowing #### Blend Protocol Universal liquidity protocol enabling permissionless lending pools. - **Use Case**: Lending, borrowing, yield generation - **GitHub**: https://github.com/blend-capital/blend-contracts - **GitHub (v2)**: https://github.com/blend-capital/blend-contracts-v2 - **Integrations**: Meru, Airtm, Lobstr, DeFindex, Beans #### Slender First non-custodial lending protocol on Soroban with flash loan support. - **Use Case**: Lending, borrowing, flash loans - **Features**: Pool-based strategy, sTokens, dTokens, utilization caps - **Oracle**: SEP-40 compatible (Reflector) ### DEXs & AMMs #### Soroswap First DEX and aggregator on Stellar/Soroban. - **Use Case**: Token swaps, liquidity provision, agg
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.