How a new blockchain ecosystem grows TVL and DeFi liquidity

Emissions reliably buy TVL. Keeping it after the programme ends is a different problem, and it's the one worth designing for.

A new blockchain ecosystem grows durable TVL by giving its canonical stablecoin somewhere productive to sit from day one, usually an anchor vault that routes deposits into strategies across the chain's own lending markets and DEXs. Incentives accelerate the initial fill, and the version that lasts replaces those incentives with organic strategy yield before the emissions taper, so liquidity has a reason to stay.

The sequencing is what separates ecosystems that hold liquidity from ecosystems that rent it. A programme that launches incentives before there is anywhere to deploy capital productively ends up paying for balances that sit in a wallet, generate no protocol activity, and leave the week the rewards stop. Getting the yield venue live first, then incentivising into it, produces a very different retention curve for roughly the same spend.

Why do incentive programmes usually fail to retain liquidity?

Incentive programmes fail on retention because they pay for a balance rather than for the activity that makes a balance useful. Mercenary capital is rational: it arrives for the highest available subsidy, contributes no borrowing demand or trading volume, and rotates to the next programme when the yield compresses. The chain gets a TVL number for a quarter and very little compounding.

What actually creates stickiness is a stablecoin that earns something without the subsidy. Once a balance is sitting in a position that pays from lending demand or a real strategy, the decision to leave has a genuine opportunity cost, and the balance starts supporting the borrowing and trading that other applications need. The chains that have retained stablecoin liquidity through a full incentive cycle generally had a productive default destination before the campaign started.

There's a second-order effect worth naming. A stablecoin with a credible yield venue becomes easier for wallets, exchanges and payment apps in the ecosystem to integrate, because they can offer their own users a rate without building anything. That turns the chain into a distribution channel for its own liquidity, which is a compounding asset in a way an emissions budget is not. Gauntlet's Idle USDC Report is a useful read on how much stablecoin balance sits unproductive across the market, which is the demand a chain is competing for.

What does an anchor vault do?

An anchor vault is a single conservative destination for the chain's canonical stablecoin, deployed at launch, designed to be the obvious answer to the question of where to put idle balances. It routes deposits across whitelisted venues on the chain, publishes its allocations, and gives every downstream application a yield source to point at rather than each one negotiating separately.

Upshift is non-custodial vault infrastructure for onchain yield, used by fintechs, exchanges, wallets, neobanks, chains and asset managers to launch custom yield products. earnAUSD on Monad is a live example of the anchor pattern: a stablecoin vault deployed as part of the ecosystem's launch, allocating into protocols on the chain.

It also demonstrates the distribution point. earnAUSD is live inside Tria, a neobank building on Monad, so a consumer app in the ecosystem can offer its users a yield product without running vault infrastructure of its own. That is the anchor working as intended: one vault, several front ends.

The scale it reached is the part worth borrowing from. earnAUSD passed $80 million in peak TVL within its first three months, on a chain that had only just launched, which is what a canonical stablecoin with a productive default destination can pull in.

Balances of that size move with the incentive cycle rather than sitting at a permanent high, which is exactly why retention through the taper is the metric that matters and peak TVL is not. The mechanics behind the vault are covered in the earnAUSD write-up, and there's a background explainer on Monad for readers unfamiliar with the chain.

The reason a chain generally shouldn't build this itself is the same reason a fintech shouldn't. Vault contracts, NAV accounting, fee logic, withdrawal processing, risk controls and an audit programme are a multi-quarter engineering commitment competing directly with core protocol work, and the ongoing cost is a permanent risk function rather than a one-time project.

As of July 2026 Upshift has processed more than $550 million in deposits at peak across over 50 vaults on more than 30 chains, with contracts that have completed 10 smart contract audits across 6 independent firms. Deploying onto that moves an ecosystem's timeline from quarters to weeks.

Vaults built to the ERC-4626 standard also give a chain something an in-house build usually doesn't: a receipt token other protocols can integrate without bespoke work.

That composability is where the ecosystem effect compounds. A lending market can accept the vault share as collateral, a wallet can display it as a balance, and a payments app can hold it as a yield-bearing float, all without a new integration each time. For teams building against a specific chain, the deployment details usually live in that chain's own developer documentation, as with Monad's docs.

Which parties need to be at the table?

Most ecosystem vault launches need four parties at the table rather than two, and naming them early avoids a stalled integration. Each one owns a piece none of the others can supply.

The curator is the role chains most often underestimate. A vault with no active allocation is a static lending position, and the difference between a mechanical deposit and a managed strategy is usually several hundred basis points on the same capital. Curators are typically hedge funds or asset managers, and on Upshift they allocate within limits the vault enforces at the chain, protocol, token and function level, so strategy discretion never becomes custody. Sentora runs vaults on the platform.

The custody row matters for institutional balances specifically. Whoever holds the assets has to be able to hold the vault's receipt token, which means the custodian needs to whitelist it, and that puts the custodian on the deal map as a counterparty rather than a vendor. Raising it during scoping avoids finding out during integration.

What should a chain have ready before launching a vault?

Five inputs determine whether a vault launch produces retained liquidity or a spike. A chain missing the first two will struggle regardless of how good the infrastructure is.

1. A canonical stablecoin decision. One asset the ecosystem treats as the default unit of account, with a clear issuer and a bridging path. Ecosystems running three competing stablecoins fragment their own liquidity and make every integration harder.
2. Live venues with real depth. A vault needs somewhere to allocate. Lending markets and DEXs with genuine borrowing demand are a prerequisite, since a curator cannot generate yield from venues that have no counterparties.
3. An incentive schedule with a taper published in advance, so the market understands the glide path rather than discovering a cliff. Front-loading is fine; surprising people is not.
4. A bridging and canonical-asset path that does not require a user to trust a bespoke bridge. Circle's Cross-Chain Transfer Protocol is the reference implementation most institutional participants are comfortable with.
5. Ecosystem applications lined up to integrate. The vault should have wallets and apps ready to route balances into it at launch, because the anchor is only an anchor if things attach to it.

How to tell whether it worked

Peak TVL is the least useful metric for judging an ecosystem vault, since it mostly measures the size of the incentive budget. The numbers worth tracking describe whether the liquidity is doing work and whether it stays once it stops being paid to.

Tooling for this exists without custom work. L2BEAT is useful for cross-chain comparison of where value actually sits, and Upshift's vault API exposes TVL, APY and allocation data for programmatic tracking. For chains whose strategy involves fixed-rate or yield-tokenised products, Pendle's documentation is worth reading on how a yield-bearing receipt token gets split into principal and yield components.

Risks a foundation should price in

Smart contract risk sits at the top of the list, and for a chain it carries reputational weight beyond the capital at stake, because a failure in an ecosystem's flagship vault reads as a failure of the chain. Audit history, per-protocol exposure limits and non-custodial architecture are the mitigations that matter. Funds moving only between the vault contract and whitelisted strategy contracts means neither the platform nor the curator can withdraw to an external wallet, and the risk management framework documents the buffer, the NAV volatility caps and the whitelisting model.

Concentration risk deserves more attention than it usually gets. Early ecosystem vaults are often filled by a small number of large depositors, sometimes including the foundation itself, and a balance built that way can leave in a single transaction. Tracking holder distribution from day one gives an honest read on how much of the TVL is a market and how much is a relationship.

Yields on these vaults are variable and depend on conditions across the venues the curator allocates into, so a foundation modelling ecosystem growth against a projected rate should model the compression case. Venue risk compounds it: a new chain's lending markets and DEXs are themselves young, and a curator's available strategies are constrained by what exists, which tends to mean fewer options and thinner depth than on established chains.

Always make sure to do your own research and be aware of the above and any other risks before depositing.

Frequently asked questions

Should a chain launch its vault before or after its incentive programme?

Before. A productive destination has to exist for incentivised capital to flow into, otherwise the programme pays for balances that sit idle and leave when rewards stop. Launching the vault first and then incentivising into it produces materially better retention for similar spend.

What is an anchor vault?

An anchor vault is a single conservative destination for a chain's canonical stablecoin, deployed at launch as the default answer for idle balances. It allocates across whitelisted venues on the chain and gives every downstream wallet or application one yield source to integrate rather than each negotiating separately.

How long does it take to launch an ecosystem vault?

Weeks rather than quarters when deploying onto existing vault infrastructure, since the contracts, risk controls, NAV accounting and withdrawal processing are already production-ready and audited. Building the same stack in-house is a multi-quarter commitment plus a permanent risk-management function competing with core protocol work.

Does a chain need its own stablecoin?

No, but it does need a canonical one. A single default asset with a clear issuer and a trustworthy bridging path is what makes integrations tractable. Ecosystems running several competing stablecoins fragment their liquidity and make every downstream integration harder than it needs to be.

Who runs the strategy in an ecosystem vault?

A curator, typically a hedge fund or asset manager, allocating within limits the vault enforces at the chain, protocol, token and function level. A chain can bring its own or use one already operating on the infrastructure. The distinction between a mechanical deposit and an actively curated strategy is often several hundred basis points on the same capital.

What metric shows whether the bootstrap worked?

Retention through the incentive taper, measured as the fraction of balance remaining 30 and 90 days after emissions step down. Peak TVL mostly measures the size of the incentive budget. Organic share of yield and borrowing demand against the stablecoin are the next two most useful.

Why does the custodian matter for a chain's vault?

Institutional balances sit with custodians, and a custodian has to whitelist the vault's receipt token before it can hold it. That makes the custodian a counterparty on the deal rather than a vendor, and it is worth raising during scoping instead of discovering it mid-integration.

Keep reading

• Earning stablecoin yield on Monad with earnAUSD is the anchor-vault pattern documented end to end.
• XRP vaults on Flare shows the same structure applied to a non-stablecoin ecosystem asset.
• What are DeFi yield vaults is the ground-up explainer on strategies and risk.
• Vault-as-a-Service documents what a chain configures versus what comes prebuilt.
• Multi-asset vaults covers the structure for ecosystems wanting more than one deposit asset.