The Complete Capital Path After Depositing Into an Afi Protocol Vault

Depositing into an Afi Protocol vault creates a defined chain of custody and accounting between the depositor, the on-chain vault, the asset backing the position, and the token issued to the user.

The exact path depends on the vault type. Afi Protocol describes two structures that should not be confused:

• a Proof-of-Reserve wrapper vault, where a tokenized RWA is locked and a reserve-verified receipt token is issued;

• a yield vault, where deposited stablecoins can be managed through approved DeFi strategies and the user receives yield-bearing shares.

In both cases, the deposited token leaves the user’s wallet and is replaced by a token representing a claim on the vault. Where the capital goes and how that claim changes are different.

The Basic Deposit Logic

The depositor first authorizes the relevant smart contract to transfer a supported asset and then submits a deposit transaction.

Once it succeeds:

1. The underlying asset enters the vault system.

2. The vault mints a receipt or share token to the specified receiver.

The received token is not an unrelated reward. It records the user’s claim while the underlying asset remains locked, held, or deployed according to the vault’s rules.

Path One: Depositing a Tokenized RWA Into a Proof-of-Reserve Vault

The clearest example is the institutional afi-rwaUSDi vault.

Its capital path can be summarized as:

Off-chain reserves → issued rwaUSDi → Afi Protocol vault → locked rwaUSDi → minted afi-rwaUSDi

Each step performs a separate function.

Step 1: The Real Assets Remain Off-Chain

The economic reserve does not physically move into the Afi Protocol smart contract.

Cash, fund interests, private credit, operating assets, commodities, or other eligible holdings remain with the issuer, custodian, fund structure, or assessed entity. Their safekeeping and legal ownership continue to depend on traditional arrangements.

Afi Protocol evaluates evidence about those reserves and publishes a verified result that on-chain contracts can use. The smart contract holds a tokenized representation, while the traditional assets remain off-chain.

Step 2: The Issuer Creates the Underlying RWA Token

The issuer creates rwaUSDi against the defined reserve structure.

The token contract can show supply and transfers, but it cannot independently inspect assets held by custodians. Afi Protocol adds another layer: the token must be connected to verified reserve information and locked inside a controlled vault before the Afi receipt token can circulate.

Step 3: rwaUSDi Is Deposited and Locked

An approved depositor transfers rwaUSDi into the Proof-of-Reserve Vault.

The deposited rwaUSDi becomes locked on-chain. It is no longer available in the depositor’s wallet and should not circulate beside the receipt token issued against it.

This prevents two transferable instruments from representing the same deposited collateral simultaneously. The original rwaUSDi becomes on-chain collateral, while the new token becomes the instrument intended for external use.

Anyone can inspect how much rwaUSDi the vault contract holds. However, that balance alone does not prove that the real-world backing still exists, so off-chain verification remains necessary.

Step 4: The Vault Checks Minting Capacity

The vault cannot safely mint receipt tokens based only on deposited rwaUSDi.

An issuer could theoretically create more units of its own token without adding real assets. The permitted receipt-token supply must therefore remain within both:

• rwaUSDi locked in the vault;

• off-chain reserves verified by Afi Protocol.

The vault must also account for afi-rwaUSDi already circulating.

Additional deposited tokens do not create capacity when verified reserves are lower. Large verified reserves also do not permit unlimited issuance when insufficient rwaUSDi has been locked.

This is a two-sided backing requirement: on-chain collateral and off-chain reserve evidence must support new circulation together.

Step 5: The User Receives afi-rwaUSDi

For the documented institutional vault, depositing rwaUSDi mints afi-rwaUSDi.

The structure uses a one-to-one relationship: one deposited rwaUSDi produces one afi-rwaUSDi, subject to access, capacity, and reserve rules.

afi-rwaUSDi is the receipt token. It records the user’s claim on the locked rwaUSDi and is designed for DeFi compatibility.

The underlying rwaUSDi stays in the vault. The user holds afi-rwaUSDi instead. This does not create double value because the deposited asset has been removed from circulation.

Where Is the Collateral Stored?

There are two collateral layers.

On-Chain Collateral

The deposited rwaUSDi is held by the Proof-of-Reserve Vault smart contract and remains visible on-chain.

Off-Chain Economic Backing

The traditional assets represented by rwaUSDi remain with the issuer, custodian, fund structure, or assessed entities. Afi Protocol verifies evidence about them but does not physically custody them through the vault contract.

Therefore, the tokenized collateral is inside the vault, while the economic reserve remains off-chain.

What Can the User Do With afi-rwaUSDi?

afi-rwaUSDi is designed as an ERC-4626-compatible receipt token.

Subject to actual integrations, access rules, liquidity, and the policies of receiving protocols, it can be suitable for treasury systems, liquidity pools, lending markets, market-making, or cross-chain infrastructure.

Compatibility does not guarantee universal acceptance. Every DeFi application must assess reserve, redemption, liquidity, and smart contract risk independently.

Transferability also differs from redemption. A token may move on-chain while primary redemption still depends on vault rules, issuer processes, available liquidity, eligibility, and off-chain settlement.

Path Two: Depositing Stablecoins Into the afiUSD Yield Vault

The capital path is different for afiUSD.

Here, the user deposits a supported stablecoin and receives afiUSD shares based on the current exchange rate. The capital does not necessarily remain idle in the main vault contract.

The documented flow is:

User stablecoin → afiUSD vault → Manager contract → approved DeFi strategies → performance reflected in the afiUSD exchange rate

Step 1: The User Deposits a Stablecoin

The user approves the vault to spend the supported asset and calls the deposit function.

The contract calculates how many afiUSD shares correspond to the deposit. The result depends on the current asset-to-share exchange rate, so the relationship does not have to remain permanently one-to-one.

Step 2: The User Receives afiUSD Shares

afiUSD represents a proportional claim on assets managed by the vault.

Yield does not need to arrive as a separate token payment. Positive strategy performance can increase the amount of underlying assets represented by each share. Recorded losses can reduce it.

The user may keep the same number of shares while their redemption value changes. This differs from the fixed one-to-one wrapper logic described for afi-rwaUSDi.

Step 3: Assets Move to the Manager Contract

Afi Protocol’s published afiUSD architecture states that deposits are transferred to a Manager contract.

The Manager coordinates asset deployment and interactions with approved external protocols. It can allocate capital across whitelisted strategies rather than leaving the entire balance in the deposit contract.

Some liquidity may remain within the vault system, while other capital is represented by positions held through strategy contracts. The vault accounting tracks the assets attributed to share holders across those locations.

Step 4: Capital Is Deployed Into Strategies

The Manager can deploy assets into whitelisted protocols under the active strategy and authorized operations.

The goal is to generate yield, but the process introduces economic and integration risk. Positions can produce profits, losses, liquidity delays, or exposure to external smart contracts.

The published architecture describes strategy calculations as off-chain driven and execution as on-chain. Users should therefore examine actual allocations, permissions, and protocol exposure rather than assuming every Afi Protocol vault stores capital identically.

Step 5: Performance Changes Share Value

When strategy performance is accounted for, the system updates the vault’s asset accounting and share-to-asset exchange rate.

A profit can increase the assets represented by each afiUSD. A loss can reduce them. The receipt token is therefore a proportional ownership record, not a guaranteed fixed-return instrument.

What Happens During Redemption?

The exit path reverses the deposit relationship but may not be instantaneous.

In the published afiUSD design, the user first requests redemption. The shares are burned, a withdrawal request is recorded, and a configurable cooldown begins.

During this period, the Manager can unwind strategies and return the required base assets. After the conditions are met, the user completes the withdrawal and receives the underlying token.

This process helps coordinate exits when capital is actively deployed, but it introduces waiting time and operational dependencies.

Redemption rules for a Proof-of-Reserve wrapper may differ because its principal asset is locked RWA collateral rather than a portfolio of yield strategies. Users must review the specific vault.

Why the Receipt Token Matters

The receipt token:

• records who owns a claim after the original asset leaves the wallet;

• maintains accounting across deposits, withdrawals, profits, and losses;

• provides a standardized asset for DeFi use while collateral remains locked or managed elsewhere.

Its reliability depends on the entire structure beneath it: the vault contract, reserve verification, custody arrangements, strategy exposure, redemption rules, and administrative permissions.

Key Benefits of the Capital Flow

For the RWA wrapper, locking the original token helps prevent simultaneous circulation of both collateral and receipt tokens. Proof-of-Reserve verification adds evidence that the off-chain assets supporting the collateral remain available.

For the yield vault, ERC-4626 shares provide standardized accounting while the Manager coordinates capital across approved strategies. Performance can be reflected through the exchange rate rather than separate payments to every wallet.

Both structures make the user’s claim programmable and potentially composable, but they solve different problems.

Risks and Important Limitations

After depositing, the user no longer controls the original asset directly. The position depends on the vault contract and its redemption process.

Smart contract vulnerabilities, administrative permissions, upgrades, pauses, capacity controls, and external integrations can affect access to funds.

RWA vaults remain exposed to custody, legal, valuation, liquidity, and issuer risk. A valid reserve proof does not automatically guarantee immediate redemption or priority during insolvency.

Strategy vaults can face losses in external protocols, liquidity constraints, operational errors, and strategies that fail to perform as intended.

Receipt-token liquidity can also differ from redemption liquidity. A secondary-market sale may occur at a discount when direct redemption is delayed or restricted.

Why This Matters for Project X and HyperEVM

No direct integration between Afi Protocol, Project X, and HyperEVM should be assumed without official confirmation.

The capital flow is still relevant to on-chain liquidity. If an Afi receipt token entered a Project X pool, liquidity providers would need to know what sits behind it.

For afi-rwaUSDi, the immediate on-chain collateral is locked rwaUSDi, while the economic reserve remains with off-chain entities. For afiUSD, capital may be distributed across managed DeFi positions.

Project X can provide trading infrastructure, but it cannot replace reserve verification or vault due diligence. HyperEVM compatibility would describe the technical environment, not guarantee asset quality, redemption liquidity, or legal enforceability.

FAQ

What Happens Immediately After a Deposit?

The underlying token is transferred from the depositor’s wallet into the vault system, and the vault mints receipt tokens or shares to the receiver.

Which Token Does the User Receive?

Depositing rwaUSDi into the documented institutional vault produces afi-rwaUSDi. Depositing a supported stablecoin into the afiUSD yield vault produces afiUSD shares.

Is the Real-World Asset Stored in the Smart Contract?

No. The contract holds the tokenized representation. The traditional assets remain with the relevant issuer, custodian, fund, or assessed entity.

Does Every Deposit Remain in One Vault Contract?

No. The Proof-of-Reserve wrapper locks rwaUSDi in the vault, while afiUSD deposits can move to a Manager and approved DeFi strategies.

How Does Yield Reach afiUSD Holders?

Performance can be reflected through a changing exchange rate, increasing or decreasing the amount of underlying assets represented by each share.

Can the User Redeem Immediately?

That depends on the vault. The published afiUSD design uses a redemption request and cooldown. RWA products may also depend on eligibility, liquidity, and off-chain settlement.

Does an Afi Receipt Token Remove Custody Risk?

No. It improves on-chain accounting and can connect supply to reserve verification, but custody, legal, valuation, strategy, liquidity, and contract risks remain.

Conclusion

The capital path in Afi Protocol begins when an asset leaves the user’s wallet and the user receives a tokenized claim on a vault.

In the afi-rwaUSDi Proof-of-Reserve wrapper, rwaUSDi is locked on-chain and the user receives afi-rwaUSDi. The traditional backing remains off-chain, while Afi Protocol verifies reserve evidence and constrains receipt-token supply.

In the afiUSD yield vault, the user deposits a supported stablecoin and receives afiUSD shares. Capital can move through a Manager into whitelisted DeFi strategies, with performance reflected in the exchange rate. Withdrawals may require a request, cooldown, and liquidity preparation.

Before depositing, identify the exact vault type, underlying asset, receipt token, custody location, reserve feed, strategy exposure, exchange-rate mechanism, and redemption process. The word “vault” describes the accounting interface, but the real capital path depends on the product behind it.