Proof-of-life · monitoring onchain

Reliquary

When founders go silent, the treasury still follows the code.

Reliquary is an autonomous onchain treasury succession agent built for projects that cannot depend on a single founder forever. Seal treasury instructions, define successors, set inactivity triggers, and let code preserve continuity when human control disappears.

Create Succession Plan → Read Protocol

No lawyers. No intermediaries. No single point of failure.
Just executable treasury logic onchain.

0+
Treasury Plans Sealed
0%
Uptime Monitoring
0 chains
Networks Supported
Deploy CLI

Seal a plan from the terminal

The same succession flow - connect, configure, sign, deploy. Immutable instructions written before silence.

RELIQUARY CLI - DEPLOYMENT LOG LIVE
root@reliquary:~#
root@reliquary:~#
root@reliquary:~#
root@reliquary:~#
01 The Problem

Founder silence should not
freeze a treasury.

Many onchain projects depend on one wallet, one founder, or one private key. If that person disappears, loses access, becomes inactive, or abandons the project, the community treasury can become permanently frozen or misused. Reliquary turns treasury continuity into programmable onchain instructions.

RISK 01

Single-founder dependency

RISK 02

Abandoned treasury risk

RISK 03

Lost private key scenarios

RISK 04

Funds without recovery rules

RISK 05

No transparent succession

RISK 06

Trust with no execution layer

02 The Solution

A dead man's switch
for project treasuries.

Reliquary lets founders define what should happen if they become inactive. The protocol monitors proof-of-life signals, inactivity windows, and execution conditions. If the founder fails to confirm activity within the selected period, the sealed treasury plan becomes executable.

↧Set inactivity trigger
⊡Name successor wallets
◫Assign community vault
%Define treasury split
⌧Seal final instructions
→Execute automatically onchain
The rules are written before silence. The code acts after it.
03 Mechanism

How Reliquary works

01/ 04

Create your treasury plan

Define the treasury wallet, successor wallets, community vault, beneficiaries, unlock rules, and execution conditions. Every parameter is explicit and reviewable before anything is committed.

→ Configure
02/ 04

Set your proof-of-life trigger

Choose how often the founder or treasury controller must confirm activity - every 7 days, 30 days, 90 days, or a custom period. Confirmation resets the countdown.

→ Interval: 7 / 30 / 90 / custom
03/ 04

Seal the plan onchain

Reliquary stores the succession logic as immutable onchain instructions. The rules are transparent, verifiable, and cannot be changed secretly - the community can read the plan before it ever runs.

→ Immutable · verifiable
04/ 04

Execute when silence is proven

If the founder goes inactive beyond the selected threshold, the protocol unlocks the succession flow and executes the treasury instructions exactly according to the sealed plan.

→ Conditional execution
04 Capabilities

Built for treasury continuity

A

Proof-of-Life Check

Founders periodically confirm they are still active. If no confirmation happens before the deadline, the succession trigger begins.

B

Succession Logic

Define who receives control, how assets are distributed, and which wallet becomes the next treasury authority.

C

Community Vault

Send part or all of the treasury to a community-controlled vault or multisig if the founder becomes inactive.

D

Successor Wallets

Assign trusted successor wallets, DAO-controlled wallets, or project agent wallets as the next line of authority.

E

Immutable Instructions

Once sealed, the plan becomes publicly verifiable and cannot be silently changed behind closed doors.

F

Transparent Execution

Every trigger, condition, and execution event is visible onchain - readable by anyone, at any time.

G

Agent-Based Monitoring

The Reliquary agent watches treasury state, inactivity status, deadlines, and execution readiness continuously.

∎

Continuity, by design.

Seven primitives, one outcome - a treasury that does not depend on a single human staying reachable.

05 Audience

Who is Reliquary for?

Memecoin founders building trust AI agent token projects DAOs needing emergency succession NFT projects with royalty wallets GameFi reward pools Community tokens with one deployer Onchain startups with founder-held funds
06 Example Scenario

If the founder disappears

A founder launches a project with a community treasury and seals a Reliquary plan. From that moment, the outcome is no longer a matter of trust - it is a matter of code.

SEALED_PLAN · 0x7f…a3c1ARMED
IFfounder wallet silent for 30 days → trigger succession
→Community vault60%
→Development wallet20%
→Reward contributors10%
→Locked - future operations10%
∎Publish final onchain message✓

The community is not left waiting, guessing, or trusting rumors.

The treasury follows the code.

07 Protocol Modes

Choose your succession mode

M1 Founder Recovery If the founder is inactive, control transfers to a backup wallet or multisig.
M2 Community Vault If the founder disappears, funds move to a community-controlled vault.
M3 Contributor Distribution Treasury is distributed to predefined contributors, builders, or beneficiaries.
M4 Agent Continuity An AI agent or automated project wallet continues basic operations after inactivity.
M5 Final Message A sealed message is published onchain when the succession condition is triggered.
08 Rationale

Why this must
be onchain

Treasury succession cannot rely on private promises, screenshots, Telegram admins, or offchain documents. Reliquary makes the rules visible before anything happens and executable when the condition is met. The community can verify the plan, monitor the trigger, and see the execution directly onchain.

✓ Publicly verifiable rules
✓ Transparent treasury logic
✓ No hidden admin process
✓ No centralized executor
✓ No lawyer or notary required
✓ Code executes the plan
09 Comparison

Reliquary vs traditional
treasury control

Traditional founder wallet
✕ Depends on one person
✕ No automatic recovery
✕ No public succession rules
✕ Treasury can be frozen
✕ Community must trust promises
Reliquary
✓ Programmable succession
✓ Onchain proof-of-life
✓ Transparent execution rules
✓ Community vault recovery
✓ Treasury follows code
10 Agent Dashboard

Treasury status at a glance

The Reliquary agent surfaces every signal that matters - proof-of-life, deadlines, succession mode, and execution readiness. Toggle the states below to see how the dashboard responds.

reliquary://agent/treasury-0x7f…a3c1
Active
Treasury Status
Active
All systems nominal
Founder Proof-of-Life
Confirmed
Last signal 2h ago
Next Check-in Deadline
27 days
Interval: 30 days
Succession Mode
Community Vault
Mode M2
Successor Wallets
3 assigned
2 multisig · 1 DAO
Execution Status
Locked
Risk status: Healthy
agent monitoring · proof-of-life within window · no action required
11 Token Utility
$RELIQ Utility-focused · not a financial promise

$RELIQ powers access and coordination across the protocol. It is a utility asset for using Reliquary - not a claim, yield instrument, or guarantee of return.

01

Pay protocol fees

02

Seal treasury succession plans

03

Access advanced monitoring

04

Unlock longer custom inactivity windows

05

Create multiple treasury plans

06

Enable agent-based treasury alerts

07

Governance over future protocol modules

∎

Access, not promises.

12 Security

Security first.
Execution only when
conditions are met.

Reliquary is never a magic recovery system. It executes only the rules the founder or treasury controller created and sealed. Users must understand the risks of smart contracts, approvals, wallet security, and irreversible execution.

// READ BEFORE SEALING
Onchain execution is irreversible. Verify every successor address, allocation, and trigger condition. Reliquary does not recover lost keys or reverse a sealed plan that has met its conditions.
Non-custodial design
User-defined rules
Clear execution conditions
Onchain transparency
Optional multisig successor support
No hidden admin override
13 Questions

Frequently asked

Reliquary is an autonomous onchain treasury succession agent that helps projects define what happens to treasury funds if the founder or controller becomes inactive.
No. Reliquary is for inactivity, disappearance, lost access, abandoned projects, or founder silence. It is a continuity protocol - not only a death protocol.
The ideal design is non-custodial or smart-contract controlled. Reliquary executes only based on predefined rules and approvals set by the treasury controller.
Before sealing, yes. After sealing, changes should require clear onchain action, delay periods, or community-visible updates - so nothing happens silently.
The project can include a grace period before execution. During that window, the founder can confirm proof-of-life and stop the succession trigger.
A successor can be a wallet, multisig, DAO vault, contributor wallet, agent wallet, or predefined community treasury.
No. Reliquary is a technical onchain coordination protocol, not a legal service.

Do not let your treasury
die with one wallet.

Create a succession plan before silence becomes a crisis.

Seal Treasury Plan → Read Docs