Mint
Bundles
A bundle mints for many addresses in one transaction, through one of your factories — one fee, one confirmation, every minter.
Making a bundled task
- Set up a factory on the chain and fund it if you'll pay the block builder.
- Create a new task card with Bundle switched on. The card shows a BUNDLE tag.
- In the task form, pick the factory and how many of its minters to use.
Options
| Partial Mints | Stop at the first minter that fails, and keep the mints before it — instead of the whole bundle failing. |
|---|---|
| Pay the Block Builder | A bribe to get the bundle included. Paid from the factory's balance — too little and the bundle reverts. |
| Spam | Sends the bundle more than once. Each one mints for every minter again, and needs the factory funded for all of them. |
Copy Calldata
On a bundle task, Copy Calldata builds the exact transaction the bundle would send to the factory and copies its hex — to send or inspect elsewhere. Nothing is signed or sent. Send it to the factory's address with a value of 0: the factory pays the mints from its own balance.
- A card with several setups asks which one to copy.
{random:…}and{id:…}are drawn fresh on every copy, so copy just before you use it.
What can't be bundled
- Edition (ERC-1155) drops — factory addresses can't receive them.
- Allowlist phases on Transient — the list is tied to your wallets, not the factory's addresses.
- ERC721C (creator-enforced) collections through a proxy factory — see below.
Don't bundle ERC721C (creator-enforced) collections with a proxy factory — your NFTs will get stuck.
Check the collection contract's
getTransferValidator() on the explorer first. If it returns anything other than 0x0000000000000000000000000000000000000000, use a delegate factory instead.Afterwards, Consolidate on the factory gathers what its minters received into one wallet.