Bundle stock tokens
Bundling means depositing the complete component recipe into its vault and receiving basket tokens. It turns several separately held stock tokens into one receipt with a defined normal redemption path.
Creating a recipe defines what one receipt represents. Minting receipts funds that recipe. A basket definition alone is not deposited backing, and creating a community token is a separate action.
1. Choose or reuse a recipe
Select 2–10 unique approved stock tokens and positive weights that total 100%, or inspect an existing basket. One selected stock uses the direct-stock model instead of a basket.
For a new standard recipe, Lots converts weights into quantities using an initial $1 reference target. Open the details to inspect those quantities and the reference timestamp. You can use advanced exact-quantity input if you want to specify the units directly.
When reusing a basket, check its exact vault identity, current quantities, value and backing. Reuse does not reset its current value or quantities. Names and old percentage weights are not sufficient identifiers.
2. Preview what you must deposit
For the fictional X/Y/Z recipe, minting 100 whole basket tokens requires:
| Token | Per basket token | Deposit for 100 |
|---|---|---|
| X | 0.005 | 0.5 X |
| Y | 0.006 | 0.6 Y |
| Z | 0.010 | 1.0 Z |
The preview must list every component. Having enough X and Y does not let you mint a partial basket without Z. Complete missing holdings first using available supported acquisition routes.
For fractional amounts, deposits round up at component atomic-unit precision. The accounting reference explains the rule. Review actual wallet amounts rather than calculating from rounded display percentages.
3. Approve and sign
Check the vault, component allowances and intended basket amount. Separate approvals may be needed. When the mint executes, the vault must verify that all required tokens actually arrived before issuing the receipt. An expected transfer, price-feed entry or router accounting credit is not backing.
If a required transfer or coverage check fails, the mint must revert. The interface should retain your inputs and explain the affected component. Any previously completed approval remains a separate onchain action.
4. Inspect the result
Your wallet receives the minted basket tokens. The vault holds their components. Verify the receipt, actual amounts and backing view. You can retain the basket, use it in a supported meme purchase, or redeem it later when healthy.
If you mint 100 receipts, do not count both the 100 basket tokens and their backing as separately owned portfolio positions. They represent the same exposure.
Buying a meme with ETH
For an ETH-funded basket-paired meme purchase, the complete route acquires every component, deposits them, mints the basket and swaps it for the meme. In that route, the minted receipt is intermediate inventory; the final wallet output is the meme you selected.
This requires executable markets for every component. It is more demanding than minting from tokens you already hold. An unavailable ETH route is not proof that healthy in-kind bundling is unavailable.
Costs and availability
Lots charges no basket mint protocol fee and pays no royalty to the recipe creator. You may still pay approval gas, mint gas and any component acquisition costs.
A healthy in-kind mint should not depend on a USD price feed, indexer or the main website. Verified interfaces and a minimal contract client are required release deliverables, but are not supplied or verified by this initial docs version. A stale reference can stop creation of a new price-dependent recipe without stopping a healthy existing one.
If the vault is impaired, issuance may be restricted. Follow the actual state and recovery guidance, rather than treating every failed route as the same kind of incident.