Skip to main content

​
Compounding boundaries

The current implementation checks a protected raw reward balance, finite allowance, permission expiry, the output destination, and minimum output. Price guards bind a reference pool and require price history; the selected guard uses at least 15 minutes of history and a 1% spot/history deviation limit. These checks can make a compound wait or revert. They do not guarantee profit or preserve a token’s dollar value. You can revoke the reward-account delegation independently through a compatible wallet.

​
Lending boundaries

Collateral and liquidity live in program-controlled vaults. Debt, position health, market liquidity, and lifecycle restrictions govern withdrawals and borrowing. Liquidation can lead to loss of collateral. LP positions can lose value compared with holding the underlying assets.

​
Token and issuer controls

Some RWA and Token-2022 issuers can freeze, pause, restrict, or seize assets. A supported token can later become non-transferable. ANVIL cannot override issuer controls or promise redemption into the underlying real-world asset.

​
Upgrades and dependencies

Program behavior can change if an authorized upgrade is deployed. Governance configuration, wallet software, RPC services, swap venues, pricing sources, and transaction delivery are also part of the system’s operation. Current-code protections should not be read as a promise about every future upgrade.

​
Verification status

ANVIL uses in-house engineering checks, including local program tests and account-replay validation. Those checks are not an independent audit and do not by themselves prove a deployed mainnet release matches the tested source. See addresses and release status. Never enter a recovery phrase or private key into a documentation page or ANVIL’s app. Verify full token and program addresses rather than trusting a symbol alone.