Execution, Routing & Custody

Fees & protocol disclosures

We charge a simple, transparent fee on capital, applied once at deposit and once at withdrawal. There are no hidden management fees, no performance cuts, and no subscription charges.

All Midas fee logic is enforced on-chain and verifiable. The platform deposit fee is charged at the time of multicall execution — it is never applied speculatively or in advance.

Third-party protocol fees

Strategies on Midas route through external DeFi protocols — Vesu, Endur, Ekubo, Troves, AVNU, and others. Each of these protocols may charge their own fees: supply APY haircuts, borrowing costs, swap fees, LP fees, or staking queue costs. These fees are native to those protocols and are not controlled or collected by Midas. You should review the documentation of each underlying protocol before executing a strategy. Midas is not responsible for fees charged by third-party protocols.

Non-custodial design

Midas is fully non-custodial. The platform never holds your keys, controls your funds, or acts as an intermediary between you and the underlying protocols.

Your wallet, your execution. Every strategy is compiled into a Starknet multicall and executed directly from your own wallet via a single signature. Midas constructs the calldata — it never submits a transaction on your behalf without your explicit approval.

Positions land in your wallet. Every resulting position — vault shares, LP NFTs, staked tokens, borrow debt — is credited directly to your wallet address. Midas holds nothing at rest between transactions.

Atomic execution. Starknet multicalls are atomic. If any step in a strategy fails, the entire transaction is reverted. There is no partial state where Midas holds your funds mid-execution — it's either all-or-nothing, in a single block.

No standing approvals. You only approve the exact amount needed for each transaction. We do not request open-ended token allowances. Each strategy execution starts with a scoped approval and cleans up after itself.

Zero custody at rest. The upcoming Strategy Router contract enforces an on-chain ends-empty rule: its token balances must be zero at the end of every transaction. This is asserted at the contract level, not assumed. The router is a plan executor, not a vault.

All protocol contracts are deployed on Starknet mainnet at publicly verifiable addresses. You can inspect every call Midas constructs before you sign it in your wallet.

Execution & routing

When you execute a strategy on Midas, the platform compiles your chosen preset and routes it into an array of on-chain protocol calls, then executes them as a single atomic multicall from your wallet.

How it works

Step 1 — Live data fetch. Before you can sign, Midas pulls live pricing, current APYs, borrow parameters from each protocol, and swap quotes. Nothing is hardcoded. If live data is unavailable for any leg, that leg shows as unavailable and execution is blocked rather than proceeding with stale numbers.

Step 2 — Pre-execution safety gate. A series of checks run server-side to validate your balance, available borrow capacity, oracle freshness, deposit bounds, and execution price. If any check fails — including gas estimation — execution is blocked entirely. There is no "proceed anyway" bypass.

Step 3 — Calldata compilation. The backend compiles each strategy step into its corresponding on-chain call against the relevant protocol. Each call is sized from live oracle data.

Step 4 — Single signature, atomic execution. All calls are bundled into one Starknet multicall. You sign once. The transaction either succeeds entirely or reverts entirely — there is no in-between state. Gas is only spent on success.

Step 5 — Positions recorded. After on-chain confirmation, your position is recorded in the Midas backend and appears under My Positions. The actual assets and positions remain in your wallet; Midas only stores metadata for display.

Swap routing

All token swaps within strategies are routed through a DEX aggregator that sources the best available price across on-chain liquidity venues. A minimum output is enforced on every swap, so you are never exposed to unbounded slippage.

Step types