Skip to content
View ReliquaryAI's full-sized avatar

Block or report ReliquaryAI

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
ReliquaryAI/README.md
Reliquary seal

Reliquary

Autonomous onchain treasury succession agent.

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

Status License Build Chain


Overview

Reliquary is a programmable treasury continuity protocol - not a wallet, not a multisig, and not a simple will app. It is built for crypto founders, DAOs, memecoin teams, AI agent projects, and onchain communities that need their treasury to stay protected even if the founder goes silent, disappears, loses access, or becomes inactive.

Founders create treasury instructions, set inactivity triggers, define beneficiaries or successor wallets, assign community vaults, create recovery rules, and seal those rules onchain. When the configured conditions are met, Reliquary executes the instructions automatically, according to code.

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

This repository contains the Reliquary static site - landing page, documentation, legal pages, resource documents, and a create-plan wizard UI. No build step required.


Site pages

Page File Description
Landing index.html Protocol overview, CLI demo, stats, FAQ, agent dashboard
Docs docs.html Technical documentation with sidebar navigation
Create Plan create-plan.html 7-step succession plan wizard (wallet connect via EIP-6963 + WalletConnect)
Whitepaper whitepaper.html Protocol vision, design principles, roadmap
Audit Report audit-report.html Security review scope, findings, disclosure timeline
Terms terms.html Terms of Service
Privacy privacy.html Privacy Policy
Disclaimer disclaimer.html Risk and legal disclaimer

How it works

Step Action Description
01 Create your treasury plan Define the treasury wallet, successor wallets, community vault, beneficiaries, unlock rules, and execution conditions.
02 Set your proof-of-life trigger Choose how often the controller must confirm activity - 7 / 30 / 90 days or a custom window. Confirmation resets the countdown.
03 Seal the plan onchain Succession logic is stored as immutable, publicly verifiable onchain instructions that cannot be changed secretly.
04 Execute when silence is proven If the founder is inactive beyond the threshold, the protocol unlocks the succession flow and executes the sealed plan.

Protocol modes

  • M1 · Founder Recovery - control transfers to a backup wallet or multisig.
  • M2 · Community Vault - funds move to a community-controlled vault.
  • M3 · Contributor Distribution - treasury distributed to predefined contributors/builders.
  • M4 · Agent Continuity - an AI agent or automated wallet continues basic operations.
  • M5 · Final Message - a sealed message is published onchain on trigger.

Project structure

reliquary/
├── index.html              # Landing page (hero, CLI terminal, FAQ, dashboard)
├── docs.html               # Technical documentation
├── create-plan.html        # Succession plan wizard
├── whitepaper.html         # Protocol whitepaper
├── audit-report.html       # Security audit report
├── terms.html              # Terms of Service
├── privacy.html            # Privacy Policy
├── disclaimer.html         # Disclaimer
├── styles/
│   ├── main.css            # Design system + landing page styles
│   ├── docs.css            # Docs layout + prose
│   ├── create-plan.css     # Wizard UI
│   ├── legal.css           # Legal page helpers
│   └── resources.css       # Audit + whitepaper layouts
├── scripts/
│   ├── main.js             # Nav, ticker, particles, FAQ, dashboard, CLI typewriter
│   ├── docs.js             # Docs sidebar scroll + mobile nav
│   └── create-plan.js      # Wallet connect + plan wizard (ES module)
├── assets/
│   ├── seal.svg            # Relic / monogram "R" mark
│   └── favicon.svg         # Compact favicon
├── .github/
│   └── workflows/
│       └── deploy.yml      # GitHub Pages auto-deploy
├── README.md
├── LICENSE
├── SECURITY.md
├── CONTRIBUTING.md
└── .gitignore

No build step. No framework. Runtime dependencies only on Create Plan (WalletConnect SDK loaded from CDN at runtime).


Design system

A solemn, institutional "vault / relic" aesthetic - a high-contrast serif (legacy, the relic) paired with a technical monospace (the code, the execution), over deep charcoal.

Token Value Meaning
--bg #05050a Deep charcoal base
--bone #f0ede6 Primary text
--gold #c8a96a Sealed / legacy / relic accent
--living #7ecb86 Proof-of-life / alive / healthy
--warn #cd924f Grace period
--alert #bd5750 Missed / succession pending

Typefaces: Cormorant (display serif) · Archivo (body) · IBM Plex Mono (data / labels).


Running locally

No dependencies for most pages. Open index.html directly, or serve the root:

# Python
python -m http.server 8080

# Node
npx serve .

Then visit http://localhost:8080.

Note: create-plan.html uses WalletConnect via CDN. Serve over http://localhost (not file://) for wallet features to work.


Deployment

The site is fully static and deploys anywhere (GitHub Pages, Vercel, Netlify, Cloudflare Pages, IPFS).

GitHub Pages is preconfigured via .github/workflows/deploy.yml:

  1. Push to the main branch.
  2. In Settings → Pages, set source to GitHub Actions.
  3. The workflow publishes the repository root on every push.

Community & contact

Channel Link
X / Twitter @ReliquaryAI
Farcaster warpcast.com/ReliquaryAI
Discord discord.gg/reliquaryai
Telegram t.me/ReliquaryAI
GitHub github.com/ReliquaryAI

Contact for support and security reports is via X only - no random email addresses.


Security & disclaimer

Reliquary is never a magic recovery system. It executes only the rules the founder or treasury controller created and sealed.

  • Onchain execution is irreversible.
  • Reliquary does not recover lost private keys.
  • Verify every successor address, allocation, and trigger condition before sealing.
  • The Create Plan wizard currently simulates onchain deployment for demo purposes.

This repository and site are for informational purposes only and are not legal or financial advice. $RELIQ is described strictly in terms of utility - it is not a yield instrument, a claim, or a promise of return. See SECURITY.md, disclaimer.html, terms.html, and privacy.html.


License

MIT © Reliquary Protocol

Popular repositories Loading

  1. ReliquaryAI ReliquaryAI Public

    When founders go silent, the treasury follows the code.

    HTML