Skip to main content
Before your users can deposit into a vault, your organization must deploy a fee wrapper for it. The wrapper is the contract users actually deposit into. It routes funds to the underlying vault, and the applicable fees accrue onchain to a fee splitter as yield accrues. Deploying it is a one-time activity per vault, with gas sponsored by Turnkey.

​
When to deploy

Deploy once per vault you want to offer, per fee configuration. Deposits into a vault with no deployed wrapper fail with EARN_SETUP_REQUIRED (see Deposit into a vault). Pick vaults from the vault catalog; the catalog’s enabled flag tells you which vaults your organization has already enabled.

​
Choose your fee configuration

The deploy intent carries your fee:
  • clientFeeBps: your fee on gross yield, in basis points ("2000" = 20%). It is capped at 4,000 bps; combined with Turnkey’s fee (10% of yield by default), the total cannot exceed 5,000 bps (50% of yield); deployments above the cap are rejected. See the fee model for current rates and caps.
  • clientFeeWallet: the address that receives your fee payouts onchain. It must be a wallet account owned by your organization; addresses outside your org are rejected.
The fee configuration is bound into the wrapper’s deterministic (CREATE2) address. Deploying the same vault with a different clientFeeBps or clientFeeWallet produces a new wrapper at a new address. Positions in the old wrapper remain fully withdrawable; new deposits should target the new wrapper. To change your fee, redeploy and point deposits at the new address.

​
Submit the activity

Submit an ACTIVITY_TYPE_EARN_DEPLOY_WRAPPER activity with the vault’s address (from the catalog), its CAIP-2 chain, and your fee configuration. For Aave, the catalog’s vaultAddress is the reserve’s underlying asset address; pass it through as-is. See Deploy Earn wrapper in the API reference for the full request/response schema and cURL example.
Aave only: Aave takes a small initial deposit at deployment and permanently locks it in the reserve, so a newly deployed Aave wrapper shows a small position straight away, about $1 for stablecoin reserves. Turnkey currently funds this deposit from its own wallet. See Aave’s deployment docs.
The activity result returns the deployed addresses immediately; they are derived deterministically before the transaction confirms:
  • wrapperAddress: the deposit target for this vault.
  • splitterAddress: the fee splitter that distributes fees between you and Turnkey (a PaymentSplitter for Morpho, a RevenueSplitterOwner for Aave).
  • deployRequestId: poll handle for the deployment transaction.

​
Poll deployment status

The activity completes when the deployment transaction is broadcast, not when it confirms. Poll get_earn_deploy_status with the deployRequestId until it reports COMPLETED before accepting deposits. status is PENDING, COMPLETED, or FAILED; on COMPLETED the response carries the deployTxHash, and on FAILED it includes an error field with the reason.

​
Gas and idempotency

Wrapper deployment gas costs are currently covered by Turnkey’s infrastructure and are not charged to you or your users. This is subject to change. Deployments are also idempotent: resubmitting the activity with identical parameters re-derives the same wrapper and splitter addresses and skips the broadcast if the contracts already exist, so retries are safe.

​
Next steps