In-Kind Backing: How Onchain ETFs Stay 100% Backed

What In-Kind Backing Actually Means

In-kind backing means every token in circulation is matched by the actual assets it represents, held in a vault you can inspect, not promised on a balance sheet you can't read. The term comes from traditional ETFs, where authorized participants create shares by delivering the underlying securities "in kind" rather than cash. Onchain, the same principle applies with fewer intermediaries: an index token is minted only when the underlying assets enter a smart-contract vault, and burned when a holder redeems them back out.

That mint-and-burn logic creates a hard invariant: circulating supply always corresponds to the assets sitting in the vault. There is no gap between what the token claims to be and what it is, because the code makes a gap impossible. That is the difference between a fully backed token and a token that merely tracks something.

Synthetic, IOU, or Asset-Backed Crypto: Three Trust Models

Not every token that references an asset actually holds it. Broadly, there are three models, with very different risks:

• In-kind: the vault holds the real assets. Minting requires depositing them; redeeming returns them. Backing is structural, not reputational.
• Synthetic: the token tracks a price using derivatives or unrelated collateral. You get exposure rather than ownership, plus liquidation risk, funding dynamics, and depeg risk under stress.
• IOU / custodial: a company holds the assets offchain and issues a claim. You are trusting books you can't read and a custodian who can freeze withdrawals, rehypothecate, or fail.

Most of crypto's worst blowups happened in the second and third categories: the assets weren't there, or the collateral unwound exactly when it mattered. Asset-backed crypto in the in-kind sense removes the question. The assets aren't attested to exist; they observably do.

Redemption Is the Real Guarantee

Backing without redemption is decoration. What makes in-kind backing enforceable is that any holder can exit into the underlying assets at any time. If the token ever trades below the value of its basket, arbitrageurs buy it, redeem it, and sell the parts, pushing the price back toward fair value. The same mechanism keeps traditional ETFs near NAV, except onchain it is permissionless: you don't need to be an authorized participant, and settlement is atomic.

This is why "redeemable" is a stronger word than "backed." A token can be technically backed while redemption is gated, paused, or reserved for insiders. In that case the backing does you no good in a crisis, which is exactly when you would need it.

Proof of Backing: Verify Vault Holdings Yourself

The strongest proof of backing is the one you run yourself. For any onchain vault-backed token, verification takes a few minutes on a block explorer:

• Find the vault contract address. Project docs or the token contract itself should reference it.
• Read the index token's total supply from the explorer.
• Check the vault's balance of each underlying asset in the explorer's token-holdings view.
• Divide holdings by supply to get per-token backing, and compare it against the stated basket weights.
• Confirm the source code is verified and that minting and burning are tied to deposits and redemptions in the code itself.

No permission, no PDF, no auditor. And because it is onchain state, you can repeat the check at any block, including historical ones, to confirm the backing has held continuously, not just on the day someone published a snapshot.

Proof of Reserves vs. Continuous Onchain State

After FTX collapsed, centralized exchanges popularized proof of reserves: periodic attestations, sometimes with Merkle trees, showing assets exceeded liabilities at a point in time. It is better than nothing, but the holes are well known: it is a snapshot, assets can be borrowed for the photo, liabilities are often self-reported, and you are still trusting an auditor's methodology between reports.

An onchain vault inverts this. The state is the audit:

• Frequency: point-in-time snapshots vs. every block, forever.
• Liabilities: self-reported by the exchange vs. the token's total supply, visible onchain.
• Verifier: an auditor you have to trust vs. anyone with a block explorer or RPC endpoint.

There is no reporting interval to game, because there is no reporting interval. For a vault-backed token, proof of reserves collapses into simply reading the chain.

Immutability and No Admin Key

Backing is only as strong as the power to change the rules. If a contract is upgradeable or controlled by an admin key, then "the vault holds the assets" is true only until someone with the key decides otherwise. They can upgrade the logic, redirect withdrawals, or mint unbacked supply. Every verification from the checklist above can be invalidated by a single transaction you didn't see coming.

Immutable contracts close that hole: the rules at deployment are the rules forever, and no one, including the team that deployed them, can touch vault assets outside the mint-and-redeem path. The honest tradeoff is that immutability cuts both ways: bugs can't be patched either. Smart-contract risk doesn't vanish; it gets frozen in with everything else. That is why verified source code and audits matter more for immutable systems, not less.

How Tessera Applies In-Kind Backing

Tessera, an onchain ETF platform on Base, is a working example of this model end to end. Each index token is a single ERC-20 backed in-kind by a basket of 2 to 30 assets held in a smart-contract vault. You buy with USDC or ETH, and a single trade routes across up to roughly six DEXs and ERC-4626 vaults to assemble the basket atomically. You never buy the legs individually. Redeem anytime and the underlying comes back out. Baskets are immutable once deployed, there is no admin key, and anyone can create one permissionlessly.

The verification checklist above applies directly: supply, vault balances, and mint/redeem logic are all public onchain state. That holds whether the basket is an "Index" of narrative assets like WETH, cbBTC, or Base memecoins, or an "Earn" basket of yield-bearing assets such as liquid staking tokens and ERC-4626 vault positions that compound while held.

None of this removes risk. This is DeFi, not a regulated securities product: the underlying assets can fall in value, and smart-contract risk exists even in immutable code. In-kind backing ensures the token equals its basket. It says nothing about what the basket is worth. Do your own research before holding any of it.