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
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 ↗THE LAUNCHER
Review every route before you launch.
YOUR MACHINES
PUBLIC PROCESSING LOG
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
Usage grows before the bill does.
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.
ADMIN
Connect the VEND admin wallet to manage production launch gates and backend test runs.
Production launch gate is ready to inspect.
LIVE PROD ONLY
This tab only shows production readiness: backend custody, launch authority, and the public creation gate. Your browser wallet is used only for explicit admin or creator transactions.
PRODUCTION LAUNCH GATE
Privy is backend custody only. Your browser wallet stays the creator/admin wallet. Retries reuse one launch intent, while each new VEND receives its own intake wallet.
Reading backend readiness...
TEST · BACKEND DRY RUN
Use the self-contained ROCK-GLD backend path: D1 is the control plane, R2 holds full staged wallet snapshots, and the Worker validates LONG plus provisions test intake wallets.
Run manually by default. Select any available hourly snapshot by date and hour, fetch holders, materialize R2 into D1 if needed, enter incoming assets, compute distribution, then validate before any routing step.
REFERENCE ONLY
These records explain what was deployed before today’s backend path. Use them only when you need to inspect or recover old setup evidence.
HISTORICAL · OPERATOR SETUP
These controls belong to the older shared-operator rollout. The live ROCK-GLD backend now reports readiness from the Worker and the Launch page stays gated until those checks pass.
Reference mode. Use backend readiness for the current production gate.
The replacement stack is complete.
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
The wallet can deploy reviewed code. It cannot decide which price source is trustworthy, prove a pool stays liquid, or show that full hourly processing succeeded. Those facts must be visible before live launch opens.