Skip to content
C

ChainLegacy

No lawyers. No gas fees. Just peace of mind.

Created on 5th June 2025

•

C

ChainLegacy

No lawyers. No gas fees. Just peace of mind.

The problem ChainLegacy solves

In today’s digital world, owning crypto assets is easy — but passing them on when you're gone? That’s a trust and timing nightmare. Traditional inheritance doesn’t work well with decentralized assets, and even existing crypto solutions are either manual, insecure, or overly reliant on third parties.

ChainLegacy solves this problem.

It's a smart inheritance protocol that:

🕒 Automates asset distribution when the original owner is no longer active, using Chainlink Automation to verify inactivity.

🔒 Eliminates reliance on lawyers or custodians — your plan is enforced by code, not by trust.

⚖️ Ensures funds are transferred fairly and transparently to the right people, at the right time.

⚠️ Warns users if their inheritance plan has unallocated funds or missing details.

In short, it lets people set up inheritance plans where digital assets are automatically airdropped to loved ones if the owner doesn't confirm they're still alive — a "dead man's switch" for crypto, made secure and user-friendly.

Challenges I ran into

-No way to update individual inheritors (gas inefficiency):
One of the earliest hurdles was managing changes to inheritance plans. My contract wasn’t designed to edit a single inheritor — instead, it would clear the entire list and rebuild it from scratch every time a change was needed. That worked… but it definitely wasn’t gas-friendly, and it felt clunky for users too.

I considered alternative data structures (like mapping + array hybrids), but decided to keep it simple for the hackathon MVP. The experience taught me how crucial updatable, gas-efficient state management is for real-world smart contracts — especially inheritance plans where changes are inevitable.

-Testing Chainlink Automation locally:
I was frustrated by how slow testing became once Chainlink Automation got involved. Having to deploy to Sepolia, fund subscriptions, and wait for real check-ins really slowed down iteration. I wondered: “Can I run Chainlink Automation locally on Anvil or simulate it somehow?”

Turns out — not really in a plug-and-play way. I had to get creative:

Built custom mock automation functions for local testing.

Emulated checkUpkeep and performUpkeep logic manually in dev scripts.

Used Anvil’s forking from Sepolia to at least test against real contract state.

This hackathon made me realize that testing time-based automation in Web3 is still a rough UX, and that dev tooling around Chainlink Automation could use more local-first support.

Tracks Applied (1)

Onchain Finance

ChainLegacy tackles a critical — yet often overlooked — pillar of onchain finance: inheritance and wealth continuity. W...Read More

Discussion

Builders also viewed

See more projects on Devfolio