VimenDocs
The Baskets

The baskets

What a Vimen basket is, and the three live at launch.

A Vimen basket is one immutable BasketToken contract holding fixed raw quantities of its constituent tokens. One basket token (1e18 wei) always corresponds to the same raw amount of each constituent (the units), fixed forever at deploy time.

How a basket is composed

  • Units are computed once, off-chain, at deploy from live Chainlink prices, targeting equal USD weight per constituent and ≈$100 per basket token. (HOOD6's pool-priced constituents use their own Uniswap v4 pools as the price source instead.)
  • After deploy, weights drift with prices, like an unrebalanced ETF. There is no rebalancing in v1; drift is documented product behavior, not a bug. See NAV, drift & pricing.
  • The constituent set, units and the 2–20 constituent bound are immutable. If a basket's recipe were ever wrong, the fix is a new contract, never a mutation of the old one (redeem on the old one keeps working forever).

Live baskets

All three were deployed 2026-07-12 with source verified on Blockscout. The guardian and fee recipient of every basket is the protocol Safe 0xc7aBc67fBB12B69240A4C213c39547C8a345Ec02.

What backs a basket

Two kinds of constituents exist today:

KindExamplesIssuer / originPrice source
Stock TokensAAPL, NVDA, SPCX…Robinhood Assets (Jersey) Ltd, tokenized equitiesChainlink feeds (24/5, US market hours)
Chain-native tokensCASHCAT, VIRTUAL…Permissionless projects on Robinhood ChainTheir own Uniswap v4 pools (24/7)

Stock Tokens are debt instruments of their issuer and carry issuer risk the basket inherits; read Risks. Chain-native tokens carry ordinary crypto-asset volatility and liquidity risk instead.

Deposit caps

Every basket launches with a supply cap of 1,000 tokens (≈$100K) that rises along a public roadmap as the protocol earns trust: traction, then audit, then scale. Caps bound the maximum damage while the code is unaudited; they never affect redemption. Full criteria: Deposit-cap roadmap.

On this page