Midas

Deposit USDC or USDG into a Midas mToken vault on Ethereum, Base, or Robinhood Chain and redeem standard or instant.

Midas is a real-world-asset issuer with five products on yield.xyz, each backed by a different strategy and each running its own standard and instant redemption vaults behind one deposit vault. KYC requirements differ per product: mTBILL and mROX are on-chain permissionless, while mGLO, mGLOBAL, and mF-ONE gate entry behind Midas onboarding.

Availability

Product	Network	Input token	Position token	KYC
mTBILL	Ethereum	USDC	mTBILL	Not required
mTBILL	Base	USDC	mTBILL	Not required
mGLO	Base	USDC	mGLO	Required
mGLO	Robinhood Chain	USDG	mGLO	Required
mGLOBAL	Ethereum	USDC	mGLOBAL	Required
mF-ONE	Ethereum	USDC	mF-ONE	Required
mROX	Ethereum	USDC	mROX	Not required

List the Midas yields enabled for your project with GET /v1/yields filtered by providers=midas. Yield ids follow {network}-{inputToken}-midas-{product}-vault, for example ethereum-usdc-midas-mtbill-vault.

For the products with kycRequired: true, the yield’s kyc metadata sets kycMode to external_redirect and carries an issuer onboarding URL; see RWA KYC for the generic flow. mTBILL and mROX set kycMode to none: entry is on-chain permissionless. On every product, yield.xyz checks the wallet against Midas’s on-chain allow-list (where enabled), deny-list, and sanctions list before building a transaction, regardless of the KYC flag.

Entering

The enter argument is amount, in the vault’s input token. Before building the transaction, yield.xyz reads the deposit vault’s live minimum and reverts a deposit below it; the minimum is returned dynamically in mechanics.arguments, not fixed per product. Depositing calls the deposit vault’s depositInstant, so entry always settles in a single transaction regardless of which redemption path you later choose to exit with.

The yield’s status.enter is false while the product’s deposit vault has minting paused.

Exiting

Each Midas product exposes two separate redemption vaults for the same position token: a standard vault and an instant vault. The exit argument useInstantExecution (optional, boolean) picks between them; omit it for standard redemption.

Standard redemption is a request, not an instant payout. It calls the standard vault’s redeemRequest, and Midas settles it off-chain on an estimated multi-business-day timeline. There is no separate claim action: the input token lands in your wallet automatically once Midas fulfills the request, and the position balance clears at that point.

Instant redemption (useInstantExecution: true) calls the instant vault’s redeemInstant and settles in the same transaction, subject to the instant vault’s available on-chain liquidity at the time of the request. The yield reports one status.exit flag for the product: it is false only when every redemption path is paused, so an open standard path keeps it true while the instant path is paused.

Redemption below the vault’s live minimum reverts; like the enter minimum, it is returned dynamically rather than fixed per product.

Rewards, schedule, and fees

Yield accrues in the mToken’s price per share; there is no separate claim step, reward claiming is automatic. Which fee types you can configure on this yield is listed in mechanics.possibleFeeTakingMechanisms; see Monetization.

All five products expose investmentSchedule metadata describing their processing windows, so you can show subscription and redemption timing without polling on-chain state.

Next steps

RWA KYC

Discover KYC requirements and route users through issuer onboarding.

Action lifecycle

Request, sign, and submit enter and exit actions.