Concrete

About

Our Concrete integration facilitates supplying assets into the vaults on Concrete protocol. Concrete vaults are ERC-4626 compliant on the deposit path: upon deposit, users receive a vault share token and yield accrues automatically through share-price appreciation (exposed as pricePerShare). Each vault accepts a single deposit asset and routes liquidity across curated DeFi strategies. Shares are redeemable for the underlying token through an epoch-based withdrawal queue.

Pending Actions

Claim Withdrawal

Concrete vaults run an epoch-based withdrawal queue on the exit path. A withdrawal does not pay out immediately — it moves the user's shares into the current epoch, which is processed off-chain on a weekly cadence. Once the epoch is processed, users claim their unstaked balance using the CLAIM_UNSTAKED pending action to receive the underlying asset back. Both the in-progress (unstaking) and claimable (unstaked) balances can be tracked via our /stake/balances endpoint.

Considerations

• Queue-based Withdrawals: Withdrawals are not instant. After requesting a withdrawal, the user's shares are queued into the current epoch and become claimable only after the epoch has been processed (roughly a weekly cutoff and payout cycle).
• Per-epoch Limits: Each vault enforces per-epoch minimum and maximum withdrawal limits. A withdrawal request below the minimum or above the per-epoch maximum is rejected; max withdrawals are automatically capped to the per-epoch limit.

List of Integration IDs

Ethereum