burneh
Crypto

A mint that holds up when 10,000 people hit it at once.

We build the drop end to end: a gas-tight contract, a merkle allowlist, phased minting, metadata pinned so it can't vanish, and a reveal nobody can game.

Start a build
10,000 supplyERC-721Aallowlist live

Mint one and watch it land on the wall. The counter, the progress, and the feed are the drop filling up, the way it looks on mint day.

Acme Genesis
ERC-721A · 10,000
minting
4,212of 10,000 minted
0.04 ETH each · max 3
1
total0.04 ETH
minting live42.1%
#4470
#4469
#4468
#4467
#4466
#4465
#4464
#4463
#4462
#4461
#4460
#4459
0x3a…c7 minted #44704,212 / 10,000

Eligibility is a proof, not a list we check.

Your address is a leaf in a tree, and one root lives on-chain. Pick an address and watch the proof climb to the root, the same check the contract runs. An address that isn't in the tree fails.

R
on-chain
·
·
·
you
·
·
verify an address
proof verified · eligible to mint

Rarity falls out of the numbers.

Every token is a set of traits, and rarity is computed from the real distribution, not assigned by hand. Flip through a few and watch how rare each trait actually is.

Acme #421
rank #118 · top 1%
VoidBackground · 12% have it
ChromeBody · 6% have it
LaserEyes · 3% have it
GrinMouth · 18% have it

The rarer the trait, the shorter the bar. It's pinned with the art on IPFS, so the numbers can't be quietly changed after the drop.

A reveal nobody can game.

The shuffle is committed to a hash before the first mint. Until reveal, even we can't see which token is which, so nobody snipes the rares. Hit reveal and watch the art resolve.

1
Commithash of the shuffled order, on-chain before any mint
2
Mintyou get a token id, the art stays sealed
3
Revealmetadata goes live and matches the committed hash
provenance 0x8a3f…d21c · committed before mint
sealed
#612
sealed
#613
sealed
#614
sealed
#615
sealed
#616
sealed
#617

Gas-tight, for when everyone arrives at once.

ERC-721A mints a range in one write, so minting ten barely costs more than one. That's the difference between a site that stays up on mint day and one that doesn't.

AcmeGenesis.sol
1// SPDX-License-Identifier: MIT
2pragma solidity ^0.8.24;
3
4import { ERC721A } from "erc721a/contracts/ERC721A.sol";
5import { MerkleProof } from "@openzeppelin/contracts/utils/cryptography/MerkleProof.sol";
6
7contract AcmeGenesis is ERC721A {
8 bytes32 public immutable allowRoot;
9 uint256 public constant MAX_SUPPLY = 10_000;
10 uint256 public constant MAX_PER = 3;
11
12 function mintAllowlist(uint256 qty, bytes32[] calldata proof) external payable {
13 bytes32 leaf = keccak256(abi.encodePacked(msg.sender));
14 require(MerkleProof.verify(proof, allowRoot, leaf), "not on allowlist");
15 require(_numberMinted(msg.sender) + qty <= MAX_PER, "over limit");
16 require(totalSupply() + qty <= MAX_SUPPLY, "sold out");
17 _mint(msg.sender, qty); // ERC-721A: batched, ten costs barely more than one
18 }
19}
minting 10 in one tx
ERC-721A (batched)~1.2× one mint
Naive ERC-721~9.7× one mint

Same ten tokens, a fraction of the gas. On a hot mint, that keeps fees sane and the mempool from choking.

A mint that holds up when 10,000 people hit it at once.

A gas-tight contract, a merkle allowlist, phased minting, metadata pinned so it can't vanish, and a reveal nobody can game.