Tx build
Each builder returns an unsigned, simulated Stellar transaction. The proposed route families keep familiar product actions while replacing EVM calldata with XDR. None of these paths is currently live.
Planned path below /v1/stellar/tx | Proposed Soroban action |
|---|---|
POST /hedge/create-event | create_event with creator seed and fee transfers |
POST /hedge/deposit | deposit into the selected event |
POST /hedge/buy-protection | buy_protection with notional max cost and deadline |
POST /hedge/claim-payout | claim_payout for the authorized beneficiary |
POST /hedge/claim-premiums | claim_premiums for an LP deposit |
POST /hedge/withdraw-capital | withdraw_capital after eligibility checks |
POST /hedge/withdraw-creator-earnings | withdraw_creator_earnings for the creator |
POST /oracle/submit-rate | Authorized observation submission under a policy |
Create event body
The proposed request carries network, creator account, pair, initial rate, strike, payout limit, rate scale, direction, expiry, premium rate and its scale, allowed asset, seed amount, LP policy, fee version, and oracle policy ID. Signature context is included only if the creator selects supported engine attestation. All integers are decimal strings; payoutCap retains its existing meaning as a price level.
Authorization and asset transfers
Contract methods require the actual user, creator, LP, oracle, or governance authority. The builder cannot make a transaction valid for an unauthorized caller. Stellar USDC flows through the configured SAC; an ERC20 approve endpoint is not used. The simulation and wallet preview disclose creation fees, seed capital, premiums, and recipients separately.
Release compatibility
The final ABI and OpenAPI schema are generated from the implemented release and checked against the manifest. Rust method names and parameter order must be verified before examples are advertised as runnable. The economic invariant suite checks funded maximum payouts, separate fee accrual, and no duplicate claims.