SeaDrop

An overview of the SeaDrop protocol and how it is used for NFT Primary Drops.

Overview

SeaDrop is a smart contract protocol for primary NFT drops on EVM-compatible blockchains.

Versions

  • v1 (main) powers ERC-721 drops. The deployment instructions below use v1.
  • v2 powers ERC-1155 self-minting for editions (open collections). It also supports existing staged drops and receives security fixes.
  • v3 is in development. It upgrades v1's drop architecture, with an opt-in path for existing v1 collections, ERC-20 mint payments, delegate-wallet and linked-wallet support, signed mint intents, clone factories, existing-contract adapters and agent NFT extensions. Self-service ERC-1155 edition drops are planned for a later rollout.

v3 is unaudited development code and requires Security review and an external audit before deployment. The v3 tracker covers the remaining contract, backend and Studio work.

v1 contracts

v1 supports public drops, Merkle allowlists, server-signed mints and token-gated drops. OpenSea Studio uses public and server-signed allowlist stages. A compatible token exposes SeaDrop's minting and configuration functions, with configuration restricted to its owner or another authorized administrator.

ERC721SeaDrop is the v1 token contract. It provides:

  • Extending ERC721A to make minting multiple tokens in a single transaction gas-efficient
  • Support for a public sale and multiple pre sales using Merkle Tree -based allowlists and server-signed mints
  • All the functionality needed to integrate with OpenSea's Drops program.

Many creators find that they require some special functionality on their smart contracts for their drops. The SeaDrop repository has extensions for a random offset reveal, locks that pause trading or make tokens soulbound, and AI agent tokens. If you require functionality not available in our pre-made contracts, extend ERC721SeaDrop as Customize a SeaDrop contract describes. So that users can mint your drop on OpenSea, please do not modify any minting functionality.

Links

Deploying a SeaDrop-compatible contract

To deploy a v1 SeaDrop-compatible contract, start with ERC721SeaDrop. Clone the repository and install Foundry with the instructions in the ReadMe. To deploy the contract, run

forge create --rpc-url $RPC_URL --private-key $PRIV_KEY --broadcast src/ERC721SeaDrop.sol:ERC721SeaDrop \
  --constructor-args "ExampleToken" "ExTkn" "[0x00005EA00Ac477B1030CE78506496e8C2dE24bf5]"

If you don't need to make any customizations, deploy ERC721SeaDrop as-is with the constructor argument of allowedSeaDrop of 0x00005EA00Ac477B1030CE78506496e8C2dE24bf5. This will allow the SeaDrop contract permission to mint on your token contract. If you've already deployed your contract without setting the allowedSeaDrop in the constructor, you can call updateAllowedSeaDrop, available on the token contract interface.

If you have or would like to deploy an upgradeable contract, see Upgradeable Contracts in the SeaDrop repository. For technical questions related to the SeaDrop minting experience and capabilities, see the SeaDrop repository and the Drops FAQ.