What is BlockFinaX?

BlockFinaX lets businesses exposed to cross-border transactions hedge against currency volatility.

Businesses in emerging markets face real, recurring losses because their local currency can swing in double-digit percentages over weeks or months. Importers and exporters in volatile FX corridors live with this daily — and the existing hedging products were built for someone else.

The problem with traditional FX hedging

If you're an SME in Lagos, Accra, Nairobi, or Cairo and you want to lock in a USD rate:

• Banks and brokers typically require you to post 30–50% of the notional amount as collateral to buy protection or lock in a rate.
• Minimum contract sizes start at $100,000+ notional.
• That's cash flow most SMEs simply don't have to lock up — so they go unhedged, absorb the losses, and pass them onto end customers as higher prices. The losses compound across the corridor.

What BlockFinaX does

BlockFinaX is insurance for currency fluctuation:

• Pay a small upfront premium (typically 0.5–3% of notional, no collateral lockup).
• If the rate moves against you into your pre-defined zone, the smart contract pays out automatically at expiry — no claim form, no broker, no human-judgment underwriter.
• If it doesn't, the premium stays with the liquidity providers who underwrote your protection.

A multi-oracle consensus reads the FX rate at expiry; the on-chain payoff is mechanical. It's a parametric option that lives on a Diamond proxy contract instead of an ISDA agreement.

For integrators

Wiring BlockFinaX into your product gives you a new revenue model:

• Sell protection to your users. Create a liquidity pool, become the counterparty, set your own price (or use our pricing engine as a reference). You earn the premium flow.
• Buy protection on behalf of your users. Pass a hedged FX rate through to end customers and capture the spread.
• Both at once. Front-end the hedge for the user, back-end the pool with your own capital, keep the bid-offer.

Whether you're a remittance app, a B2B payments provider, a payroll service, or an exchange — if your users are exposed to a volatile FX corridor, you can turn that exposure into a product line.

In one diagram

Who is this for?

BlockFinaX has three audiences, and most integrators only care about one of them:

Role	Who	What they do	What they earn / save
Hedger	SMEs and businesses with cross-border exposure: importers, exporters, treasury teams, payroll providers, remittance corridors	Pays a small premium up-front to protect against a specific FX move. No collateral lockup.	Bounded loss on FX exposure. The payoff is determined purely by the on-chain settlement price.
Liquidity Provider	Yield-seeking capital, on-chain funds, individual depositors	Deposits USDC into the pool that backs an event. Premiums are distributed pro-rata.	The premium flow of every hedger in that event. Bounded downside (capital is at risk only if the event triggers).
Underwriter (Creator)	Investment banks, FX desks, NDF traders, anyone with an option-pricing background	Creates events: defines the strike, payout cap, expiry, premium rate, allowed payment token, and seeds the pool with initial liquidity.	Creator loyalty fee + the premiums from their own seeded LP share. Recurring yield if the pool earns a reputation.

If you're integrating BlockFinaX into your product, you're probably wiring one specific role. Skip to:

• For Hedgers → — most common integration. Wire "buy protection" into a payment / treasury / remittance app.
• For LPs → — earn yield by depositing into a pool you already trust.
• For Underwriters → — create + price events.

Use cases

The protocol is intentionally generic — it's parametric on any FX rate that the oracle network can read — but the obvious markets are:

• African / frontier-EM corridors (USD/GHS, USD/NGN, USD/KES, USD/UGX, USD/ZAR …). These are the markets traditional FX hedging products price out of, because they're too small, too volatile, or too unstable.
• Stablecoin off-ramp risk. A remittance app paying out in local currency hedges the time between receiving USDC and paying out cash.
• Cross-border salary / payroll. A payroll provider locks in the rate they promised the employee a month ago.
• Importer / exporter cost protection. The shop that imports inventory in USD but sells in local currency can cap the worst-case FX hit.
• Algorithmic hedging vaults. Strategies that systematically buy protection on negative-skew corridors and pay the premium out of the spread.

Why on-chain?

Three properties traditional FX hedging products struggle with at the same time:

1. Settlement is mechanical. Once the oracle's median lands at expiry, the contract knows the payout amount. No counter-party disputing whether the "fixing rate" was the right one. No 7-day wait for a claim review.
2. Capital is permissionless. Anyone can be an LP. Anyone can underwrite events. The book is on-chain; integrators can read it; capacity is visible.
3. It composes. Any other on-chain system — payments, lending, vaults — can read positions, listen to settlements, and trigger downstream logic from them.

How to integrate

There's one public API: the Integrator API. It speaks REST. Every state-changing smart-contract function has a corresponding endpoint that returns ready-to-sign calldata; you sign with your wallet of choice (Privy, MetaMask, Rift, a raw key) and broadcast through your own RPC — or through POST /v1/tx/broadcast if you'd rather not run one.

The server never holds private keys and never signs anything. That keeps the trust model clean: BlockFinaX gives you a typed calldata builder; your infrastructure controls custody and broadcast.

Continue to Concepts → Parametric options to understand how an event is priced, settled, and paid out. Or jump straight to the API overview.