3 baskets,and every unit in them.
A basket is one token holding a fixed recipe of real tokenized US stocks. These are the ones the protocol curates itself at launch, so nobody has to be the first person to deploy one. Nothing here is a model portfolio or a suggestion: each NAV is the recipe valued at the same Chainlink prices the protocol would mint it at, right now.
The launch lineup
Basket NAVs: loading…
Every recipe is bounded by what its components' onchain float can absorb, and that arithmetic is published alongside it rather than asserted.
Not every stock token can go in a basket.
34 of 96
Need a price feed
A component has to have a Chainlink feed on chain 4663: the registry requires one and the NAV oracle fails closed without it. That rules out 62 of the stock tokens outright, however much you might want them.
10
Have real depth behind them
Of the feed-backed tokens, this many have both enough onchain float and enough traded volume to sit at a meaningful weight today. The rest are not forbidden, just unproven, and we would rather say so than quietly include them.
15%
Cap what one name can be
No component is weighted past the point where the basket would need to own more than 15% of everything that exists of it onchain. At our $250k target that is a real constraint, and it is the reason some obvious recipes are not here.
The full list of what exists is on the stock token dashboard, and the mechanics of recipes, minting and NAV are in the docs.
Nothing here is your thesis.Publish yours.
A recipe is an argument. The protocol gives it a price, a token anyone can hold, and60% of every fee it earns.