Support for 12 SEPs

Anchor integrations (deposits, withdrawals, KYC, quotes), HD wallets, web auth, federation, regulated assets, recovery and web auth for contract accounts. KMP developers get production-ready implementations instead of implementing these Stellar Ecosystem Proposals from scratch.

Maintenance of the SDK for 1 Year

1-year maintenance commitment, 2-day response SLA for issues, Stellar Discord presence (#sdk-dev channel)

Yes

$68.0K

Quantitative Outputs (12 months post-launch):

• 10+ production applications using the SDK

• 50+ GitHub stars

• Active community engagement (issues, discussions)

Qualitative Impact:

• Developer Access: Enable Kotlin developers to build cross-platform Stellar apps

• Cost Reduction: Single codebase for multiple platforms reduces development costs significantly

• SDK Completion: Bring SEPs support to KMP developers

Validation:

• Production apps deployed

• 1-year maintenance commitment fulfilled

• 2-day response SLA maintained

• SDK current with Stellar protocol

At Launch (v1.0.0 Release):

• Public announcement on Stellar Discord

• Blog post with architecture overview and demo apps

Ongoing Support:

• GitHub Issues (primary support channel)

• Stellar Discord presence (#sdk-dev channel)

• 2-day response SLA for issues

Community Building:

• Monthly release notes / updates

• Track and showcase public projects using the SDK

• Respond to community questions and feature requests

Developer Track Record (Proven Capability):

• Maintainer of 3 public good production Stellar SDKs: Flutter (79 stars), iOS/macOS (125 stars), PHP (39 stars)

• Multiple SCF Build Award wins with on-time delivery

• 8 years active in Stellar ecosystem

• SCF Pilot, Public Good Contributor, SCF Category Delegate for many quarters including Q1'25, Q2'25 and Q3'25

• GitHub: [Flutter SDK link], [iOS SDK link], [PHP SDK link]

Current KMP SDK Status (Production-Ready):

• Published: on Maven Central

• Status: Production-ready core SDK complete

• Platforms: JVM - android + server, iOS, macOS, JavaScript - Browser, JavaScript - Node.js

• Demos: 11 feature demos operational across all platforms

• Investment: self-funded development of the core SDK

Why This Grant (Growth Stage):

• SDK is production-ready but NEW (needs SEPs support for adoption)

• Current features: Core SDK (crypto, transactions, Horizon, RPC, Soroban)

• Missing: 10+ SEPs needed for real-world apps

• This grant completes the SDK to enable KMP devs to easily build cross-platform wallet applications, authenticate and interact with Stellar Anchors

Market Validation:

• Kotlin: 7M+ developers, official Android language (Google)

• KMP usage more than doubled in one year (JetBrains Developer Ecosystem Survey 2024-2025: 7% → 18%)

• Major company adoption: Shopify, Forbes, Google official support (Google I/O 2024)

• Only production-ready KMP Stellar SDK

I’ve deployed the current version of the demo web app here for interested reviewers and voters. It provides an easy way to get a first impression without having to clone the SDK from GitHub. The apps for other platforms require signed builds for deployment but can be tested locally by cloning the SDK.

Deliverable 1: SEP-01 Support

• Brief description: SEP-1 (Stellar Info File) implementation is fundamental to the Stellar KMP SDK as it enables discovery and verification of Stellar network participants through the stellar.toml file standard. This implementation allows applications to automatically retrieve and validate essential information about organizations, their assets, validators, and compliance endpoints, forming the foundation for trust and interoperability within the Stellar ecosystem. The stellar.toml parser serves as a critical entry point for establishing secure connections with anchors, exchanges, and other Stellar services.

• How to measure completion: SEP-1 implementation completion requires robust TOML parsing with full support for all stellar.toml sections (DOCUMENTATION, PRINCIPALS, CURRENCIES, VALIDATORS) and all service endpoint fields defined in the specification. Success is measured by passing unit tests with 90%+ coverage including edge cases for malformed TOML, successful parsing of real-world stellar.toml files. The implementation must include documentation with examples demonstrating domain discovery and currency lookups.

• Estimated date of completion: Nov. 16, 2025

• Budget: $3.000

Deliverable 2: SEP-10 Support

• Brief description: SEP-10 Web Authentication provides the foundation for secure client-server authentication in the Stellar ecosystem, enabling wallets and applications to prove account ownership through cryptographic challenge-response mechanisms. This protocol is essential for accessing authenticated services like SEP-24 interactive flows, SEP-31 cross-border payments, and SEP-12 KYC operations, making it a critical security component for any Stellar-integrated application. The implementation ensures secure, standardized authentication across the Stellar network while supporting both standard and muxed accounts, as well as client domain verification for enhanced security in non-custodial wallet scenarios.

• How to measure completion: SEP-10 client implementation completion requires functional challenge request/response handling, comprehensive challenge validation (sequence number, time bounds, server signature, home domain), transaction signing, and JWT token parsing with claim extraction. Success is measured by passing unit tests with 90%+ coverage including security validation tests (sequence=0 enforcement, time bounds checking, signature verification), successful authentication against reference SEP-10 server (Stellar testnet anchor), support for both standard and muxed accounts, and optional client domain verification. The implementation must include documentation with explicit security warnings about each validation requirement, working examples demonstrating the complete authentication flow.

• Estimated date of completion: Nov. 30, 2025

• Budget: $8.000

Deliverable 3: SEP-09 Support

• Brief description: SEP-09 standardizes the exchange of KYC (Know Your Customer) and AML (Anti-Money Laundering) information across the Stellar ecosystem, enabling compliant and interoperable identity verification between anchors, wallets, and financial institutions. This implementation provides KMP developers with a structured, type-safe way to handle sensitive customer data fields required for regulatory compliance in cross-border payments and asset issuance. The standardized field definitions ensure consistent data formats across different Stellar services, reducing integration complexity and improving the reliability of KYC/AML processes.

• How to measure completion: SEP-9 implementation completion requires comprehensive data model classes for all field categories (natural person, organization, financial account, card) with proper type definitions. Success is measured by passing unit tests with 90%+ coverage including validation tests, proper handling of binary field encoding (base64 for photo IDs and documents), and correct dot notation support for organization-prefixed fields. The implementation must include documentation along with working examples demonstrating field population.

• Estimated date of completion: Dec. 4, 2025

• Budget: $1.500

Deliverable 4: SEP-12 Support

• Brief description: SEP-12 provides the standardized KYC (Know Your Customer) API that enables anchors to collect and verify customer information required for regulatory compliance in deposit, withdrawal, and cross-border payment operations. This protocol is essential for Stellar anchors to meet legal requirements while maintaining interoperability between different wallet implementations and service providers. The implementation ensures that customer data can be collected once and reused across multiple Stellar services, reducing friction in the user experience while maintaining compliance with financial regulations.

• How to measure completion: SEP-12 client implementation completion requires functional methods for all KYC endpoints (getCustomerInfo, putCustomerInfo, putCustomerCallback, postCustomerFile, getCustomerFiles) with proper SEP-9 field handling and SEP-10 authentication support. Success is measured by passing unit tests with 90%+ coverage, successful integration tests against reference KYC server (Stellar testnet anchor), proper handling of all customer status values (ACCEPTED, PROCESSING, NEEDS_INFO, REJECTED), and multipart/form-data file upload functionality. The implementation must include documentation along with working examples for customer registration and document upload workflows.

• Estimated date of completion: Dec. 16, 2025

• Budget: $6.500

Deliverable 5: SEP-38 Support

• Brief description: SEP-38 (Anchor RFQ API) enables anchors to provide real-time quotes for exchanging Stellar assets with off-chain assets, facilitating seamless cross-border payments and fiat-to-crypto conversions. This implementation is critical for financial applications requiring transparent pricing, guaranteed exchange rates, and efficient asset bridging between traditional finance and the Stellar network. The quote service provides both indicative and firm quotes with expiration times, enabling reliable financial planning and execution for anchor operations.

• How to measure completion: SEP-38 client implementation completion requires functional methods for all quote endpoints (info, prices, price, postQuote, getQuote) with proper SEP-38 Asset Identification Format support and context-aware responses for SEP-6, SEP-24, and SEP-31 integrations. Success is measured by passing unit tests with 90%+ coverage, proper handling of both indicative and firm quotes with expiration tracking, and support for all optional fields including delivery methods and country codes. The implementation must include documentation with working examples demonstrating price discovery, firm quote request with guaranteed rates.

• Estimated date of completion: Jan. 12, 2026

• Budget: $5.500

Deliverable 6: SEP-24 Support

• Brief description: The SEP-24 implementation will be a critical component of the Stellar KMP SDK as it provides the standard interface for integrating with anchor services that bridge traditional financial systems with the Stellar network. This protocol enables seamless fiat on-ramps and off-ramps through interactive deposit and withdrawal flows, allowing users to move value between Stellar assets and external payment rails like bank transfers or other cryptocurrencies. By supporting SEP-24, the SDK empowers KMP applications to offer complete end-to-end payment solutions that connect the Stellar ecosystem with the broader financial world.

• How to measure completion: SEP-24 client implementation completion requires functional methods for all anchor endpoints (info, deposit, withdraw, transaction polling, transaction history) with comprehensive request/response model support and SEP-10 authentication handling. Success is measured by passing unit tests with 90%+ coverage, successful integration tests against reference anchor implementations (Stellar testnet anchor), and the ability to complete end-to-end deposit and withdrawal flows with the Stellar testnet anchor. The implementation must include documentation with working examples demonstrating the complete interactive flow from service discovery through transaction completion.

• Estimated date of completion: Jan. 30, 2026

• Budget: $8.000

Deliverable 1: SEP-06 Support

• Brief description: SEP-6 (Deposit and Withdrawal API) is a critical protocol for enabling fiat on-ramps and off-ramps in the Stellar ecosystem, allowing users to convert between traditional currencies and Stellar assets programmatically without interactive web flows. This implementation provides anchors and wallet developers with the essential infrastructure to facilitate secure deposit and withdrawal operations, including support for cross-asset conversions via SEP-38 quotes, comprehensive transaction tracking, and integration with SEP-10 authentication and SEP-12 KYC workflows. By implementing SEP-6, the KMP SDK enables production-grade financial on/off-ramp services that are essential for real-world adoption of Stellar-based payment systems.

• How to measure completion: SEP-6 client implementation completion requires functional methods for all anchor endpoints (info, deposit, depositExchange, withdraw, withdrawExchange, fee, transaction, transactions, patch) with comprehensive request/response model support and SEP-10 authentication handling. Success is measured by passing unit tests with 90%+ coverage, successful integration tests against a reference anchor implementation (Stellar testnet anchor), and the ability to complete end-to-end deposit and withdrawal flows including cross-asset exchanges. The implementation must include documentation with working examples demonstrating the complete programmatic workflow from service discovery through transaction completion and status monitoring.

• Estimated date of completion: Feb. 20, 2026

• Budget: $10.000

Deliverable 2: SEP-05 Support

• Brief description: SEP-5 standardizes hierarchical deterministic key derivation for Stellar, enabling secure generation of multiple accounts from a single mnemonic seed phrase. This implementation is critical for wallet interoperability, allowing users to recover their accounts across different applications while maintaining the security benefits of deterministic key generation. The standard ensures consistent key derivation paths (m/44'/148'/x') across the Stellar ecosystem, making it an essential component for any production-ready Stellar SDK.

• How to measure completion: SEP-5 implementation completion requires full BIP-39 mnemonic generation and validation (12, 15, 18, 21, 24-word phrases), BIP-32 hierarchical key derivation with SLIP-0010 ed25519 support, and Stellar-specific derivation paths (m/44'/148'/x'). Success is measured by passing unit tests with 90%+ coverage including test vectors from BIP-39 and SLIP-0010 specifications, successful key derivation matching reference implementations, and proper entropy validation with secure random generation. The implementation must include documentation with security warnings about entropy handling, mnemonic storage, and passphrase protection, along with working examples for wallet key generation and account recovery.

• Estimated date of completion: Mar. 02, 2026

• Budget: $5.500

Deliverable 3: SEP-08 Support

• Brief description: SEP-8 (Regulated Assets) is a critical component for the Stellar KMP SDK that enables compliant token issuance and trading for securities, regulated financial instruments, and other assets requiring per-transaction approval. This implementation allows asset issuers to maintain regulatory compliance by reviewing and approving each transaction before execution, supporting use cases such as securities trading, KYC/AML enforcement, velocity limits, and jurisdiction-based restrictions. By implementing SEP-8, the KMP SDK provides wallet developers and exchanges with a standardized interface to interact with approval servers, making it possible to build compliant applications on the Stellar network while meeting regulatory requirements across various jurisdictions.

• How to measure completion: SEP-8 client implementation completion requires functional methods for transaction approval workflow (authorizationRequired, postTransaction, postAction) with support for all five response statuses (success, revised, pending, action_required, rejected) and proper handling of action methods (GET and POST). Success is measured by passing unit tests with 90%+ coverage, proper AUTH_REQUIRED and AUTH_REVOCABLE flag verification via Horizon, and the ability to complete transaction approval flows including user action workflows. The implementation must include documentation, working examples, and guidance on authorization flag configuration.

• Estimated date of completion: Mar. 15, 2026

• Budget: $5.000

Deliverable 4: SEP-2 Support

• Brief description: The SEP-2 Federation Protocol implementation is essential for providing user-friendly payment addressing in the Stellar network. It enables applications to resolve human-readable addresses like "alice*example.com" into Stellar account IDs and memo information, significantly improving the user experience and reducing errors in payment transactions. This implementation allows SDK users to seamlessly integrate federation services, making Stellar payments as simple as using email addresses.

• How to measure completion: SEP-2 implementation completion requires functional support for all four federation lookup types (name, account ID, transaction ID, forward) with proper memo handling including base64 encoding for hash types. Success is measured by passing unit tests with 90%+ coverage, proper handling of error responses, and integration with SEP-1 for automatic federation endpoint discovery. The implementation must include documentation with examples for each lookup type.

• Estimated date of completion: Mar. 25, 2026

• Budget: $2.000

Deliverable 1: SEP-30 Support

• Brief description: SEP-30 Account Recovery is a critical protocol that enables multi-party recovery of Stellar accounts when users lose their private keys, eliminating the catastrophic consequences of key loss. This implementation allows users to securely regain access to their accounts through alternative authentication methods such as email, phone number, or other Stellar addresses, while maintaining security through distributed trust across multiple recovery servers. The protocol also supports secure account sharing between parties and multi-device access scenarios, making it essential for enterprise wallets, custodial services, and user-friendly wallet applications that prioritize accessibility without sacrificing security.

• How to measure completion: SEP-30 client implementation completion requires functional methods for all recovery endpoints (registerAccount, updateIdentitiesForAccount, signTransaction, accountDetails, deleteAccount, accounts) with support for multiple authentication methods (stellar_address, phone_number in E.164 format, email) and proper identity role handling. Success is measured by passing unit tests with 90%+ coverage, successful integration tests against reference recovery servers (2 Stellar reference recovery serves running in docker), proper handling of multi-server workflows with signature aggregation. The implementation must include documentation along with working examples demonstrating the complete five-phase recovery workflow.

• Estimated date of completion: Apr. 12, 2026

• Budget: $5.000

Deliverable 2: SEP-45 Support

• Brief description: SEP-45 defines the authentication protocol for Soroban smart contract accounts (C... addresses), complementing SEP-10 which handles traditional Stellar accounts (G... and M... addresses). Without SEP-45 support, KMP SDK users cannot authenticate contract account holders, effectively excluding them from critical Stellar services including SEP-12 KYC, SEP-6/24 deposit/withdrawal endpoints, SEP-8 regulated assets, and SEP-31 cross-border payments. As Soroban smart contracts become central to Stellar's ecosystem with increasing adoption by institutional users and DeFi applications, the absence of SEP-45 creates a fundamental gap that limits the SDK's utility and competitive position. Implementation is essential to ensure the KMP SDK is a first-class development platform capable of serving the complete Stellar ecosystem including modern contract-based account architectures.

• How to measure completion: SEP-45 implementation completion requires four core components (challenge endpoint, token endpoint, configuration/discovery, and client-side support) with comprehensive testing including 90%+ unit test coverage, integration tests against reference implementations, and security validation to prevent attacks. Success is measured by all components being functional, tests passing, documentation with working examples, and successful authentication with at least one live Stellar service supporting SEP-45 (if available). The implementation must demonstrate JWT token generation with required claims, and clean separation from existing SEP-10 code to enable services supporting both authentication protocols.

• Estimated date of completion: May. 9, 2026

• Budget: $8.000

I have been a Stellar Developer since 2017, specialized on the implementation and maintenance of Stellar SDKs. Main developer and maintainer of the iOS, Flutter and PHP Stellar SDKs.