What is BlockFinaX?
BlockFinaX lets businesses with cross-border exposure buy bounded FX protection. Underwriters create and price events, liquidity providers fund those events, and hedgers pay a premium for the event's payout terms.
These docs describe how we plan to bring the existing BlockFinaX platform and API to Stellar. They follow the current product model and documentation structure. The Stellar contracts and endpoints are part of the proposed build and are not live yet. The current EVM documentation remains at docs.blockfinax.com.
Why BlockFinaX exists
Businesses increasingly use stablecoins to pay suppliers and move funds across borders. Many still earn in local currency while their invoices and loans are denominated in dollars. When the local currency depreciates, those obligations become more expensive to meet. A faster payment rail leaves that currency mismatch in place.
A business facing a dollar invoice needs protection between the day it agrees the purchase and the day it pays. A financial institution borrowing in foreign currency needs to manage repayments against local-currency revenue. Traditional hedging can be hard to access in the markets we serve, particularly for smaller transactions and less-liquid currencies.
BlockFinaX exists to make FX protection part of payment, lending and treasury workflows. Our platform connects hedgers with collateral providers around defined events, with an agreed premium, payout rule and settlement date. The SDK and API give financial institutions, fintechs and insurance desks a way to offer that protection inside their own products.
The Stellar build will bring this model to stablecoin payments and programmable financial services through Soroban contracts and Stellar settlement. Protection covers the event's defined exposure and payout limits; it does not guarantee every exchange-rate loss will be recovered.
Background: IFC client risk management and IMF on stablecoins and cross-border payments.
What BlockFinaX does
The underwriter defines the currency pair, initial rate, strike, payout limit, direction (a Cap or a Floor), expiry, premium rate, and settlement policy. LPs supply the collateral. A hedger buys notional exposure within the funded capacity. After oracle settlement at expiry, a qualifying position can claim its calculated payout. Premiums, remaining capital, and creator earnings follow separate accounting paths.
The Stellar build retains this event lifecycle. Its asset transfers use Stellar USDC through a Stellar Asset Contract; its event and position state runs in Rust Soroban contracts. It does not copy a Solidity Diamond address or change a customer's existing EVM position into a new contract.
Who is this for
| Role | Platform action | Integration guide |
|---|---|---|
| Hedger | Buy protection and claim a qualifying payout | Hedgers |
| LP | Supply collateral and receive a share of premiums, with capital at risk | Liquidity providers |
| Underwriter | Create and price an event and seed its liquidity | Underwriters |
| Bank or fintech | Embed these roles in payments and treasury workflows | Institutional integration |
Stellar platform and API
We currently use Rift for the wallet, but our integration does not support Stellar accounts or signing. We plan to build our own Stellar wallet infrastructure and will also evaluate a Rift extension or another provider. Read the wallet infrastructure plan for the three paths and the Blux, Privy and Dfns shortlist.
The application keeps the wallet UI and business workflow. Our Stellar adapter adds network selection, typed account addresses, SAC balances, transaction XDR, and Soroban authorization. Application login identifies a user; a separately authorized Stellar account signs transactions.
The planned API uses /v1/stellar routes alongside the existing EVM API. The server prepares an unsigned transaction; the customer signs its authorization and envelope; a relayer or wallet submits it to Stellar RPC. Read API overview, transaction builder, and SDK guide.
Existing Base and BSC events remain on their original contracts. See migration for user-authorized funding of new Stellar accounts and new events.