> **Can't find what you're looking for?** Use `search_docs` on the docs MCP server at `https://docs-sepolia.modularium.art/api/mcp` to find what you need.

# Mint requirements (recipes)

A public mint can ask collectors to do more than pay. With requirements, an edition can only be minted by someone who burns, freezes or holds tokens from other collections. Modularium calls this combination of steps a **recipe**.

Add requirements under **Open a Public Mint** when you [create an ERC-1155 token](/create/selling#public-mint-erc-1155). Click **+ ADD REQUIREMENT** once per step.

## Requirement fields

| Field | Options |
| --- | --- |
| Collectors must | **Burn**: the tokens are destroyed. **Freeze**: the tokens stay in the collector's wallet but can't be transferred or burned until the freeze ends. **Hold**: the collector only has to own them. |
| Frozen for (days) | Freeze only. Defaults to 30. |
| Collection | Search for any indexed collection by name, slug or address. |
| Tokens | **Any token in this collection**, or **Specific tokens** picked from the collection. |
| Amount | How many tokens the step needs. For ERC-1155 inputs this counts editions. |

The **Mint Price** is added as a final pay step. Each mint requires all steps, and each mint produces one edition.

### Example

> Burn 2 tokens from *Seeds* and hold any token from *Gardeners*. Pay 0.01.

That's two requirements, Burn × 2 from Seeds and Hold × 1 from Gardeners, plus a Mint Price of `0.01`.

## For collectors

Collectors mint from the token page. They pick which of their tokens to use for each step. If the drop contract needs approval to burn or freeze those tokens, the approval goes into the same transaction as the mint when every contract involved supports batching. Otherwise each approval is signed separately before the mint.

Frozen tokens appear in the collector's **\[FROZEN]** profile tab. Once the freeze has ended, they can **thaw** them there to make them transferable again.

## Rules for self-serve recipes

Anyone can create a recipe drop, with these limits:

* **Your tokens only.** Every token the recipe mints has to be in a collection you own.
* **Burn, freeze, hold and pay only.** Steps that transfer tokens, check a merkle allowlist, or call external contracts, and drop hooks, are reserved for drops curated by Modularium. They run with the drop contract's permissions, which other collections may rely on.

:::info
Modularium collections support burning, so their tokens are destroyed outright. If an input collection can't burn, the drop sends the token to the dead address (`0x…dEaD`) instead, which takes it out of circulation just the same. Outside collections aren't guaranteed to allow that transfer. If one blocks it, the mint fails, so try a test mint before launching a drop that burns tokens from an outside collection.
:::
