Skip to main content
Build the latency-sensitive trading loop on an Ephemeral Rollup (ER), then commit the state or settle funds on Solana when the result must become durable. This guide maps each protocol requirement to the MagicBlock feature that solves it.
The linked examples demonstrate integration patterns, not a production risk engine. A leveraged protocol still needs audited pricing, liquidity, solvency, liquidation, pause, and recovery rules.

​
Choose the components

​
Reference architecture

1

Initialize durable market state

Create market configuration, authorities, collateral mint, and base-layer custody accounts. Keep administrative controls and durable settlement records on Solana.
2

Delegate the latency-sensitive state

Delegate position, order, or bet accounts to the ER. Use a PER when the contents or allowed participants must be restricted inside a TEE-backed validator.
3

Authorize repeated user actions

Scope a session key to the protocol instructions, duration, and limits the user needs. Do not grant the session unrestricted control of the user’s assets. SPL Token does not understand session tokens, so token movement may also require a one-time approval to a constrained program authority, as shown in the binary prediction example.
4

Fund custody and execute

Deposit collateral into the Global Vault and use program-controlled eATAs when funds must move at ER speed. Read the configured oracle account inside each price-sensitive instruction.
5

Automate time-sensitive checks

Schedule cranks for expiry, liquidation, or periodic settlement logic. Make every scheduled instruction safe to retry and validate the current market state before changing it.
6

Commit and settle

Commit final state while remaining delegated for continued trading, or commit and undelegate when the market closes. Use a Magic Action when the commit must trigger a base-layer payout or another Solana instruction.

​
Choose a custody model

The Smart Contract Integration guide implements both patterns and links the binary-prediction reference.

​
Prepare for production

Before moving from a reference example to a production protocol, define:
  • oracle freshness, confidence, and failure behavior;
  • collateral, exposure, and liquidation rules when the product requires them;
  • maximum position, market exposure, and utilization limits;
  • liquidity and payout reserves under worst-case moves;
  • fees, rounding, and integer overflow boundaries;
  • crank failure, retry, and manual recovery paths;
  • commit frequency and the authoritative state during settlement;
  • emergency pause, close-only, and controlled unwind behavior.
Use PER only when restricted visibility is a protocol requirement. Privacy does not replace solvency, oracle validation, or authorization checks.

​
Start with working examples

Binary Prediction

Session-authorized bets, real-time prices, eATA pool custody, and expiry-based settlement.

Oracle-Priced Purchase

A smaller example focused on freshness checks, feed validation, and slippage protection.

Sealed-Bid Auction

Hidden bids on a Private Ephemeral Rollup with two-layer SPL escrow and on-chain winner selection.
Build the binary prediction example first. Add crank-driven settlement next, then choose ER custody or a post-commit base-layer payout based on where your protocol needs funds to remain authoritative.