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.
Why this project matters
This is a reference architecture for a Reactive-native wallet direction.
It also reacts to real Uniswap Sepolia swap events.
The wallet keeps acting after the UI disconnects.
youtu.be/dqHAGzGRY4E
Origin -> Reactive -> Destination
3 live end-to-end flows
Current wallets are still session-bound.
That model breaks when the product should keep responding to external onchain events, not just to the user being online at the right moment.
If Reactive Network enables event-driven execution, the wallet should evolve too.
Origin event in. Autonomous wallet execution out.
Saves transfer intent or swap intent into a personal autonomous wallet.
Raw signal, permissionless poke(), or a real Uniswap swap.
Reactive contract validates the route and builds the callback payload.
Checks callback path, runtime state, duplicate protection, and execution limits.
The frontend and scripts show source proof, Reactive dispatch, and destination outcome.
Three verified end-to-end paths are already live.
Raw Signal Path
The minimum loop: emitSignal -> listener -> callback -> execution
Mirrored Intent + Permissionless poke()
The user stores intent once. A keeper only needs to call poke(wallet, nonce).
Real Protocol Event -> Wallet-Funded Action
A real Uniswap Sepolia Swap triggers a wallet-funded faucet request.
The best demo is not self-authored. It comes from the outside protocol world.
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.
Live Uniswap v3 Sepolia fee tiers under one multi-source listener.
Real upstream protocol activity becomes the source event.
Wallet-funded request executed from the autonomous wallet itself.
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
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
Transfer or swap response plan lives inside the wallet.
Listener, source path, callback path, and execution status remain inspectable.
Source, callback, and destination outcomes are visible in the frontend and scripts.
WillLead is bigger than one demo wallet.
Reactive-native wallet architecture
A concrete reference implementation for developers exploring the same direction.
Origin -> Reactive -> Destination
A product-shaped example that explains the execution model with real contracts and proof.
From infra to product form
Shows how Reactive Network can drive user-facing behavior, not only backend automation.
Consumer intent execution
The wallet is only the first entry point. Persistent intent is the larger application pattern.
The next stage is not more demo features. It is architecture hardening.
Multi-intent wallet
Move beyond a single active flow into richer wallet-native execution composition.
More live protocol templates
Expand beyond one swap path into additional upstream event patterns.
Operator / keeper hardening
Stabilize the shared runtime service and failure-recovery posture.
Cross-chain intent direction
Extend from same-chain response into Reactive-native cross-chain execution flows.
WillLead asks a simple question.
youtu.be/dqHAGzGRY4E