Mint flow

Contract pathCopy Anchor Link

AMM accepts native ETH as msg.value. enter(minTokensToMint) is the standard path for users authorized to enter. During the invite period, a new invited user submits enterWithInvite(minTokensToMint, inviteId, deadline, signature).

See the deposit and mint sequence diagram for the normal deposit path.

SequenceCopy Anchor Link

1. The app verifies chain, input, and invite state and asks the wallet to sign.
2. AMM checks pauses, whitelist authorization, and the minimum output.
3. On a bootstrapped deployment, AMM prices the deposit from net NAV and live supply, excluding the just-arrived deposit from the pre-entry pricing basis.
4. EVE is minted to the user and the deposited ETH is forwarded to Controller.

The historical first-deposit bootstrap path has separate initial-supply and USD minimum rules. It is not the normal minimum for a later user's mint.

Pricing dependenciesCopy Anchor Link

Entry price is NAV / (liveSupply × connectorWeight). The contract enforces the submitted minTokensToMint; frontend estimates alone are not protection.

NAV can depend on token feeds and strategy pool TWAPs. Normal minting is therefore not oracle-independent, even though ETH/USD conversion is not directly required for every entry.

Indexed dataCopy Anchor Link

Bootstrap mints and later mints have distinct event types and update indexed deposit/mint totals. A submitted transaction is not a confirmed mint until the receipt is known.