Open Demo Video
Reactive-native Wallet MVP
WL

Hackathon Pitch Deck

WillLead

Define once. Execute when the right event arrives.

WillLead is a wallet prototype designed around Reactive Network itself. The wallet stores intent, keeps runtime state, receives callbacks, and executes even after the frontend goes offline.

Persistent onchain intent
Event-driven execution
Live protocol proof

Why this project matters

A new wallet model
Not just automation
This is a reference architecture for a Reactive-native wallet direction.
Not only demo events
It also reacts to real Uniswap Sepolia swap events.
Not frontend-bound
The wallet keeps acting after the UI disconnects.
Demo Video

youtu.be/dqHAGzGRY4E

Execution Model

Origin -> Reactive -> Destination

Verified Paths

3 live end-to-end flows

WILLLEAD / 01
The Problem

Current wallets are still session-bound.

"The user clicks once, the wallet acts once."

That model breaks when the product should keep responding to external onchain events, not just to the user being online at the right moment.

Temporary intent Intent usually exists only inside the UI or in one signature flow, then disappears.
Passive wallet model The wallet holds keys and balances, but it does not hold an ongoing execution posture.
Automation lives outside the wallet Bots poll events, decide what to do, and execute on behalf of the user from the outside.
WILLLEAD / 02
The Thesis

If Reactive Network enables event-driven execution, the wallet should evolve too.

A wallet should hold intent, runtime state, and execution logic.
Persistent intent User intent becomes first-class wallet state, not temporary frontend input.
Event-driven execution A valid source-side event can trigger wallet behavior without re-opening the UI.
Wallet-native proof Source event, Reactive callback, and destination execution are all visible onchain.
WILLLEAD / 03
Architecture

Origin event in. Autonomous wallet execution out.

1. Controller
User signs once

Saves transfer intent or swap intent into a personal autonomous wallet.

2. Origin
Source event happens

Raw signal, permissionless poke(), or a real Uniswap swap.

3. Reactive
Listener reacts

Reactive contract validates the route and builds the callback payload.

4. Destination
Wallet validates

Checks callback path, runtime state, duplicate protection, and execution limits.

5. Proof
Execution is surfaced

The frontend and scripts show source proof, Reactive dispatch, and destination outcome.

WILLLEAD / 04
Proof Of Execution

Three verified end-to-end paths are already live.

Path 1

Raw Signal Path

The minimum loop: emitSignal -> listener -> callback -> execution

Origin: 0xae45...a7d3
Destination: 0x8de1...7584
Path 2

Mirrored Intent + Permissionless poke()

The user stores intent once. A keeper only needs to call poke(wallet, nonce).

Intent: 0xd2c1...d1e1
Poke: 0x6eb2...d5a9
Dispatch: 0x615e...0e5f
Execution: 0x5e01...7abe
Path 3

Real Protocol Event -> Wallet-Funded Action

A real Uniswap Sepolia Swap triggers a wallet-funded faucet request.

Source swap: 0xec40...302a
Destination faucet: 0xa38a...6ff9
WILLLEAD / 05
Strongest Evidence

The best demo is not self-authored. It comes from the outside protocol world.

Live upstream trigger

WillLead listens across live Uniswap Sepolia v3 WETH / USDC pools. When a real swap happens, the Reactive listener routes a callback directly into the autonomous wallet.

Not a fake demo event The source trigger is a real protocol event emitted by live external contracts.
Not a bot-controlled wallet action The autonomous wallet uses its own execution balance to perform the action.
Not only infrastructure narrative This ties Reactive Network capability directly to a credible user-facing product shape.
Watched Source
4

Live Uniswap v3 Sepolia fee tiers under one multi-source listener.

Trigger Event
Swap

Real upstream protocol activity becomes the source event.

Destination Action
Faucet

Wallet-funded request executed from the autonomous wallet itself.

WILLLEAD / 06
Why Reactive Network Is Essential

Without Reactive Network, this collapses back into offchain bot automation.

Offchain bot model

  • Poll origin events from outside the wallet
  • Trust external infra to decide when to relay
  • Execution logic lives in service glue, not wallet state
  • Automation belongs to the bot operator, not the wallet model

WillLead on Reactive Network

  • Reactive contracts listen to the origin-side event path directly
  • Callbacks are routed into the autonomous wallet
  • Saved onchain intent is the execution source of truth
  • Automation becomes wallet-native capability
Reactive Network is not decoration here. It is the condition that makes the wallet model possible.
WILLLEAD / 07
What Users Actually Get

One setup flow. Ongoing wallet behavior.

The user does this once

  • Connect a controller wallet
  • Create or discover the autonomous wallet
  • Save a transfer intent or swap intent
  • Fund execution when needed

The wallet keeps doing this later

  • Wait for valid source-side events
  • Receive Reactive callbacks
  • Validate route and runtime state
  • Execute the saved action without reopening the frontend
Intent
Stored onchain

Transfer or swap response plan lives inside the wallet.

Runtime
Bound to route

Listener, source path, callback path, and execution status remain inspectable.

Proof
Readable afterwards

Source, callback, and destination outcomes are visible in the frontend and scripts.

WILLLEAD / 08
Why This Matters To The Ecosystem

WillLead is bigger than one demo wallet.

Reference

Reactive-native wallet architecture

A concrete reference implementation for developers exploring the same direction.

Teaching Case

Origin -> Reactive -> Destination

A product-shaped example that explains the execution model with real contracts and proof.

Platform Story

From infra to product form

Shows how Reactive Network can drive user-facing behavior, not only backend automation.

Future Layer

Consumer intent execution

The wallet is only the first entry point. Persistent intent is the larger application pattern.

The submission is not trying to prove "wallets can call Reactive Network." It is trying to prove "Reactive Network can support a new wallet paradigm."
WILLLEAD / 09
Next Milestones

The next stage is not more demo features. It is architecture hardening.

1

Multi-intent wallet

Move beyond a single active flow into richer wallet-native execution composition.

2

More live protocol templates

Expand beyond one swap path into additional upstream event patterns.

3

Operator / keeper hardening

Stabilize the shared runtime service and failure-recovery posture.

4

Cross-chain intent direction

Extend from same-chain response into Reactive-native cross-chain execution flows.

WILLLEAD / 10
Close

WillLead asks a simple question.

If the user defines intent once, why should the wallet stop acting when the frontend disappears?
What WillLead proves now
Intent can become wallet state
Reactive callbacks can keep the wallet acting
Real protocol events can directly trigger user-side behavior
Watch the live demo

youtu.be/dqHAGzGRY4E

Demo video: youtu.be/dqHAGzGRY4E
WILLLEAD / 11