Skip to main content
Makina offers managed strategy vaults on Ethereum. Each vault accepts a specific deposit asset and issues a corresponding share token. As the strategy earns yield, the value of each share increases relative to the underlying deposit asset.

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 an APPROVAL 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 exit amount 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:
  1. Request a withdrawal: The exit action returns an APPROVAL transaction for the share token, if needed, followed by an UNSTAKE transaction that creates a redemption request with Makina.
  2. Wait for finalization: While the request is pending, the balances endpoint reports it as a separate exiting balance denominated in the deposit asset. The amount is an estimate, tokenId identifies the redemption request, and date indicates the earliest expected unlock time. The current cooldown period is 2 days, as reported in cooldownPeriod, although Makina may finalize the request later.
  3. Claim the withdrawal: Once Makina finalizes the request, the balance changes to withdrawable and includes a CLAIM_UNSTAKED pending action. Executing this action transfers the redeemed assets to your address.
Each redemption request must be claimed individually using its own 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, set useInstantExecution: 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.
Important
  • Full withdrawals: useMaxAmount is not supported. To withdraw an entire position through queued redemption, pass the active balance’s amount as the exit amount. Fetch the latest balance immediately before building the transaction, since its value changes with the share price.
  • Whitelisted addresses: Makina may restrict direct deposits and queued redemptions to approved addresses. Requests from non-whitelisted addresses return HTTP 401 (Unauthorized).
  • DUSD instant exits: Instant withdrawals are not supported for DUSD. Its exit arguments do not include useInstantExecution, and passing this argument returns HTTP 412 (YieldUnderMaintenanceError). Check mechanics.arguments.exit for useInstantExecution before displaying the instant exit option.

Rewards and position

Makina distributes yield through increases in the vault’s share price rather than through separate reward tokens. Your active 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.