Programmable ownership that outlives you.
Set rules now—time, dormancy, attestations, or committee votes—and smart contracts transfer your crypto, NFTs, vault keys, DIDs, or even sanctioned AI agents later. No lawyers, no rumors, no ledger scavengers. Just execution as locked, from inheritance to passive income to unstoppable treasury handoffs.
- Binds recipients, assets, and verifiable conditions (timers, dormancy, attestations, committee votes, oracle facts, staged releases, conflict rules)
- Moves tokens, NFTs, vault keys, personal data, DID-linked wallets, sanctioned agents—as your deployment enumerates them
- Resolves conflicting claims on the same balance deterministically so execution is unambiguous on-chain
- Executes without lawyers, surprise relatives, kitchen-table hostage politics, or renegotiating the deal after predicates fire
That's it. The same backbone handles inheritance, dormant treasuries, timed gifts, corporate continuity, or an exit triggered by silence or a data feed—not because laws changed or cousins appeared, but because you decided.
| Goal | Where to read |
|---|---|
| Browse all technical docs (ADR, architecture, schemas, tests) | Documentation index |
| Understand the problem and design | § Rationale, then Reference specification |
| Contribute or propose changes | CONTRIBUTING.md |
| Report a vulnerability | SECURITY.md |
| See work in progress drafts | drafts/ |
License: MIT.
Crypto doesn't behave like a bank account. Value sits unreachable after a lost seed, a vanished founder, a wallet that stops signing, or an argument about who was "really" supposed to inherit. The same failure happens off-chain: opportunists, slow process, surprise relatives, and narrative wars ignore the quiet deal you thought everyone understood.
ARPA Legacy Protocol treats that as one class of problem: pre-committed, machine-checkable rules for who gets which assets when which conditions fire. Death and disability are major drivers—but not the only ones. The same backbone handles dormancy timers, committee votes, oracle-backed facts, staged releases, and conflict rules when two policies reach for the same balance. You choose scenarios ahead of time: inheritance, yes, but also long-silent treasuries, timed gifts, corporate continuity, or an exit triggered by silence or a data feed.
What stays constant is sovereignty of intent before the storm. You set beneficiaries and predicates while you hold keys. The chain executes when the predicates hold. No lawyers. No surprise cousins. No kitchen-table negotiations. No frozen museums on the ledger. Programmable money finishes the story—because you decided, not because laws changed or someone got loud after you stopped signing.
Today: reference spec (docs/arpa-legacy-protocol-reference.md), structured implementation docs (docs/README.md: Accepted ADR 001, architecture, MVP scope, ideal-vs-MVP asset coverage, events, policy JSON schema, behaviour matrix, vault spec), initial Solidity v1 scaffolding in contracts/, and non-canonical sketches (drafts/).
Coming next: Foundry project wiring, executable tests against the behavior matrix, machine-readable policy manifests, and an SDK for encoding commitments and integration proofs.
Pull requests welcome. See CONTRIBUTING.md for norms.
Documentation and artifacts in arpahls/legacy-protocol default to MIT. Separate packages (when added) declare their own LICENSE at their roots if different.
Use CONTRIBUTING.md for pull requests and community norms. ARPA Legacy Protocol and ARPA Hellenic Logical Systems are steward and project identifiers—do not imply endorsement by the Ethereum Foundation or other third parties without explicit approval.
-
Freeze v1 custody model→ Done: ADR 001 Accepted — vault custody (path A), immutable v1 implementations, hybridexecutemodel. Next: mirror incontracts/(Foundry) and behavior tests. -
Bootstrap
contracts/into executable build/tests — wire Foundry (or Hardhat), then add unit and invariant tests mapped to behaviors indocs/arpa-legacy-protocol-reference.md. -
Authoring tooling — policy manifests, CLI/SDK for commitments and regression fixtures.
-
Testnet deployment and operations — monitoring, (v1: immutable bytecode per deployment; migrations explicit), coordinated disclosure via SECURITY.md.
-
External audit — then sober mainnet-adjacent or high-value use only after reviewers sign off.
Clone:
git clone https://github.com/arpahls/legacy-protocol.git
cd legacy-protocolTrack remote and publish (adapt paths if your checkout lives elsewhere):
git remote -v
git add .
git commit -m "Describe your change"
git push -u origin mainNew repository bootstrap (maintainers initializing an empty origin):
git init
git branch -m main
git remote add origin https://github.com/arpahls/legacy-protocol.git
git add README.md CONTRIBUTING.md SECURITY.md LICENSE assets/ docs/ drafts/
git commit -m "ARPA Legacy Protocol: initial documentation"
git push -u origin mainIf origin already exists: git remote set-url origin https://github.com/arpahls/legacy-protocol.git
This material is not legal advice. ARPA Legacy Protocol enables conditional on-chain transfers of assets and control you scope in code—it does not, by itself, create a valid will, trust, or testamentary instrument in any jurisdiction unless off-chain law and counsel say otherwise.
Healthcare condition, death, or identity attestations implicate regulated data and regulated claims; they require separate compliance regimes and professional review, not assumptions inside Solidity alone.
Consult qualified counsel before relying on any deployment for high-value balances, fiduciary duties, sanctions exposure, tax planning, or other legally binding arrangements.
A conventional will does not move cryptographic keys on its own; it typically does not read oracle-fed facts inside the consensus layer; it does not atomically adjudicate overlapping payout rules the way an explicit conflict policy must; it does not self-execute on chain without someone's ongoing permission—and this stack is aiming at deterministic execution when predicates you authored already hold.
ARPA Legacy Protocol is stewarded by ARPA Hellenic Logical Systems alongside open community contributions.