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 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.
ONE ORDERED SETUP
Deploy the shared system from top to bottom.
These eight contracts are genuinely token-independent. They start paused with empty feed and route books, so setup cannot accept creator funds. Each button prepares one contract-creation transaction; the next step unlocks only after its receipt and code are verified.
0 / 8Next: Admin safety controls
Start with Admin safety controls. No token or pool is part of this deployment sequence.
System settings and required service addresses
Chain bindings, recovery approvers and safety limits are prefilled. The only intentional blanks are the four separate automation wallets that must actually be provisioned.
AFTER THE EIGHT RECEIPTS
Connect automation and add supported markets.
Your wallet can deploy and wire the shared contracts. It cannot create custody identities, publish a private worker or decide that a live market route is safe. Those remain explicit release steps.
- Connect the Worker and proof storeUse the downloaded registry, factory and service addresses.
- Add safety feedsRegister ROCK, wrapped native and each supported fee asset.
- Add reviewed routesApprove each fee asset → ROCK and fee asset → wrapped-native path.
- Rehearse two tokensOpen public creation only after both complete the full hourly and recovery story.