Owner
You keep control while active.
Your vault remains yours while the configured inactivity window has not matured. You can check in, update settings, deposit, or withdraw.
Protocol logic
No inbox. No judge. Just state.
The contract does not ask why someone disappeared and it does not rely on a centralized operator. It only enforces the rules the owner configured.
Clock
Time is the trigger.
Vestige does not guess intent. It reads the latest check-in timestamp, inactivity period, and grace period directly from the contract.
Heir
The heir gets a narrow path.
When the silence window fully passes, the configured heir can activate inheritance and claim the assets the protocol tracks.
Lifecycle
Four states people can understand.
The dApp turns contract timing into a readable flow: create, fund, check in, release.
Flow
The practical path.
These are the actions users actually take inside the dApp. The deeper docs can cover ABI details, but this page keeps the mental model simple.
01 / Create
Create a vault and name the heir.
The owner chooses one heir wallet and two timing windows: inactivity and grace. These values become the rulebook for the vault lifecycle.
02 / Fund
Add native USDC or token balances.
On Arc, native USDC can be deposited directly into the vault. ERC20-compatible token balances can also be tracked and claimed individually.
03 / Check in
Refresh the owner signal over time.
A check-in updates the vault timestamp. This is the simple recurring action that keeps the inheritance path locked.
04 / Release
Let the heir claim only after silence matures.
If inactivity plus grace has passed, the heir can activate inheritance. Owner actions freeze and the claim path opens deterministically.