Silence is the signal
Every value-carrying transfer of an allowlisted token out of your address, on each watched chain, is a visit stamp. The same transfer at $0 is struck through.
SYSTEM.subscribeIf you die with crypto in your own wallet, nobody gets it. Heirloom's reactive contract counts your ordinary transfers of the tokens you list as proof of life. When they stop for the period you set, a grace window opens; any value-carrying transfer of a listed token cancels it. If none comes, two presses anyone can make pay your heir from the vault. No check-in button. No keeper.
TESTNETReactive Lasna · Base Sepolia · Ethereum SepoliaMainnet: not deployed, no mainnet transactions
testnet demo · T = 5 min · 2026-11-08reactive 0xa3d9…9B8b
HEIR STUB pay to 0x440E…438b
claim delay served
finalizeClaim 0x13d8…80d3Base Sepoliaunsubscribed 0x1eb6…a988Lasna
PAIDThe demo run (evidence/triples.csv, demo-actions.csv): 2 graces, 1 cancel, 1 release, 5 of 5 callbacks acknowledged. Recorded 2026-11-08 18:02–18:26 UTC, replayed ×120; times are Lasna blocks (claim row: send time). One pencil mark per minute of silence.
contract tests passing; the whole loop runs in forge test on the Reactive Test Lib
README · Engineering Rigorcallbacks the demo vault acknowledged, 0 resends
evidence/status.jsonrows in the evidence ledger, 22 of them with a callback leg
evidence/triples.csvsubscriptions left on Lasna after the release: the contract removes its own
DEMO.md · rnk_getFiltersEvery transaction on this page is on a public testnet. Mainnet is scripted, not deployed.
Reactive Lasnachain 5318007
TESTNETHeirloomReactive: subscriptions, react(), the Cron clock, callback requests
demo released and torn down 2026-11-08; long-T armed at the last evidence refresh (2026-11-09)
Base Sepoliachain 84532
TESTNETHeirloomVault: callbacks land here; the two-step claim pays out here
claim paid: 0x13d8…80d3
Ethereum Sepoliachain 11155111
TESTNETA watched origin chain: transfers there count as proof of life
heartbeat: 0xbc2c…ac55
Unichain Sepoliachain 1301
PROBE ONLYA subscription probe on build day 1 (2026-11-08); no Heirloom instance watches it yet
probe origin: 0xf99e…1cc7
Reactive mainnet + Basechains 1597 + 8453
NOT DEPLOYEDTwo instances planned: T = 90 days and T = 48 h
scripted, never run; no mainnet transactions
The status page reads the vault and the reactive contract live, and the heir claims from its stub. Below: the demo instance after release, beside a spoof you can fire yourself.

status/, 2026-11-08 20:47 UTC, cropped; the full card has ten rows and the heir stub. Open it live.# dry run, captured 2026-11-08 20:45 UTC $ pnpm exec tsx scripts/trigger-spoof.ts --dry-run instance long-t reactive contract (Lasna): 0x80b56204D8860a6B46c08deCd9F01DD1881F9DC6 owner: 0x12bF8bbD1Eec23B5ab5A44B8d551bbC1d038651C token: Base Sepolia USDC 0x036CbD53842c5426634e7929541eC2318f3dCF7e you: 0x000000000000000000000000000000000000dEaD simulation ok: transferFrom(owner, you, 0) does not revert --dry-run: nothing sent # earlier live run (evidence/fresh-loop-runs.csv) origin Base Sepolia 0x777b953e…4d79 reactive Lasna 0xb622bc82…f226 refusal ZERO_VALUE
evidence/trigger-spoof-dryrun.txt). Bottom: an earlier live run of the same script, from evidence/fresh-loop-runs.csv. Two runs, labelled apart.How it works
There is no server. One reactive contract on Lasna listens to your transfers, keeps time on Reactive's Cron and calls back into a small vault on Base.
LISTENS · SUBSCRIBED LOGS
Your token transfers
Transfer(from = owner)transferFrom(owner, x, 0)Chainlink feed · canary
AnswerUpdatedCron topic, on Reactive
subscribed logs flow into react()
DECIDES · REACTIVE NETWORK
HeirloomReactive.react()
lastSeen on accepted lifeARMEDthenGRACEthenEXPIREDthenDONESystem contract 0x8888…8888
subscribe · unsubscriberequestCallbackV_1_0callback, then sync() on the vault
RELEASES · BASE
Callback proxy
sync(rvm, snapshot)HeirloomVault
Two-step claim
initiateClaimthenfinalizeClaimvault logs flow back to react()
src/ at build time. The panel under react() replays the loop.Open full sizeEvery value-carrying transfer of an allowlisted token out of your address, on each watched chain, is a visit stamp. The same transfer at $0 is struck through.
SYSTEM.subscribeReactive's Cron measures silence, grace and the attest. No server keeps time.
CRONA $0 transfer is refused first in react() and logged. A token you have not listed is never subscribed, so it never counts.
An owner-independent Chainlink feed proves a chain is still heard; on a chain with a canary, a gap freezes the countdown once, capped.
canaryinitiateClaim, then finalizeClaim after the claim delay. Anyone may press; the payout goes to the heir. Then the contract unsubscribes itself.
A clerk strikes a wrong row through instead of rubbing it out. Each attack below is refused the same way, and a test pins every one.
transferFrom(owner, x, 0)Refused and logged; your clock does not movetest_spoof_zero_valuetest_spoof_not_allowlistedtest_spoof_in_grace_does_not_canceltest_refused_react_gas_ceiling · test_spam_braketest_freeze_not_twicetest_sync_direct_call_reverts · test_sync_wrong_rvm_revertsTyped on the back of the card, verbatim from the README's known limits.
An active spam brake holds a grace. Safety over liveness: spam can delay a release, never cause one.README · Known limits, item 1
Approved spenders count as life. … That can only delay a release. Allowlist tokens that have no standing allowances.README · Known limits, item 2
No mainnet evidence yet. Cost per month is not published: the measured window is too short, and a dollar figure needs a second price source.README · Known limits, item 6
Card No. 0xa3d9…9B8b · row 5
At 18:08:42 UTC the owner's ordinary Base Sepolia transfer met an open grace. Three transactions on two networks, each one a click away.
A value-carrying transfer of a token on your allowlist, out of your address, on a chain you watch; or an action you take on the vault itself. A $0 transfer never counts.
You choose the silence period at deploy; the long-running testnet instance uses 90 days. Silence first opens a grace window, and any value-carrying transfer of a listed token, or any action of yours on the vault, cancels it. You can withdraw from the vault at any time before release.
Neither a spoof nor an unlisted token counts as life: $0 transfers are refused and logged, and tokens you have not listed are never subscribed. Only your silence can start a release; a sustained spam spray can delay one, never cause one (Remark 1).
An owner-independent Chainlink ETH/USD feed acts as a canary. If its updates stop arriving, the countdown freezes once, capped, so a short outage cannot trigger a release. The Ethereum feeds measured so far update about hourly (medians 3,612 s and 3,636 s over about 23 h).
Real: every transaction on this page is on a public testnet (Reactive Lasna, Base Sepolia and Ethereum Sepolia, plus one Unichain Sepolia probe), linked to its explorer, and the tests run the whole loop. Not yet: mainnet (scripted, never run; no mainnet transaction exists). The testnet rows come from a build earlier than HEAD; mainnet deploys HEAD.
Not published yet. The long-running instance's measured window is shorter than the 6 hours the meter needs, and a dollar figure needs a second REACT price source. Refused reacts are billed too, which is why the filter runs first and a spam brake bounds it.
The status page holds the claim: initiateClaim, wait out the claim delay, then finalizeClaim. Anyone may press both steps (in the demo, the owner key did); the payout goes to the heir, or to an address the heir redirects it to.