Reactive Omni Buildathon · Set It and Forget It

When your wallet goes quiet, silence pays your heir.

If 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

TESTNETBox 0x5136…dDBA · vault on Base Sepolia · watched from Reactive Lasna

Access card

18:26:59 UTC

testnet demo · T = 5 min · 2026-11-08reactive 0xa3d9…9B8b

  1. Deposit into the vaultBase Sepolia · 0x17d6…f478VISIT
  2. Token transferEthereum Sepolia · 0xbc2c…ac55VISIT
  3. $0 USDC transferBase Sepolia · 0xaac4…52e9REFUSED
  4. Silence past T: grace openscallback 0xde28…9488DORMANT
  5. Owner transfer cancels the graceBase Sepolia · 0x2082…ef00VISIT
  6. Silence again: grace openscallback 0x484b…fe2fDORMANT
  7. Grace ran out: claimablecallback 0xabb5…0401EXPIRED
  8. Claim initiated (anyone may press)Base Sepolia · 0xf866…de8dCLAIM
  9. Attest callbackcallback 0x54d9…3614ATTEST
Silence10:32 grace ran out
T = 5 min
RELEASED

HEIR STUB pay to 0x440E…438b

claim delay served

finalizeClaim 0x13d8…80d3Base Sepoliaunsubscribed 0x1eb6…a988Lasna

The 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.

168

contract tests passing; the whole loop runs in forge test on the Reactive Test Lib

README · Engineering Rigor
5 of 5

callbacks the demo vault acknowledged, 0 resends

evidence/status.json
43

rows in the evidence ledger, 22 of them with a callback leg

evidence/triples.csv
0

subscriptions left on Lasna after the release: the contract removes its own

DEMO.md · rnk_getFilters

Where it runs today.

Every transaction on this page is on a public testnet. Mainnet is scripted, not deployed.

Reactive Lasnachain 5318007

TESTNET

HeirloomReactive: 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

TESTNET

HeirloomVault: callbacks land here; the two-step claim pays out here

claim paid: 0x13d8…80d3

Ethereum Sepoliachain 11155111

TESTNET

A watched origin chain: transfers there count as proof of life

heartbeat: 0xbc2c…ac55

Unichain Sepoliachain 1301

PROBE ONLY

A 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 DEPLOYED

Two instances planned: T = 90 days and T = 48 h

scripted, never run; no mainnet transactions

The same card, on the status page.

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/ · demo instanceOpen it live
The Heirloom status card for the demo instance: RELEASED stamp, live facts, and the first access-card rows with origin, reactive and callback hashes
Capture of status/, 2026-11-08 20:47 UTC, cropped; the full card has ten rows and the heir stub. Open it live.
terminal · trigger-spoof.ts
# 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
Top: a dry run, captured verbatim 2026-11-08 20:45 UTC (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

Silence starts the clock.

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)
  • value > 0 counts as life
  • transferFrom(owner, x, 0)
  • Base, Ethereum Sepolia

Chainlink feed · canary

  • AnswerUpdated
  • owner-independent proof
  • that a chain is still heard

Cron topic, on Reactive

  • the only clock: silence,
  • grace and the attest

DECIDES · REACTIVE NETWORK

HeirloomReactive.react()

  • 1Filter first: allowlist, owner, value > 0
  • 2Stamp lastSeen on accepted life
  • 3ARMEDthenGRACEthenEXPIREDthenDONE
  • 4Silence timed on Cron; canary caps a freeze
  • 5Callback held until Ack, resent on a tick
  • 6Spam brake bounds refused reacts

System contract 0x8888…8888

  • subscribe · unsubscribe
  • requestCallbackV_1_0

RELEASES · BASE

Callback proxy

  • sync(rvm, snapshot)
  • rvm = the reactive contract

HeirloomVault

  • ARMEDthenGRACEthenCLAIMABLE
  • thenCLAIM_PENDINGthenRELEASED
  • owner may withdraw any time
  • owner actions count as life
  • emits OwnerActive · Ack ·
  • StateChanged · EstateReleased

Two-step claim

  • initiateClaimthenfinalizeClaim
  • anyone may press; pays the heir
Every name is checked against src/ at build time. The panel under react() replays the loop.Open full size

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.subscribe
Token transferEthereum Sepolia · 0xbc2c…ac55VISIT
$0 USDC transferBase Sepolia · 0xaac4…52e9REFUSED
Silence past T: grace openscallback 0xde28…9488DORMANT
Owner transfer cancels the graceBase Sepolia · 0x2082…ef00VISIT

The clock is a Cron topic

Reactive's Cron measures silence, grace and the attest. No server keeps time.

CRON

Spoofs are struck through

A $0 transfer is refused first in react() and logged. A token you have not listed is never subscribed, so it never counts.

SpoofRefused

A deaf network buys one extension

An owner-independent Chainlink feed proves a chain is still heard; on a chain with a canary, a gap freezes the countdown once, capped.

canary

Two presses pay the heir

initiateClaim, then finalizeClaim after the claim delay. Anyone may press; the payout goes to the heir. Then the contract unsubscribes itself.

requestCallbackV_1_0

Voided, not erased.

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.

A stranger's transferFrom(owner, x, 0)Refused and logged; your clock does not movetest_spoof_zero_value
A worthless token sent from your addressIgnored: only allowlisted tokens counttest_spoof_not_allowlisted
A spoof during an open graceOne spoof never cancels it; a sustained spray trips the brake, which can delay a release, never cause onetest_spoof_in_grace_does_not_cancel
Spam to drain the contract's reserveRefused under a fixed gas ceiling; a spam brake bounds ittest_refused_react_gas_ceiling · test_spam_brake
A chain the network stops hearingFreezes the countdown once, capped; cannot be chainedtest_freeze_not_twice
Anyone but the callback proxy calling the vaultReverts: both the caller and the relayed contract are checkedtest_sync_direct_call_reverts · test_sync_wrong_rvm_reverts

Remarks.

Typed on the back of the card, verbatim from the README's known limits.

Remark 1
An active spam brake holds a grace. Safety over liveness: spam can delay a release, never cause one.README · Known limits, item 1
Remark 2
Approved spenders count as life. … That can only delay a release. Allowlist tokens that have no standing allowances.README · Known limits, item 2
Remark 3
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

One cancel, end to end.

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.

ORIGIN

Base Sepolia

0x2082f0bc…e05def00

The owner moves an allowlisted token, as on any day.

REACTIVE

Lasna

0x99bb1f22…ed2899fe

react() sees life during grace and requests the cancel.

CALLBACK

Base Sepolia

0x217b43e3…62f390ce

The vault goes from grace back to armed.

Every origin, reactive and callback hash: DEMO.md

Questions a judge would ask.

What counts as being alive?

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.

What if I just go travelling for a month?

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.

Can a stranger fake my life, or cause my 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).

What if the Reactive Network stops hearing a chain?

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).

What is real, and what is not yet?

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.

What does it cost to keep running?

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.

Heirloom mark: the card in its vault drawer; the stamps stop, RELEASED lands and the heir stub tears free

Your heir needs one link, not your key.

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.