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
EARLY PILOT MVP
Route fees to the admin EOA.
Admin wallet only.
Connect the admin wallet to check or start the early pilot.
This pre-pilot does not deploy a VEND, create service wallets, split holder rewards, run burns or start automation. It only keeps the current fee route on an EOA and sends 100% of the creator-controlled fee share back to the admin wallet.
One-wallet fee route.
Use the cards below in order. If the admin EOA already owns the current fee share, there is no setup transaction to send.
- Admin EOA
- Pending wallet
- Network
- Robinhood · 4663
- Fee manager
- Loading…
- Fee pool
- Loading…
- Core token
- Loading…
- Admin fee share
Start by checking whether the admin EOA is already the fee receiver.
YOUR MACHINES
Your fees, in motion.
No deployed v1 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.
PUBLIC FACTORY / SYSTEM WORKBENCH
Follow one VEND from start to finish.
Review mode
The architecture is public to inspect. Connect the admin wallet only when you are ready to record decisions and evidence.
This page is the V2 execution blueprint—not a deployable V2 release.
The repository has a closed, token-bound V1 pilot. The reusable V2 contracts, database-backed runtime, public creator flow and production proofs still need to be built and rehearsed. Public creation stays locked until every release gate below has verifiable evidence.
START HERE · ONE COMPLETE VEND STORY
How VEND works
Follow Alex from an existing LONG fee stream to a safe, repeatable holder-reward machine. Open any step for the why, the handoff and what breaks without it.
HumanWalletOn-chainAutomated
KNOWN LAUNCH BLOCKERS
These are the gaps—not footnotes.
CONTRACT BOUNDARY
Deploy once vs. create per VEND.
Worker-owned after activation.
Event indexing, fee collection, historical snapshots, checker requests, payouts, burn operations, reconciliation, retries and public reports should run from one shared runtime across every registered VEND.
Four actions stay explicit.
The protocol council approves policy. An accountable reviewer opens public creation. Each creator signs createVend. Each creator separately redirects the LONG fee share. Those are intentional control points, not workflow defects.
Missing proof disables the feature.
No verified token or pool means no creation. No fresh price means no USD threshold. No executable route means no conversion. No checker quorum means no payout commitment. The UI explains the missing dependency instead of improvising.
V2 workbench loaded in review mode.
PLATFORM ADMIN / PRIVATE PILOT
Set up the VEND protocol.
Admin access only.
Connect the admin wallet to manage infrastructure deployment.
This page prepares the private V1 pilot. V1 still includes admin-wallet, pilot-token, fixed-pool, feed and route bindings. The reusable public release should be V2: deploy shared contracts and backend once, then let creators launch each VEND from token and pool inputs. Each V1 contract deployment asks for one wallet confirmation.
Known values are prefilled. Remaining infrastructure appears in the setup checklist above.
Five contracts. One reviewed sequence.
Do not send other transactions from this wallet during deployment. The gas bank pins the predicted factory address. A changed nonce stops the sequence.
Before the first VEND goes live.
Deploying contracts does not start the backend. Apply the exported addresses to the runtime configuration, finish managed-signer enrollment, verify executable market routes and burn support, configure both snapshot checkers, then publish the Cloudflare-backed runtime. The launcher stays gated until those checks pass.
Intake wallets are provisioned through the managed signer. The factory deploys each VEND vault when you launch; neither is a separate infrastructure deployment here.