Receipt tokens, explained: how VXUSD represents your share of a yield strategy

The word "deposit" carries a hidden assumption. When you deposit money at a bank, you give it to someone who promises to give it back. Your claim is a database row in their system. If the database disappears, your claim disappears with it.

A receipt token is a different kind of claim. It's a token in your own wallet that says this much of that pool is mine. The bank's database is replaced by a smart contract on a public blockchain, and the row is replaced by a token only you can move.

For vildX, that token is called VXUSD. Here's what it actually does, and why it matters that the claim lives in your wallet rather than ours.

The mechanics

When you deposit $100 of USDC into the vildX vault, two things happen:

1. The vault contract adds your USDC to the pool and routes it across the managed strategy (Aave, Compound, Morpho, Curve).
2. The contract mints VXUSD tokens to your wallet, valued at the current NAV (net asset value per share).

If NAV is $1.02 when you deposit, you receive 98.04 VXUSD. If NAV is $1.10 a year later, those same 98.04 VXUSD are worth $107.84 of USDC at redemption. Your token balance doesn't change — the price of each token does.

That single design choice has a few important consequences.

You don't see "earnings" appear in your wallet

In a per-share model, the vault never sends you new tokens to represent yield. It can't, because that would dilute everyone else proportionally. Instead, the underlying pool grows, and the price of each share grows with it.

This is sometimes confusing for users coming from staking products that mint new tokens as rewards. The mental model to swap in is mutual funds: a Vanguard share doesn't multiply when the fund earns; it just becomes worth more. VXUSD works the same way.

Redemption is a smart-contract call

To withdraw, you call redeem(amount) on the vault contract. The contract burns your VXUSD and sends you USDC at the current NAV. There is no "withdrawal request" sitting in someone's queue waiting for human approval.

There is a 72-hour processing window — we explain why in the case for a 72-hour withdrawal window — but the right to withdraw is enforced by the contract, not by us.

The contract is the source of truth

Anyone can read the vault contract on-chain:

• Total assets under strategy
• NAV per VXUSD
• Allocations across each underlying protocol
• The address of every harvest, every rebalance, every fee transfer

If vildX as a company vanished tomorrow, the contract would still be there, and you would still be able to redeem. That is a meaningful structural difference from any custodial yield product. The trust assumption is "the audited contract behaves as written," not "the company behaves as advertised."

ERC-4626: the standard underneath

VXUSD is implemented as an ERC-4626 vault share. ERC-4626 is the Ethereum standard for tokenized yield-bearing vaults, and it specifies exactly which functions a vault must expose: deposit, withdraw, mint, redeem, totalAssets, convertToShares, and so on.

The point of the standard isn't elegance — it's that any wallet, any explorer, any third-party tool that supports ERC-4626 already knows how to read and interact with VXUSD. We didn't invent a custom token; we implemented the standard everyone else uses for this exact purpose. We unpack the standard in ERC-4626 explained.

You can transfer VXUSD

Because VXUSD is just an ERC-20 token, you can send it to another wallet, hold it in cold storage, or — in principle — use it as collateral elsewhere. The yield-bearing nature doesn't change. Whoever holds the token on the day of redemption gets the value.

We don't currently encourage active VXUSD trading or using it as collateral elsewhere because the secondary-market liquidity isn't deep enough to make that responsible, but the optionality is structurally there.

Where the trust still has to live

Receipt tokens move the custody trust assumption, but they don't eliminate all trust. You still have to trust:

• The vault contract code. That's what audits, allocation limits, and timelocks are for. We dig into this in smart-contract risk.
• The underlying protocols. If Aave were to suffer a critical exploit, the funds allocated there are at risk. The blended strategy mitigates this, but doesn't erase it.
• The strategy decisions. We choose which protocols to allocate to and when to rebalance. You trust that judgment to a real but bounded degree — the contract caps how concentrated any single allocation can be.

The trade is real: a receipt token gives you custody and verifiability in exchange for accepting different trust assumptions than a bank. For people who want better yield without the operational burden, it's the trade that makes the rest of the product possible.