
Over the past few years, the vast majority of investment in on-chain yield has targeted strategy optimization. Risk curators tirelessly evaluate protocols, scale positions, monitor collateral, and rebalance portfolios as market conditions evolve. Today, these automated strategies manage billions of dollars across lending, liquidity provision, staking, and tokenized real-world assets. However, the connection between these high-performing vaults and the end users they serve has been largely neglected, becoming the primary bottleneck to mainstream adoption.
A wallet, exchange or fintech that wants to offer a vault still has to build the interface between that vault and its users. That interface reads positions, prepares deposits, handles token approvals, routes transactions through the user's wallet and explains withdrawals that can take days to settle. Each task is small on its own, but together they can take weeks of engineering time per vault, and many product teams defer the integration for that reason.
Sentora built the Smart Yield Integration Widget to take that work off the integrator's roadmap. Every Sentora Smart Yield Vault now includes generated code that gives a product a working deposit and withdrawal interface, configured for that vault and for the wallet provider the product already uses. The code runs on the Sentora SDK and covers the three vault families behind Smart Yield Vaults: Morpho, Boring (built by Veda) and Upshift.
This article covers the track record behind Smart Yield Vaults, what the widget generates, what users experience once it is live, and how platforms can earn from the integration and partner with Sentora.
Why Sentora Smart Yield Vaults
Smart Yield Vaults hold Sentora-designed strategies across lending, liquidity, staking and tokenized asset markets. A user deposits a single asset, and the vault spreads it across multiple venues, monitors collateral, liquidity and utilization continuously, rebalances as conditions change and carries risk cover inside the vault structure. A platform inherits all of this from the first deposit, so it can offer on-chain yield without building a strategy desk.
The same strategies already run at scale for some of the industry's largest platforms:
Scale. Sentora-curated vaults hold about $2.4 billion, making Sentora the second-largest risk curator tracked by DefiLlama as of November 2026.
Kraken. Sentora curates all four vaults in Kraken DeFi Earn, which reached nearly $1 billion in deposits across more than 100,000 active depositors within, with no liquidations.
EtherFi. Sentora's strategies powered four EtherFi Liquid vaults, which grew from zero to $1.4 billion in TVL in just over a year.
Embedded vaults. Fireblocks launched its Earn product with a Sentora-curated vault, and Privy already lists Sentora-curated vaults in its Earn product. These same vaults can be implemented through this widget.
Where the Integration Work Sits
A vault contract exposes a small set of functions: deposit, redeem and a few read functions. Executing these function calls from an application is standard, so the bulk of the engineering work lies in implementing the supporting execution logic. That logic falls into four areas:
Share accounting. Vaults issue shares, and the value of each share in the deposit token changes over time. The interface reads the user's shares, converts them to assets at the current rate and formats both with the correct decimals. Stablecoins such as USDC and PYUSD use six decimals, while shares can use six or eighteen depending on the vault. Sentora's Morpho PYUSD vault uses eighteen for shares, and its Boring USDC vault on Ink uses six, so a mismatch can produce balances that are wrong by a factor of a trillion.
Transaction preparation. Depositing an ERC-20 token, the standard token format on Ethereum, usually requires an approval transaction before the deposit. The interface checks the existing allowance and requests an approval only when needed. Before either step, it confirms that the user has enough balance, is on the correct chain and is depositing into a vault that accepts funds.
Withdrawal settlement. Some strategies cannot exit positions immediately without passing costs to other depositors. For example, staked assets with an unbonding period or lending positions with limited available liquidity. Vaults running these strategies settle withdrawals asynchronously: the user submits a redemption request, and the funds arrive later, either when a solver fills the request or on a claim date set by the vault's timelock. Queued shares drop out of the user's vault balance, so an interface that ignores this flow leaves users unable to see where their funds are or when they will arrive.
Wallet connection. Consumer products increasingly use embedded wallets from providers such as Privy and Dynamic, which create a wallet for the user at sign-up. Each provider exposes its transaction signer differently, so code written for one provider needs changes before it works with another.
These tasks are repetitive, easy to get slightly wrong, and specific to each vault and wallet provider. That combination makes them well suited to code generation, which is the approach the widget takes.
What the Widget Generates
Each vault page on vaults.sentora.com includes an integration widget. Its header lists the details a product team needs to evaluate the vault, including the chain, deposit token, 7-day APY, TVL and contract address. The team selects the wallet provider and framework it already uses, and the widget produces a working deposit and withdrawal interface configured for that vault, together with a short setup guide.
The main difference between vaults is how withdrawals settle, which shapes the experience a platform offers its users. Smart Yield Vaults run on three vault technologies:
Vault technology | How withdrawals settle | Example vault |
Morpho | Synchronously. The withdrawal redeems the shares and returns the tokens in the same transaction. | Morpho Sentora PYUSD Main V2 (Ethereum) |
Boring (built by Veda) | Asynchronously. The request enters the vault's queue, and a solver fills it after a waiting period set by the vault, with no separate claim. | Advanced Strategies USDC (Ink) |
Upshift | Asynchronously. The timelock gives each request a claim date a few days later, or the user can withdraw instantly for a small fee. | Sentora USD (Ethereum) |
The team can run the generated code in StackBlitz, a browser-based development environment, before adding it to its product. Once copied, the code belongs to the integrator, who can restyle the interface to match the product or replace it entirely. File structure, setup steps and configuration details are covered in the Sentora developer documentation.

What Your Users Experience
Before a user signs anything, the generated code checks whether the deposit or withdrawal can go through, for example whether the user has enough balance, whether the vault is accepting deposits and whether the amount fits within the vault's cap. If a check fails, the interface explains why before the user pays any gas. When a deposit needs a token approval, the interface requests it first and then completes the deposit, so the user follows one guided flow.
Withdrawals settle according to the vault technology:
Morpho vaults pay out in the same transaction, so the user receives the tokens at once.
Boring vaults queue the request, and a solver fills it after a waiting period set by the vault, sending the tokens straight to the user's wallet.
Upshift vaults give each request a claim date a few days later and usually pay out automatically on that date. Users who prefer to skip the wait can withdraw instantly for a small fee.
For queued withdrawals, the interface shows the pending amount and its expected timing, so users can always see where their funds are.

The widget supports self-custody browser wallets as well as embedded wallets from Privy and Dynamic. The vault logic is identical across providers and only the wallet connection changes, so a platform can launch through the sign-in flow it already runs. Setup for each provider is covered in the developer documentation.
Wallet Providers Supported at Launch
The choice of wallet provider determines which users a product can reach, so the widget supports both self-custody browser wallets and embedded wallets from the first release.
Provider | Background | Typical integrator |
Browser wallets | Injected wallets such as MetaMask and Rabby | Products whose users already hold a self-custody wallet |
Privy | Embedded wallet infrastructure, part of Stripe, used by more than 1,000 developer teams | Consumer and fintech apps that create wallets at sign-up |
Dynamic | Authentication and embedded wallets, part of Fireblocks, used by products including Kraken's Inky and Ondo Finance | Products that connect consumer wallets to Fireblocks' institutional infrastructure |
Embedded wallet support means a product can offer Smart Yield Vaults to users who have never installed a crypto wallet, through the sign-in flow the product already runs.
What Changes for Integrators
The widget moves the generic part of the integration from the product team to generated code. The team's effort shifts to the work that is specific to its product: design, user communication, eligibility checks and support.
Integration task | Building in-house | With the widget |
Share accounting and formatting | Written and tested per vault | Generated for each vault |
Approvals and deposit sequencing | Custom logic | Prepared automatically in the right order |
Pre-transaction validation | Custom checks | Checked before the user signs, with a clear reason if blocked |
Asynchronous withdrawals | Custom state and claim flow | Handled for each vault type, with pending withdrawals shown to the user |
Wallet provider support | Rewritten per provider | Selected in the filter |
User interface | Built from scratch | Ready-made interface the team can restyle |
Time to launch | Weeks of engineering per vault | Several hours for finalizing a live proof of concept |
Because the widget only generates the interface layer, a product that integrates through it offers the same Sentora-curated vaults that allocators use directly, with the same strategies, continuous risk monitoring, automated rebalancing and cover. Integrators should link to each vault's page on vaults.sentora.com so their users can review holdings, performance and risk context.
How Integrators Earn and Partner With Sentora
A yield product gives users a reason to keep their balances on a platform, and it gives the platform a new revenue line built on those balances. The widget lets a product team offer that yield without taking on strategy research, venue diligence or risk monitoring.
Platforms that want a product built around their own requirements can work with Sentora on Protected Earn, a savings, rewards or yield program configured to the platform's mandate, branded as its own and offered only to its users.
To discuss a partnership, commercial terms or a custom program, book a demo with Sentora and the team will walk through the options for your platform.
Limits and Considerations
Generated code reduces the engineering work of an integration, while the vault's risk profile and the integrator's obligations stay the same. Deposits remain exposed to smart contract, market, liquidity and venue risk, and returns are variable. Integrators are responsible for the eligibility and jurisdictional requirements that apply to their users, and some Sentora products and services are not available to U.S. residents.
Before launch, the integrator's team also sets up a dedicated connection to the vault's blockchain, writes clear user messaging on withdrawal timing and fees, and tests the flow with a small real deposit. The developer documentation covers each of these steps.
Conclusion
On-chain yield strategies have matured and now run at institutional scale, which moves the constraint on adoption to distribution: the cost for a product to put a vault in front of its users. The Smart Yield Integration Widget reduces that cost to choosing a vault, a wallet provider and a framework, and gives any platform access to the same allocation, risk monitoring and cover behind Sentora's institutional deployments.
Product and partnership teams can explore every vault at vaults.sentora.com and book a demo with Sentora to discuss integration and commercial terms. Developers can open the widget on any vault page and find the full integration guide in the Sentora developer documentation.






