Aevo: perpetual fees, option premium caps, portfolio margin and collateral transfers

Aevo’s architecture is deliberately hybrid: an off-chain order book matches maker and taker orders and an off-chain risk engine checks account collateral; only matched results are submitted to settlement contracts on a layer-2 system. This can offer a different execution experience from a purely on-chain automated market maker, but it also gives the matching service operational roles not held by a permissionless pool.[3]

The documented products include perpetual futures and options. They are derivative exposures, not proof that a trader owns or can withdraw the underlying BTC or ETH represented by a contract. Perpetuals add funding and liquidation risks; purchased options involve premium and expiry; written options may impose nonlinear obligations. A crypto-backed margin wallet does not turn those contracts into spot holdings.[2][4][5]

Aevo charges on contract notional, with a separate premium cap for options. Standard perpetual rates remain 0.05% maker and 0.08% taker in the retrieved official schedule; a note promising future reductions is not an effective new tariff. Funding, expiry settlement and forced-liquidation charges are separate.[2][4][8]

Funding Aevo is not a fiat purchase via a domestic bank. A participant interacts with wallets and supported smart-contract deposit arrangements; fees may include source-chain gas, bridging, collateral conversion and eventual destination settlement. The matching price and P&L account use derivatives mechanics after collateral arrives. This means a trader may have a token balance on one chain but not free margin in the venue until deposits are credited.[3][2]

Withdrawal availability is affected not just by network finality but by the account’s free collateral after open positions, margin requirements and funding. The documentation does not establish a universal cash-withdrawal rail or an unconditional immediate return time in an outage. Model withdrawal as an account-risk action with blockchain and contract identifiers retained.[5][3]

The off-chain matching engine and settlement smart contracts divide functions. Users may keep control of the source wallet while making margin deposits, but collateral in a venue contract is exposed to smart-contract, upgrade, oracle, sequencer and insolvency/operational risks. Describing an order book as on-chain because settlement follows matching would obscure this architecture.[3]

Aevo’s portfolio-margin explanation describes scenario and floor components, with multiple hypothetical price/volatility shocks. This can recognise hedged risk but does not cap losses or remove liquidation and auto-deleveraging. A balanced portfolio today may become unbalanced after volatility or option decay. Stop orders, notifications and dashboards depend on system availability; always consider tail-event gaps.[5]

A wallet may be technically able to load a trading page without the person being eligible to trade a derivative under their home-country law or the platform’s terms. The source review did not establish a complete date-stamped country matrix or the currently designated legal counterparty for each client type. Those are meaningful documentation gaps rather than reasons to declare worldwide availability.[6][1]

An institution considering Aevo also needs operational controls for wallet signers, collateral allocation, liquidation alerts and reconciliation of off-chain fills to on-chain events. A retail app’s user interface is not evidence that an institution gets segregated custody, audited execution standards or a dedicated derivatives-law permission.[3][5]

A customer needs two audit trails: the off-chain order/fill record and the on-chain transaction or contract event. During an exchange outage or an L2 delay, a failure to see an expected fill is not necessarily proof that a signed order never reached the matching engine. Conversely a wallet transaction alone may only show collateral movement, not the derivatives execution and final account P&L.[3]

The official documentation offers help navigation and technical descriptions, but the inspected material did not verify a compensatory outage policy, full order-cancellation guarantee or fixed tax-export format. A user should retain contract addresses, network hashes, execution timestamps, liquidation notices, margin snapshots and support-ticket IDs before attempting a dispute.[2][6]

No completed financial-services licence or permission number was verified for a legally identified Aevo interface operator. It is therefore inappropriate to describe “the DAO” as an authorised corporate counterparty or to present decentralised settlement as the equivalent of an exchange-trading licence. The structured entity and permissions arrays remain empty where an enforceable company scope cannot be verified.[6][3]

A jurisdiction’s derivatives restrictions can apply to its residents even when the execution uses smart contracts or a browser wallet rather than a domestic intermediary. Regulatory analysis for an eligible institution should be conducted against the actual product, operator, user location and applicable derivatives law.[2][6]

Aevo publishes an exchange architecture and a family of developer documents rather than the kind of company-registry and licensed-entity tariff found for a local exchange. The review distinguishes software protocol, trading interface, off-chain operator and collateral-holding contracts. The fact that they share a brand does not demonstrate that one jurisdictional company is responsible for every component.[3][6]

A venue’s self-described volume, if later supplied by a dashboard, would need corroboration and a clear metric: contracts traded, open interest, collateral deposits and unique wallets are different quantities. We did not adopt a token-market-cap statistic as a count of exchange customers.[1]

Operator

Aevo decentralised derivatives protocol; specific client-interface operator not independently verified

Exchange model

Hybrid

Service scope

Derivatives venue using off-chain matching/risk and on-chain settlement on an L2; documented perpetual futures and options, not ordinary fiat spot banking.

Client types

Retail clients; Professional clients

Pricing publication

Public pricing

Other names

Ribbon Finance related heritage

Pricing scope

Standard perpetuals 0.05% maker/0.08% taker; options 0.03%/0.05% notional capped at 12.5% of premium. Liquidation and network-specific collateral transfer charges are separate.

Funding scope

Crypto collateral through supported Ethereum, Arbitrum and Optimism routes. Published deposit/withdrawal fees differ by asset and network; canonical rollup withdrawals have a documented 2–3-hour architecture estimate.

Custody and asset handling

Collateral committed to smart-contract or venue-controlled settlement arrangements. The exact interface/custodian legal operator and security coverage cannot be inferred from decentralised branding.

Client eligibility

Wallet and platform terms determine access, with jurisdiction restrictions not comprehensively verified in this review; derivative suitability and sanctions checks may apply.

Support

Official documentation, help tickets and community support; irreversible on-chain actions and liquidations require transaction evidence.

Authorisation and registration scope

No regulator-issued licence for the correct interface operator established. Smart-contract deployment and governance do not equal financial authorisation.

Exchange metadata checked 26 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8Source 9Source 10Source 11

One useful threshold is the maximum funding payment and adverse price move a leveraged position can survive, not merely the posted maker percentage. The second is a worst-case collateral withdrawal plan if off-chain matching is impaired while the L2 continues to record transactions. The third is how an option’s premium cap interacts with its notional-based trading charge and settlement fee.[5][4][3]

This profile is a desk-source analysis and does not constitute a live order-book liquidity test or an approved jurisdictional determination. Aevo is covered as a meaningful derivatives venue, not because its token is promoted or because it has a standard fiat on-ramp.[2][6]