Availability
Use
GET /v1/yields?providers=makina to retrieve the Makina vaults available to your project.
Each yield includes the vault’s current deposit and withdrawal status. When a vault reaches capacity, status.enter becomes false, while status.exit remains true. You can check state.capacityState for the vault’s current, max, and remaining capacity, denominated in the deposit asset, and state.pricePerShareState for the current share price.
Entering
To deposit into a Makina vault, the enter action returns anAPPROVAL transaction for the deposit asset, followed by a STAKE transaction that deposits the assets through Makina’s depositor and mints the corresponding share tokens to your address. The approval is skipped if the existing allowance is sufficient, and there is no warmup period after depositing.
You can configure slippage using the optional slippageBps argument, which accepts values between 1 and 1000 basis points and defaults to 50 (0.5%).
If a direct deposit is unavailable, the integration can route the deposit through the share token’s Uniswap pool instead. In this case, the action returns the required Permit2 approvals, if any, followed by a SWAP transaction to purchase the share tokens within the specified slippage tolerance.
Deposits that exceed the vault’s remaining capacity, contain invalid arguments, or originate from an address that is not whitelisted will return an error.
Exiting
Makina supports queued redemptions for all three vaults, with instant exits available for DETH and DBIT through Uniswap. The exitamount is always denominated in the underlying deposit asset (USDC, WETH, or WBTC), rather than in vault shares.
Queued redemption
By default, withdrawals follow a queued redemption process:- Request a withdrawal: The exit action returns an
APPROVALtransaction for the share token, if needed, followed by anUNSTAKEtransaction that creates a redemption request with Makina. - Wait for finalization: While the request is pending, the balances endpoint reports it as a separate
exitingbalance denominated in the deposit asset. Theamountis an estimate,tokenIdidentifies the redemption request, anddateindicates the earliest expected unlock time. The current cooldown period is 2 days, as reported incooldownPeriod, although Makina may finalize the request later. - Claim the withdrawal: Once Makina finalizes the request, the balance changes to
withdrawableand includes aCLAIM_UNSTAKEDpending action. Executing this action transfers the redeemed assets to your address.
CLAIM_UNSTAKED transaction. Claiming multiple requests in a single action is not currently supported.
Instant exit
DETH and DBIT also support instant withdrawals through Uniswap. To use this route, setuseInstantExecution: true in the exit arguments. Instead of creating a redemption request, the integration sells the vault shares through Uniswap and returns the underlying deposit asset in the same transaction.
The action returns any required Uniswap approvals, followed by a SWAP transaction. Instant exits depend on available pool liquidity and the configured slippageBps. Since the withdrawal completes immediately, there is no cooldown period or separate claim step.
Rewards and position
Makina distributes yield through increases in the vault’s share price rather than through separate reward tokens. Youractive balance represents the current value of your vault shares in the underlying deposit asset, including any accrued yield. There is no separate reward claim required.
The displayed reward rate uses Makina’s reported 7-day APY, falling back to the 30-day APY when the 7-day value is unavailable. These figures exclude MAK token incentives and Makina points.
List available yields
Use the following request to retrieve the Makina yields enabled for your project. We recommend fetching the available yields through the API rather than hardcoding yield IDs, as new markets and networks may be added over time.Next steps
Vaults
Explore other supported vault integrations and compare their deposit and withdrawal mechanics.
Action lifecycle
Learn how to execute deposit, withdrawal, and
CLAIM_UNSTAKED actions.
