A PROTOCOL FOR HOLDERS
Make ’em
VEND.
Holders give tokens value, liquidity,
distribution and staying power.
VEND asks the obvious question:
where do the fees go?
The replacement stack is complete.
THE NEXT CHAPTER
Public release
coming soon.
VEND is starting with a private pilot. Explore the machines and follow the rollout.
The launcher is available only to the admin wallet for now.
Explore machines ↗Loading pilot configuration…
THE LAUNCHER
Give your fees a purpose.
Review every route before you launch.
- 1 Token
- 2 Holders
- 3 Routes
- 4 Launch
YOUR MACHINES
Your fees, in motion.
No deployed machine loaded.
PUBLIC PROCESSING LOG
Every hour, accounted for.
Same cutoff. Verifiable commitments. Public retries.
Snapshot and accounting checks each get an initial attempt and three automatic retries. Anyone can retry after those attempts fail. Payout commitments cannot be replaced.
| Hour (UTC) | Machine / check | Status | Attempts | Action |
|---|---|---|---|---|
| No processing records yet. | ||||
USAGE & BUDGET
Small pilot. Visible costs.
Usage grows before the bill does.
Loading application usage…
Application counters include reserved and uncertain requests. They are estimates, not provider invoices. Gas is separate. The pilot uses an existing host and shared storage; its two checker processes share a host failure risk.
PLATFORM ADMIN
Set up VEND once.
Admin wallet required.
Connect the VEND admin wallet to review and deploy the shared system.
THE FOUNDATION IS BUILT
Now make the system safe to use.
The shared contracts and their four corrected connections are live. Public creation remains paused. The next six cards tell the rest of the story in order: teach VEND how to swap, protect those swaps with prices, connect the hourly robot, prove the full loop twice, then open the door.
0 / 8Checking the foundation
Start with Admin safety controls. No token or pool is part of this deployment sequence.
NEXT · MAKE IT OPERATE
Teach it, protect it, prove it, then open it.
Only the first card is a safe deployment today. Later buttons unlock only when their required evidence exists; “not ready” means the system is protecting you from guessing.
Ready to deploy one token-independent venue executor. No token or pool is included.
Completed foundation upgradeFour corrected contracts · expand to inspect0 / 4
Completed original foundationEight generic contracts · expand to inspect8 / 8
System settings and required service addresses
Chain bindings, local-rehearsal service addresses, recovery approvers and safety limits are prefilled. Only public addresses reach this page; signing keys remain in the local Keychain and must be replaced with independently operated identities before public launch.
WHY SOME BUTTONS ARE LOCKED
A click should finish a known job—not hide a guess.
The wallet can deploy reviewed code. It cannot decide which price source is trustworthy, prove a pool stays liquid, or show that two full hourly rehearsals succeeded. Those facts unlock the later buttons.
- Prices before routesThe swap needs a fresh independent “do not accept less than this” value.
- Routes before automationThe robot must not invent a path while money is moving.
- Automation before rehearsalThe full loop must run without a human doing hourly chores.
- Rehearsal before openingTwo different tokens must prove both the happy path and recovery path.