Network
Built for Arc-native USDC.
Vestige’s current frontend is configured around Arc Testnet and native USDC settlement.
Quick context
The questions people ask first.
Inheritance protocols can feel heavy. These cards set the frame before the detailed questions.
Custody
No centralized inheritance desk.
The owner and heir interact directly with the contract. Vestige does not custody private keys or decide claims.
Timing
Days, not mystery states.
Inactivity and grace windows are configured by the owner and shown in the dApp as human-readable timing.
What is Vestige?+
Vestige is a self-custodial inheritance vault. The owner creates a vault, names an heir, deposits native USDC or tokens, and periodically checks in. If the owner signal stops for the configured inactivity plus grace window, the heir can claim.
Does Vestige hold my wallet or private keys?+
No. Vestige is a contract interface and protocol flow. You connect a wallet, sign transactions yourself, and remain responsible for wallet security.
Why does the heir need the owner address?+
Without an indexer, the claim flow is owner-address driven. The heir looks up the vault by owner address, then the contract verifies whether that connected wallet is the configured heir.
Can the owner withdraw funds?+
Yes, while the vault is still active and not claimable. Once the timing window matures, owner-side actions freeze and the heir claim path opens.
What assets are supported?+
The frontend focuses on Arc-native USDC and ERC20-compatible tracked token balances. Token claims are granular so each token can be claimed independently.
Can one wallet create multiple vaults?+
A wallet can have one active vault at a time. After an empty or completed vault is disabled, the owner can create a new one.
Is this production-ready legal estate planning?+
Vestige is a technical inheritance primitive, not a substitute for legal advice. Real-world estate planning should still be handled with qualified legal guidance.