EternVault

I shipped another public update for EternVault, focused on making the inheritance workflow clearer and easier to verify across Polygon, Base, and Arbitrum.

The product is still deliberately non-custodial: users keep control of assets and private keys. EternVault focuses on the process layer:

- heartbeat-based trigger

- 14-day confirmation window

- on-chain SignalEmitted state

- beneficiary-only key capsule retrieval

- offline decryption tools for Windows/macOS

The hardest UX problem is not only the testator setup. It is whether a beneficiary can understand what to do under stress, without trusting a hosted recovery screen blindly.

I am looking for feedback on that beneficiary experience: what proof, wording, or walkthrough would make this feel safer for a family member?

Live product: https://www.eternvault.com

I shipped the next version of EternVault with multichain support across Polygon, Base, and Arbitrum.

The core idea is still the same: crypto inheritance should not require giving private keys or asset custody to a platform.

Current flow:

- users keep custody of assets and keys

- heartbeat timeout starts a confirmation window

- after 14 days, the will can move to SignalEmitted

- only then can the beneficiary recover the key package

- recovery can be done offline with Windows/macOS decrypt tools

I am still looking for feedback on the beneficiary side of the flow: what would make this clear enough for a non-technical family member to use under stress?

Live product: https://www.eternvault.com

Crypto inheritance still feels broken. Most options are either manual and fragile, or they require giving custody of keys to a third party.\n\nI built EternVault to make the inheritance workflow verifiable without taking custody of assets or private keys. The live version supports Polygon, Base, and Arbitrum, uses heartbeat-based monitoring, adds a 14-day confirmation window before final signal emission, and only lets beneficiaries recover the key package after the on-chain status reaches SignalEmitted.\n\nI also shipped offline decrypt tools for Windows and macOS so beneficiaries can decrypt locally instead of trusting a hosted flow.\n\nIf you've thought about estate planning for crypto, I'd like feedback on two things:\n1. Which part of the flow feels hardest to trust?\n2. What would make the beneficiary recovery path clearer for non-technical family members?