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
Deployment safety stop.
The current compiled contracts still bind to ROCK and one fee pool. Their transaction buttons are blocked until the genuinely token-independent shared contracts replace them; signing this build would create the wrong architecture.
0 / 6Waiting for generic deployment build
Start with the LONG token checker. The next module unlocks only after the previous receipt is confirmed.
System settings and required service addresses
Most settings are already filled in. Open only the small section you need; the four automation wallets and reviewed market routes are the remaining inputs.
AFTER THE SIX RECEIPTS
Connect the automation.
Your wallet deploys contracts; it cannot create managed signers or publish a private worker. Download the verified addresses, place them in the automation runtime, then complete the live checks before opening Launch.
- Intake authorityCreates one restricted fee wallet for each VEND.
- ExecutorClaims, sweeps, converts and pays using only allowed calls.
- Two checkersIndependently rebuild every hourly holder result.
- Runtime and proof storeRuns the loop, retries failures and publishes receipts.