Ctrlk
Launch app
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

This section is for integrators building on top of KPK vaults: wallets adding an Earn section, fintech apps offering yield to end-users, custodians and CEXs allocating client assets, and distribution partners that want to charge a fee on top of KPK strategies.

End-users who simply want to deposit should use the protocol UI directly. Vault addresses, supported assets, and current parameters are listed on each vault page.

This page covers the protocol-agnostic shape of an integration: who is integrating, what they need to build, and which functions to wire up. For protocol-specific nuances (SDKs, batch flows, referral codes, fee wrappers), follow the links into the per-protocol pages:

Cover

Morpho

Cover

Euler

Cover

Gearbox

Pick your integration path

Wallets and fintech apps

Adding an Earn section to a wallet, neobank, or savings app where users hold their own keys.

Existing dApps and aggregators

Already have an Earn product; just need vault references and the right SDK or interface.

Custodians and CEXs

Allocating from a custodial wallet via direct contract calls.

Distribution partners

Want to charge a performance or management fee on top of a KPK vault.

Building an Earn section

If you don't yet have an Earn surface, this section walks through what to build and how the pieces connect. If you already have one, skip to SDKs and direct integration.

An Earn section gives users a way to put idle assets to work. They deposit from their own wallet, yield accrues over time, and they can withdraw whenever they want. No intermediary holds the funds; every interaction is between the user's wallet and the vault.

What to build

A complete Earn integration covers four areas:

  • Position display. Show the user their current deposit, accrued yield, current APY, and any claimable rewards. Update in real time.

  • Deposit and withdrawal flows. Deposits require an asset approval (or permit signature) before the deposit transaction; withdrawals are a single call. Give users clear feedback on what's happening at each step.

  • Rewards. Some vaults distribute additional incentive tokens on top of base yield. Surface claimable amounts and let users claim independently of their deposited position.

  • Monitoring. Refresh user position and yield data continuously, and surface meaningful changes to vault parameters when they happen.

Integration checklist

  1. Pick the vault(s) from the vault directory and copy the addresses from each vault's Key information table.

  2. Choose the integration path based on which protocol(s) the vault(s) live on:

  3. Display vault APY and the user's position via the relevant SDK or contract reads.

  4. Build the deposit flow following the per-protocol page.

  5. Build the withdrawal flow following the per-protocol page.

  6. Surface claimable rewards via the Merkl API where applicable.

  7. Set up real-time refresh for position and yield data.

SDKs and direct integration

All KPK vaults are ERC-4626 compliant, so any integrator can interact with them via the standard deposit, withdraw, redeem, previewDeposit, and previewWithdraw methods. Each protocol exposes additional helpers and routing on top of the ERC-4626 surface:

  • Morpho-hosted vaults are best integrated through the Morpho SDK. The SDK handles approvals, permit signatures, slippage protection, and bundler routing into the underlying v1 markets. See Morpho integration for code samples.

  • Euler-hosted vaults can be integrated either through Euler's EVK batch() flow (recommended when bundling Permit2 + deposit) or via direct ERC-4626 calls on the vault. See Euler integration.

  • Gearbox-hosted vaults are integrated through direct ERC-4626 calls, with depositWithReferral used in place of the standard deposit so KPK is correctly attributed. See Gearbox integration.

Direct contract integration

For custodians, CEXs, and onchain protocols that prefer raw contract calls without a JavaScript SDK, all KPK vaults expose the standard ERC-4626 interface: approve the vault on the underlying asset, then call deposit(assets, receiver) or withdraw(assets, receiver, owner) on the vault.

The protocol-specific deposit and withdrawal flows below cover the additional steps each protocol requires (bundlers, batch calls, referral codes):

Fee wrappers for distribution partners

Distribution partners can request KPK to deploy a fee wrapper on top of a curated vault, charging their users a performance or management fee on the underlying KPK strategy without changing the vault itself.

Fee wrappers are currently available for Morpho-hosted vaults through the Morpho Fee Wrapper. See Morpho integration → Fee wrapper for the full feature set, including flexible fee configuration and optional permissioned setups.

For partners interested in a fee arrangement on a Euler- or Gearbox-hosted vault, contact sales@karpatkey.com or use the contact form to discuss what's possible.

Protocol-specific integration

For deposit and withdrawal flows, SDK details, and protocol-specific quirks (bundlers, batch calls, referral codes, fee wrappers), follow the relevant protocol page:

Support

For integration questions, technical reviews, or hands-on help, reach out to sales@karpatkey.com or use the contact form.

PreviousSigner architectureNextMorpho

Last updated