Deliverables and timeline
We are bringing the existing BlockFinaX platform to Stellar. The build covers the protection contracts, our own wallet layer, partner API and SDK, FX oracle and institutional treasury workflows.
Stellar development began on 14 October 2026, and the protection lifecycle has run on Stellar testnet since 17 October 2026. The dates below are targets for the remaining work, with mainnet on 26 February 2027.
What we will ship
Our first release will keep the BlockFinaX interface and the existing hedger, LP and underwriter model. We will focus on one embedded account model, the full FX rate catalogue currently carried by BlockFinaX and one anchor adapter. The wallet plan, migration plan and API guide explain how these components fit together.
Other Stellar projects will also be able to consume the full BlockFinaX emerging-market FX catalogue through a Soroban interface and API. We will provide a consumer-contract example so developers can test rate precision, freshness and unavailable-data handling before using a feed.
Implementation team
We plan to hire two developers: a Rust/Soroban developer for contracts, account authorization and deployment, and a full-stack developer for the wallet, UI, API, SDK and partner integrations. A part-time derivatives specialist will review payoff calculations, collateral accounting, FX observations and settlement test cases.
Timeline
| Milestone | Build window | Proposed completion | Result |
|---|---|---|---|
| 1 · Working MVP | Weeks 1 to 7 | 27 November 2026 | Core testnet hedge lifecycle in the existing UI |
| 2 · Institutional testnet | Weeks 8 to 14 | 15 January 2027 | Embedded wallet, oracle, SDK, treasury and partner sandbox |
| 3 · Mainnet release | Weeks 15 to 20 | 26 February 2027 | Verified deployment, production tools and operational handover |
Tranche 1 · Working Stellar MVP
Target: 27 November 2026
An underwriter will create an event, an LP fund it, and a hedger buy protection and claim a qualifying payout through the BlockFinaX UI. This milestone uses an existing Stellar wallet connection and a labelled settlement fixture; embedded accounts and oracle-driven settlement follow in tranche 2.
1. Protection contracts
Implement Soroban event creation, collateral deposits, hedge purchases, settlement and claims. Preserve the initial-rate, strike, limit, direction, expiry, premium and notional semantics. Track committed collateral, maximum liabilities, LP balances and underwriter fees using the configured asset through the Stellar Asset Contract interface.
Evidence: Open-source code, testnet addresses and executed parity tests. Cover payout boundaries, rounding, insufficient collateral, unauthorized operations and repeated claims.
2. Wallet connection
Add account ownership verification, balances, network selection, simulation, unsigned XDR preparation, signature requests and receipts to the wallet screens.
Evidence: A tester links an account, receives a test asset, sends a payment and approves a Soroban purchase from the UI.
3. Platform and initial API
Connect event discovery, details, deposits, purchases and claims. Add /v1/stellar reads, transaction builders, receipts and ledger-event ingestion.
Evidence: A reproducible MVP walkthrough with ledger transactions and matching API responses.
4. Financial validation
Create shared test cases for appreciation, depreciation, strike crossings, payout limits, expiry and collateral accounting.
Evidence: Versioned test vectors with consistent contract, API and interface results.
Tranche 2 · Institutional testnet and partner sandbox
Target: 15 January 2027
Partners will be able to test the account-to-payout workflow, integrate the SDK and reconcile protection and payments against their treasury records.
1. Embedded wallet and recovery
Implement one passkey-based Soroban smart-account model using established libraries. Connect application sign-in to verified ownership. Add credential registration, rotation, revocation, recovery and relaying with bounded fee sponsorship. Keep customer signing, recovery and service administration permissions separate.
Evidence: Account creation or linking, test funding, payment, hedge purchase and settled claim through the UI. Also test refused signatures, expired requests, duplicate submissions, revocation and device loss.
2. FX oracle and reusable feed interface
Port the full existing BlockFinaX FX catalogue to the Stellar oracle, rather than limiting the feed to two pilot pairs. Reuse our current ingestion services and pair registry, and implement the Soroban publication and consumer layer. Validate source mapping and publication behaviour for every registered pair. Define quote conventions, precision, timestamps, freshness and aggregation, and retain settlement observations. Keep premium recommendations separate from settlement rates.
Expose validated observations through a documented Soroban interface and API for other Stellar projects. Include pair, rate, precision, timestamp and source reference. Publish access terms and a consumer example that handles stale or unavailable observations.
Evidence: A catalogue-parity report covering every existing FX pair, traceable observations, settlement failure tests and a reference Soroban consumer contract. Every pair has a queryable status; missing or stale observations are reported explicitly rather than replaced with invented rates.
3. Partner API and TypeScript SDK
Implement accounts, event discovery, payments, purchases, deposits, claims and receipt tracking. Add scoped credentials, tenant isolation, idempotency and signed webhooks.
Evidence: Tagged SDK, OpenAPI specification and a reference application that runs from a clean checkout. Test tenant isolation and request/webhook retries.
4. Treasury controls and anchor adapter
Add signer roles, maker/checker approvals, limits and reconciliation exports. Separate spendable balances from collateral, reserved liabilities, unpaid claims, premiums and transfers in progress. Implement one anchor adapter for the selected test corridor, including applicable authentication, customer information, quotes, funding, payouts, rejections and refunds.
Evidence: An institutional approval, collateral deposit and reconciled payment. Demonstrate the adapter in a provider sandbox or identified reference environment and label simulated bank operations.
5. Threat model, monitoring plan and audit readiness
Complete the data-flow diagram and STRIDE model across contracts, wallet, recovery, oracle, API, indexer and relayer. Map threats to monitoring triggers, baselines, owners and responses. Cover collateral, claims, asset movements, privileged changes, oracle freshness, settlement failures, relayer spend and TTL. Prepare stable testnet code, executed tests and security-tool results for independent review.
Evidence: Completed security documents supplied privately to reviewers, a public non-sensitive summary and demonstrated alert exercises. Each threat has a monitor or a documented offchain control.
Tranche 3 · Verified mainnet release
Target: 26 February 2027
We will resolve security findings, deploy the services and verify that the contracts, UI and financial records agree through a complete lifecycle.
1. Hardening and remediation
Complete integration, property and financial tests, resolve independent-review findings, and verify upgrades, emergency controls, restoration, TTL and settlement recovery.
Evidence: Tagged release, test results and remediation records. Unresolved critical or high findings block activation; other findings have documented treatment.
2. Production wallet services
Deploy accounts, wallet adapter and relayer. Configure credentials, permissions, fee budgets, backups and recovery. Verify account policies against deployed contracts.
Evidence: Mainnet account access, an approved payment, a protocol transaction and signing/recovery procedures.
3. Platform, API and SDK release
Complete role interfaces, positions, claims, errors and institutional reports. Release versioned API/SDK, tenant controls, webhooks and reconciliation.
Evidence: A reproducible partner workflow and consistent UI, API and treasury records.
4. First funding and migration route
Implement one verified route into Stellar USDC, using CCTP where supported by the selected source network. Validate destinations and track transfers. Existing EVM positions remain on their original contracts while customers fund new Stellar events.
Evidence: Completed transfer, reconciled destination balance and continued access to original-chain positions.
5. Monitoring and operating procedures
Deploy monitors against production contracts and services. Exercise stale-data, privileged-change, failed-settlement, relayer and credential incidents. Document response, recovery and address-inventory updates.
Evidence: Alert tests, incident exercises and operating runbooks.
6. Financial acceptance and public documentation
Demonstrate event creation, collateral deposit, purchase, oracle settlement and claim on mainnet, plus a payment. Reconcile the resulting records. Publish contract IDs/hashes, manifests, API/SDK examples and production oracle consumer documentation.
Track active accounts, funded events, protection notional, collateral and claims, distinguishing controlled verification from external customer use.
Evidence: Transaction links, walkthrough, financial reconciliation and a deliverable-by-deliverable release report. Other Stellar developers can follow the oracle example to consume an enabled feed.
Release dependencies
The mainnet date depends on the independent security review finishing in time. Unresolved critical or high findings move the launch date; they are not waived to keep it. Independent security review, provider access and the permitted production scope must be resolved before launch. Bank and anchor routes will only go live once their access and operating terms are confirmed.
The wallet already has a Stellar testnet prototype. The work here extends that foundation with recovery, institutional controls and the protection lifecycle. Existing work will be recorded separately from the remaining implementation.
References: SCF deliverable guidance, monitoring template, and Audit Bank rules.