NFTs, Web3, and On-Chain Inheritance: Planning for the Blockchain Assets You Can't Call Customer Service About

The Inheritance Problem That Didn't Exist Five Years Ago

If you own Bitcoin or Ethereum, you've probably heard the statistic: billions of dollars in cryptocurrency are permanently lost because holders died without sharing their seed phrases. That problem is real, and we've covered it before.

But there's a newer, messier version of the same problem that almost nobody is planning for: the rest of your on-chain life.

NFTs you bought during the 2021 boom and still hold. Ethereum Name Service (ENS) domains tied to your identity. DeFi positions earning yield on Aave or Compound. Staked ETH or staked Solana. Liquidity positions on Uniswap. ENS profiles, Lens protocol handles, Farcaster accounts, Base names, Arbitrum airdrops — the whole scattered footprint of participating in Web3 over the last few years.

None of this is inheritable by default. None of it has customer service. And most of it lives in places your family wouldn't know to look.

This post covers what actually lives on-chain, what dies with your wallet, and how to build an inheritance plan that accounts for Web3 assets properly.

What "On-Chain" Actually Means for Inheritance

The core property of blockchain assets — the thing that makes them censorship-resistant, permissionless, and verifiably scarce — is also what makes them impossible to inherit through normal channels.

Traditional financial assets have a custodian. You don't technically "hold" the shares in your brokerage account; you have a claim against the brokerage that holds them. When you die, the brokerage can transfer those claims to your heirs through a well-established legal process.

On-chain assets are different. You don't have a claim against a custodian. You have the private keys that control the addresses those assets live at. The assets are the keys. No key, no asset. That's not a workflow problem — it's a mathematical fact.

This means that for every on-chain asset you hold:

There is no "forgot password" flow
There is no legal process that can force a blockchain to give someone else access
There is no court order that can compel the network to release the asset
There is no customer service that can help your heirs
Your heirs can't prove ownership any way other than presenting the keys

When your Coinbase account passes to your spouse through the normal inheritance process, that's Coinbase — not the blockchain. Anything that actually lives on-chain requires planning, not probate.

The Web3 Inventory: What You Might Actually Own

Let's take stock of the common categories. You might own any or all of these:

Fungible Tokens

Native tokens: BTC, ETH, SOL, AVAX, MATIC, etc.
Stablecoins: USDC, USDT, DAI (across multiple chains)
Governance tokens: UNI, AAVE, COMP, MKR, LDO
Meme coins and speculative holdings

NFTs

Art and PFPs: BAYC, Azuki, Doodles, Art Blocks, individual 1/1 pieces
Music and media NFTs: Sound.xyz drops, catalog releases
Gaming NFTs: Axie Infinity, Gods Unchained, Parallel, Pixels
Membership NFTs: DAO access, community passes, Proof collective
Utility NFTs: tied to subscriptions, benefits, or ongoing access

DeFi Positions

Lending deposits: Aave, Compound, Spark (often aTokens, cTokens)
Liquidity provider positions: Uniswap, Curve, Balancer LP tokens
Yield farm deposits: Pendle, GMX, Jito, Marinade
Staked assets: stETH, rETH, mSOL, jitoSOL
Leveraged positions: Gearbox, dYdX, GMX

Identity and Access

ENS names (.eth) — tied to wallet, often worth $100–$50,000+
Base names (.base.eth)
Farcaster accounts and associated Frames/casts
Lens Protocol profiles
Bankr handles, mirror.xyz publications, Paragraph accounts
DAO voting power and associated delegations

Less Obvious Assets

Airdrop eligibility for future tokens based on your on-chain history
Soulbound tokens (SBTs) and other non-transferable credentials
Validator nodes (staked ETH validators, Solana validators, etc.)
Domain names in various blockchain naming systems

A single wallet might hold all of these. A user with multiple wallets (hardware, hot, multisig, cold storage) spreads them further.

What Actually Transfers vs. What Dies With You

Here's the honest breakdown of inheritance behavior for each category.

Transferable to Heirs (If You Plan Ahead)

Fungible tokens (BTC, ETH, SOL, stablecoins)
Most NFTs
ENS names and other token-based naming systems
Most DeFi positions (after unwinding)
Staked positions (after unstaking)

For all of these, the prerequisite is access to the private keys or seed phrase. Given that, transfer is a simple on-chain transaction from the original wallet to the heir's wallet.

Non-Transferable (Soulbound or Wallet-Tied)

Soulbound tokens
Reputation-based systems (Gitcoin Passport, on-chain credentials)
Some validator slots with identity binding
Future airdrop eligibility based on on-chain history

These can't be moved. They expire with the wallet.

Ambiguous / Platform-Dependent

Farcaster and Lens profiles (some components transfer, identity generally doesn't)
DAO memberships tied to specific wallet addresses
Gaming positions in Web3 games (some items are NFTs that transfer, some game-state is tied to the wallet)

Conditional

Staked assets during lockup periods may not be immediately transferable
Liquidity positions may need to be unwound before transfer
Leveraged positions need to be closed before the underlying collateral can be moved

The key planning insight: inheritance often requires unwinding. An heir who suddenly gains control of a complex DeFi position might not know how to close it. That's not just a technical problem — it's a financial one. Positions that aren't managed get liquidated.

The Five-Layer Web3 Inheritance Plan

Here's a comprehensive approach that handles the main failure modes.

Layer 1: Wallet and Seed Phrase Documentation

Everything on-chain starts here.

Document:

Every wallet you own (hardware, software, mobile)
The seed phrase for each
Any additional passphrase (the 25th word for BIP-39 wallets)
Hardware wallet PINs
Which wallets hold which assets (approximately)
Software wallet locations (Rabby, MetaMask, Phantom, Coinbase Wallet, etc.)

Store in a zero-knowledge encrypted vault. This is non-negotiable — seed phrases written on paper in a safe fail in too many scenarios (fire, flood, theft, misplacement).

Layer 2: Asset Inventory

List what each wallet contains, at a high level. Not transaction-by-transaction, but enough for an heir to understand what they have.

Example structure:

Wallet	Chain	Holdings	Approximate Value	Notes
Ledger #1	Ethereum	ETH, USDC, 3 BAYC NFTs	$40K	Main cold storage
Rabby Hot	Multi-chain	Trading tokens, small balances	$2K	Day-to-day wallet
Ledger #2	Solana	SOL, mSOL, Jupiter LFG NFT	$8K	Solana-specific
Hardware backup	Bitcoin	BTC	$50K	Long-term hold

This inventory serves two purposes. It tells your heir what they're receiving, and it forces you to actually know what you own.

Layer 3: The Unwinding Guide

For complex positions, your heir needs instructions, not just access. Write a step-by-step unwinding guide for any position that's more complex than "send tokens to new wallet."

Examples:

"The aUSDC in the Ethereum Ledger is a deposit in Aave. To withdraw: connect to app.aave.com, click Withdraw on the USDC row. It will convert back to plain USDC, which can then be transferred to your wallet."
"The stETH in the hot wallet is staked ETH via Lido. You can either keep it as stETH (it continues earning yield), trade it back to ETH on Curve or Uniswap, or unstake directly via Lido's withdrawal queue (7-day wait)."
"The NFT titled 'Terraforms #1234' is the artwork for ENS name xxxx.eth. If you transfer the NFT, the ENS name goes with it. If you just want to release the name, use app.ens.domains."

Don't assume your heir is technical. Assume they're intelligent but have never used DeFi. Write instructions for that person.

Layer 4: Identity and Handle Planning

For on-chain identity (ENS, Farcaster, Lens, etc.), document:

What the handle is
Where it's held (which wallet)
Whether you want it preserved, transferred, or released
Any connections to off-chain identity (website, socials, creative work)

ENS names in particular can be valuable. A short, memorable .eth domain can sell for five or six figures. Your heir should at least know what the asset is worth before deciding what to do with it.

Layer 5: The Check-In Ritual

Web3 is particularly well-suited for a deadman switch approach because the inheritance mechanism is already digital and doesn't require probate.

Using Killswitch (or any deadman switch), you can:

Store wallet documentation, seed phrases, and unwinding guides encrypted
Configure delivery to trigger when you stop checking in
Assign different asset groups to different heirs (e.g., technical nephew gets NFTs and DeFi, spouse gets fungible tokens)
Include video explanations for complex topics

The advantage over traditional methods: the delivery matches the asset class. On-chain assets don't wait for probate, so neither should the instructions for accessing them.

The Multisig Alternative

Some advanced crypto users set up multisig wallets specifically for inheritance. A 2-of-3 multisig might have:

One key held by you
One key held by your spouse
One key held by your attorney or a trusted third party

Any two keys can move funds. This provides both:

During life: You need your spouse's cooperation (or the attorney's) for large transactions — good for accountability
After death: The remaining two keys can still access funds — good for inheritance

Multisig is powerful but operationally complex. It works best for significant holdings where:

The cost of setup is justified by the amount at stake
All keyholders are technically competent
You're comfortable with the coordination overhead

For most people, a well-designed deadman switch is simpler and equally effective. For high-net-worth holders, multisig plus a deadman switch layer of documentation provides the strongest protection.

The "DeFi Position Monitor" Problem

Here's a subtle issue that deserves specific attention.

DeFi positions can be liquidated. If you have collateralized debt on Aave or Compound, and the collateral value drops enough, the position gets liquidated automatically. The protocol doesn't care that you died — it cares that the collateralization ratio dropped below the threshold.

If you have leveraged positions, they're even more time-sensitive. A GMX perp position can be liquidated in minutes during a volatile market.

Your heir needs to know these positions exist immediately so they can either close them or monitor them. An inheritance plan that takes 30 days to deliver the wallet information may leave them inheriting less than expected — or nothing at all.

Two implications:

Shorter check-in intervals for volatile DeFi exposure. If you hold meaningful leveraged positions, configure your deadman switch to trigger in days, not weeks.
Prefer simpler positions when planning for legacy. Assets you plan to leave behind should ideally be ones that don't require active management. An ETH balance sits happily forever. A leveraged LP position does not.

NFT-Specific Considerations

NFTs deserve a few specific notes because they behave differently from fungible tokens.

Value Is Market-Dependent

Fungible tokens have clear prices. NFT prices are floor-dependent, collection-dependent, and can crash faster than tokens can. An NFT worth $50,000 at peak might be worth $500 at inheritance time. Your heirs should know the approximate floor of the collection, not a peak-price appraisal.

Some Provide Ongoing Utility

Membership NFTs unlock things — Discord access, events, merchandise, voting rights, airdrops. Your heir inheriting a BAYC gets more than an image; they get access to ongoing community features. Document what the utility is, not just that you own the NFT.

Royalties and Creator Earnings

If you created NFTs rather than just collected them, you may have ongoing royalty streams from secondary sales. These are contract-level programmable payments tied to the NFT's metadata. Your heir needs to know:

Which NFTs you minted that have royalty provisions
Where royalties are paid (which wallet)
Any creator identity associated with the work

Storage and Metadata Risk

NFT images and metadata often live off-chain (on IPFS, Arweave, or centralized servers). If the storage provider disappears, the image attached to your NFT may vanish even though the token still exists on-chain. This isn't an inheritance planning issue per se, but it's worth noting: not all NFTs you own today will have their metadata intact decades from now.

Tax Considerations (Briefly)

Inherited crypto and NFTs are generally subject to the same step-up basis rules as other assets — the cost basis resets to the fair market value at the date of death. This is generally favorable for heirs.

But:

Determining fair market value for illiquid NFTs is nontrivial
Crypto inherited through normal probate has a paper trail; crypto delivered via deadman switch may need more careful documentation
Tax treatment varies significantly by jurisdiction

This is a place where your heirs should consult a crypto-aware accountant, not a general practitioner. Document who that person is, if you have one, and include their contact in your inheritance plan.

The Technical-vs-Non-Technical Heir Mismatch

Most Web3 users are technically sophisticated. Most of their heirs are not.

This is the single biggest cause of inheritance failure in the crypto space. Someone dies holding $200,000 in ETH and NFTs. Their spouse knows it exists. Their spouse has the seed phrase. But the spouse has never used MetaMask, doesn't understand gas fees, doesn't know what Etherscan is, and is terrified of making a mistake that wipes out the holdings.

The solution isn't to teach your spouse blockchain before something happens. It's to designate a "technical executor" — someone competent in crypto who can help your non-technical beneficiary manage the inheritance.

Structure:

Your non-technical heir (e.g., spouse) receives the documents, instructions, and assets
A technical executor (a family member, friend, or crypto-savvy professional) is named as a resource
Documentation includes the technical executor's contact information and a description of the help they're authorized to provide

This is similar to naming an executor for your estate: one person bears the legal authority, others assist with execution.

A Final Thought on Volatility

On-chain assets can 10× or 100× — or drop 90% — in weeks.

An inheritance plan that assumes 2024's prices will be the same in 2035 is unrealistic. Build flexibility into the plan:

Include approximate values, but acknowledge they'll change
Provide guidance on decisions (e.g., "if ETH is above $X, consider selling some; if below, probably hold") if your heirs want direction
Revisit the plan annually or when significant changes happen

And consider: the asset landscape your heirs inherit may not be recognizable in a decade. New chains, new protocols, new categories of assets, new risks. Your documentation should be specific enough to be actionable today and general enough to be useful tomorrow.

Bottom Line

Web3 is more than crypto. It's a growing ecosystem of assets, identities, and positions that live entirely on-chain and have no customer service, no account recovery, and no default inheritance path.

Passing it on to your family requires the same kind of planning crypto has always required — documented seed phrases, clear instructions, thoughtful beneficiary selection — plus an acknowledgment that the complexity is growing faster than most plans are keeping up.

A zero-knowledge encrypted deadman switch is the right tool for this job. It matches the privacy and permissionless nature of the assets themselves while providing a reliable delivery mechanism that doesn't require courts, custodians, or probate.

The best time to set this up was when you bought your first NFT. The second-best time is today.

Killswitch stores seed phrases, wallet documentation, NFT inventories, and DeFi unwinding instructions with zero-knowledge encryption. When you stop checking in, everything delivers automatically to the people you designate — with the privacy and sovereignty your Web3 assets deserve. Get started today