The curator platform
Permissionless basket publishing: burn $VIM, deploy an index, keep your holders safe by construction.
Vimen's second act: anyone can publish an index. The curator platform wraps
the unchanged, immutable BasketToken core with a thin layer that makes
publishing permissionless while keeping curators unable to rug anyone.
Status
The curator platform is in active development and not yet live. The core mechanic is decided: publishing a basket burns $VIM. The detailed economics are still being finalized. Details of the $VIM token are coming soon; this page will grow as pieces ship.
The model: burn to publish
Publishing a basket through the factory burns $VIM tokens: the publishing fee is destroyed, not paid to anyone. That keeps the platform's incentives simple and clean:
- Publishing costs something real, which keeps spam baskets out without any gatekeeper, allowlist or review committee.
- Nobody collects the fee: no privileged fee-taker, nothing to capture.
- Every basket published permanently reduces $VIM supply.
The exact burn amount and mechanics will be published with the platform contracts.
Why curators can't rug
Every factory-deployed basket is the same immutable BasketToken as the
first-party ones (MAG7, HOOD6,
AI6), wired so that:
guardian= protocol Safe: the cap roadmap applies to curated baskets exactly like first-party ones; curators hold no admin power at all over their baskets.- The constituent set, units and mint fee (≤ 0.50%, enforced in code) are immutable after deploy: a curator can never change the recipe under their holders.
- Redemption is ungated, same as everywhere in Vimen: holders can always unwind, no matter what the curator does or stops doing.
- The factory adds no power over baskets after deployment.
A curated basket's holders never depend on the curator for anything after deploy. The curator picked the recipe; the contract does the rest, forever.