Deadman Vault is a proof-of-life treasury continuity protocol built on the Stacks blockchain. Lock USDCx in a vault, configure your beneficiaries with percentage allocations and optional vesting cliffs, then check in periodically. If you stop checking in, an automated keeper releases your funds exactly as you specified — no intermediaries, no manual action required.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/natureloved/DeadMan-Vault/llms.txt
Use this file to discover all available pages before exploring further.
Introduction
Learn what Deadman Vault is, how it works, and who it’s built for.
Quickstart
Set up your local environment and create your first vault in minutes.
How It Works
Understand the full lifecycle from vault creation through beneficiary payout.
API Reference
Explore the REST API endpoints for vaults, heartbeats, and the keeper.
Core Concepts
Vault Lifecycle
Six states from funding to claimed, driven by block height and heartbeat deadlines.
Heartbeat System
How periodic check-ins extend your lock and keep the deadman switch inactive.
Beneficiaries
Configure multi-address allocation with percentage splits and vesting cliffs.
The Keeper
The automated cron agent that monitors vaults and settles triggered payouts.
Deploy Your Own
Environment Variables
All required and optional environment variables with descriptions and examples.
Database Setup
Run Supabase migrations and configure row-level security for production.
Keeper Cron
Configure the Vercel Cron Job to sweep vaults and trigger settlements.
Deployment
Deploy the full Next.js application to Vercel with all services wired up.
Deadman Vault currently uses a testnet-only custodial keeper pattern. Per-vault server-held keypairs act on behalf of owners for FlowVault contract calls. This is a deliberate demo shortcut — see the Security Model for the full production-grade architecture.