Vestige Docs

OverviewProtocol modelFAQVault lifecycleAssets and balancesSecurity modelContract overviewFunction referenceDeployed contractsdApp integrationDeploymentLocal developmentOperational runbookEvents and indexingTroubleshooting
Introduction

FAQ

Common questions about Vestige protocol behavior, Arc Testnet deployment, dApp UX, and contract limitations.

Can one owner have multiple vaults?

Not at the same time. One owner address can have one existing vault lifecycle. After the vault is drained and disabled, the same owner can create a new vault.

Why are USDC functions payable?

Arc uses native USDC as the chain-native asset. Solidity receives native value through msg.value, so depositUSDC and depositUSDCFor are payable even though the user-facing asset is USDC.

claimInheritance vs claimUSDC

claimInheritance(owner) is the simple heir action: it activates inheritance and sends native USDC to the heir. claimUSDC(owner, receiver) is useful when the heir wants native USDC sent to a specific receiver address.

Why does the heir enter an owner address?

Without an indexer, the dApp cannot automatically discover every vault where the connected wallet is heir. The heir console reads a specific owner's vault by address. A future indexer can improve discovery.

Why claim tokens one by one?

Token-by-token claims prevent a single inheritance claim from depending on an unbounded token list. This is safer for gas and prevents one problematic token from blocking all other claims.

What if the owner returns during grace?

If the vault is in the grace window but not fully claimable yet, the owner can check in. That resets lastCheckIn and closes the immediate inheritance path.

What happens after inheritance is activated?

The vault is marked claimed. Owner controls are no longer the normal path. Remaining token balances can be claimed by the heir individually, and once all balances are zero the vault can be disabled.