Publishing a basket
Burn $WOOD, design in the studio, deploy your own index through the factory. Live now.
Anyone can deploy a basket through the public factories: no allowlist, no review queue, no admin approval. The whole flow runs in the app's basket studio at app.rwoodstocks.xyz — the same machinery that published the live pilots.
Choose the kind, then design it
A basket is either frozen (the recipe never changes) or agentic (an agent rotates it inside a hard policy and pays holders in USDG — see what an agent can and cannot do).
Either way, pick 2–20 constituent tokens and their weights. The studio handles the unit math the same way first-party baskets are built: target equal (or custom) USD weights at ≈$100 per basket token, converted to raw units from live prices. For an agentic basket you also set the agent key and the policy — cooldown, turnover, slippage, payout interval — inside the contract ceilings (1 day, 25%, 1%, 1–90 days). Constraints enforced on-chain: no duplicate tokens, every unit > 0, mint fee ≤ 0.50%. An agentic basket can only hold assets covered by the on-chain AssetRegistry.
Burn $WOOD for your license (once, forever)
A license is a one-time burn of $WOOD —
destroyed, not paid to anyone. Two tiers, both hard constants in the
CuratorRegistry:
- V1 — frozen baskets: 10,000 $WOOD.
- V2 — agentic baskets: 25,000 $WOOD (includes the frozen tier; a legacy 25,000 burn is grandfathered into it).
You approve the registry and burn in a single call; from then on you can publish as many baskets of that tier as you want. The burn permanently reduces $WOOD supply.
Deploy — and your basket is out of your hands
The factory deploys a standard immutable basket token (plus, for agentic baskets, its USDG payout distributor in the same transaction), wired so you can never rug your holders — and no one can rug you: the guardian is the restricted CuratorGuardian (it can only raise the supply cap along the public cap roadmap, starting at the 1,000-token starter cap — it can't redirect your fees or pause your basket). A frozen basket's recipe is immutable forever; an agentic basket's recipe rotates, but only inside the policy locked at deploy, and its backing stays full after every trade. Redemption is ungated, like every Robinwood Stocks basket: your holders never depend on you again.
What you earn
Every time someone mints your basket, its mint fee is split by the
immutable FeeSplitter: 60% goes straight to your wallet, 40% to the
protocol treasury. No staking, no pool, no lockup — the split is a
hardcoded constant, and because your basket's guardian is the restricted
CuratorGuardian, that 60% can never be
redirected or switched off, by anyone.
What you control, and what you don't
| You control | You don't control |
|---|---|
| Constituents & units (at deploy; immutable after, on a frozen basket) | A frozen basket after deploy: the recipe is frozen |
| Name, symbol, mint fee (≤ 0.50%) | Cap increases: only the protocol Safe can raise them, along the roadmap |
| The agent key & policy, for an agentic basket | The policy ceilings: cooldown, turnover, slippage are immutable limits |
Rotating the agent key later (setAgent, curator-only) | Holder funds: no path exists, same as first-party baskets |
Curate responsibly
A basket's constituents can't be changed after deploy (an agentic basket's agent can rotate them, but only inside the registry's covered universe). Vet token addresses against official sources (fakes with identical tickers exist), mind pool liquidity if you want the zap to work for your holders, and remember: if any constituent can be frozen by an issuer, your basket inherits that risk. See Risks.