Funding and issuance

A community basket is created and funded in one transaction. The factory deploys the vault, verifies receipt of its constituent tokens, and initializes share accounting. If any required step fails, the whole transaction reverts.

Fund a new basket with ETH

The native factory accepts one ETH amount and uses the declared weights to allocate it across the constituents. It wraps ETH into the configured wrapped-native token, then acquires the other constituents through its configured V3 venue.

Earlier allocations round down in raw ETH units; the final constituent receives the remainder. A wrapped-native constituent keeps its allocation as wrapped ETH without a swap. Each other route can contain at most two pools and must match the configured factory, token endpoints, and pool identities.

The transaction includes a minimum received amount for each constituent and an expiry. Each minimum must satisfy the vault’s 1,000-raw-unit seed floor. Exact transfer checks verify that the router spent and delivered the reported quantities.

The resulting token quantities become the initial active reserves. Launch weights describe input spending allocations, rather than oracle-verified percentages of the resulting portfolio’s value.

Fund with constituent tokens

The in-kind createAndSeed operation remains available through the contract interface. The caller provides an amount for every constituent and approves the factory to transfer those tokens. The caller is both the recorded creator and the payer; a separate receiver can receive the net shares.

The factory checks both the payer’s balance decrease and the vault’s balance increase. Observable transfer taxes cause the transaction to revert.

Mint shares after launch

A later deposit uses the current active reserves and supply to calculate the exact inputs for a chosen gross share amount. It does not reuse the launch’s ETH-spending weights.

previewMint returns:

• The required amount of every constituent, rounded up.
• The issuance-fee shares.
• The net shares delivered to the receiver.

For a direct mint, approve the vault for constituent transfers. The transaction specifies maximum amounts for each token, minimum net shares, a receiver, and a deadline. The vault enforces these limits and verifies token coverage before issuing shares.

The native trading router can acquire those same proportional inputs with ETH and complete the mint in one transaction. The accounting rules explain the formula and minimum deposit sizes.

Gross and net issuance

The initial deposit always funds one gross share. Later deposits fund the requested gross amount. The issuance fee is taken from those newly created shares: net shares go to the receiver and fee shares go to the immutable fee recipient.

No extra, unfunded shares are added for the fee. See creator fees for examples and the distinction from the planned fee model.

When issuance is unavailable

Issuance fails if a constituent is underfunded, cannot complete the required transfer, or has an insufficient deposit amount. ETH funding additionally requires executable constituent routes and the submitted limits to hold.

When the final outstanding share is redeemed, the basket closes permanently. Existing withdrawal claims remain payable, but the vault cannot accept a new seed or mint more shares.