Optional: Drop from a contract you already deployed
Use a SeaDrop adapter to run an OpenSea drop for an ERC-721 contract deployed without SeaDrop support.
OpenSea drops mint through SeaDrop, which calls a mintSeaDrop function on the token contract. If your ERC-721 contract is already deployed and doesn't have SeaDrop's functions, you can still drop new tokens from it by deploying a SeaDrop adapter next to it.
SeaDrop treats the adapter as the drop's contract. You configure stages, prices and payouts on the adapter, and each mint delivers a token of your existing contract to the collector. The tokens are ordinary tokens of your collection, so they keep your contract's metadata and royalties.
Check what your contract supports
These adapters use SeaDrop v1. The adapter you need depends on how your contract mints.
| Your contract | Adapter | How a mint works |
|---|---|---|
| Lets the owner grant another address the right to mint, through a minter role or allowed-minter list | ERC721SeaDropMintAdapter | The adapter calls your mint function for each sale |
| You hold transferable tokens, or can mint them and allow the adapter to transfer them to collectors | ERC721SeaDropTransferAdapter | You deposit tokens into the adapter, and it sells them in order |
For the mint adapter, your contract's mint function must take (address to, uint256 quantity) and mint all quantity new tokens to the supplied to address, like mint(address,uint256) or mintTo(address,uint256). It must let the adapter mint without paying the target: the adapter forwards no ETH, even for a paid SeaDrop stage. If the target requires payment, use the transfer adapter with tokens you already own instead. A function that takes a token ID instead of a quantity won't work. The adapter checks how many tokens each call minted, so a multi-token purchase reverts, but a single-token purchase can't tell the difference. Confirm the function takes a quantity, for example in your contract's verified source, before you deploy. A developer can support other mint functions by extending ERC721SeaDropAdapter.
The adapter counts mints by totalSupply() when your contract has it, or by the recipient's balance otherwise. A supply increase alone does not prove that the buyer received the tokens. Check the target's verified source and test that its mint function delivers the full quantity to to. On a contract without totalSupply(), a recipient that forwards or burns tokens during its receive callback can make the count check fail. The whole purchase then reverts, including the payment. Test the intended recipient wallet before launching.
If your contract cannot mint new tokens, the transfer adapter can still sell transferable tokens you already hold. The target must allow the adapter to transfer those tokens out to collectors. Unlock them and allow the adapter as a sender in any transfer validator before the sale. Test a transfer from the adapter: being able to deposit tokens does not prove they can leave it. If you have no tokens available to transfer, neither adapter can deliver a mint.
Deploy and set up the adapter
The SeaDrop repository has the contracts and full deploy commands. In short:
- Deploy the adapter from the wallet that owns your existing contract. Pass your contract's address and an allowed SeaDrop address array containing the v1 minter for your chain from SeaDrop deployments. GUNZ, Somnia and MegaETH use a different v1 address from Ethereum and Base. The mint adapter also takes your mint function's selector, for example
cast sig 'mintTo(address,uint256)'. - Give the adapter something to deliver. For the mint adapter, grant its address minting rights on your contract. For the transfer adapter, mint the drop's tokens to the adapter's address, or send tokens you hold with
safeTransferFrom. Then checkqueuedTokenCounton the adapter. If a direct mint skipped the receiver callback, those tokens already exist in the adapter but are not queued. Callrescue(tokenId, owner)for each unqueued token, then deposit those same tokens withsafeTransferFrom. The adapter's owner must be the sender or operator for the deposit. For future deposits, mint to that owner's wallet first if the target uses a non-safe mint. - Call
setMaxSupplyon the adapter with the size of this drop. To drop your next 60 tokens, set it to 60. This limit applies to the drop only, not to your contract. For a mint adapter, confirm the target still has capacity to mint the full remaining allocation. For a transfer adapter, keep the cap no higher thantotalMinted() + queuedTokenCount(), including after withdrawals. - Contact OpenSea with your contract and adapter addresses to verify ownership and link the adapter to your collection. Then configure the drop stages and payouts in OpenSea Studio. Studio sends one
multiConfiguretransaction to the adapter when you select Publish changes. That transaction can overwrite the cap from step 3. Set Studio's item count to the drop allocation and verify the adapter'smaxSupply()after every publish, including on replacement adapters. You can also configure the adapter through its individual functions, such asupdateCreatorPayoutAddressandupdatePublicDrop. To let current holders mint first, add an allowlist stage with their addresses.
The adapter can't change your contract's metadata or royalties, so setBaseURI and setRoyaltyInfo on the adapter revert. Its multiConfigure function ignores the pre-reveal base URI from Studio. Keep managing token metadata and royalties on your existing contract. Edit the collection's Overview page separately in Studio to show the mint module and other page content.
Replace an earlier adapter
An earlier adapter without multiConfigure cannot publish changes through Studio and cannot be upgraded. Replacing it creates a separate drop: linking the new address does not stop the old adapter or copy its configuration and mint counts.
- Stop every stage on the old adapter by calling
updateAllowedSeaDropwith an empty array. For a mint adapter, also revoke its minting rights on the target. Record the final total and per-wallet mints after it is stopped. - Deploy the current adapter. Grant a mint adapter minting rights. For a transfer adapter, withdraw unsold tokens to its owner's wallet, then deposit them into the replacement with
safeTransferFrom. Rescue any unqueued tokens first and check the replacement'squeuedTokenCount. - Ask OpenSea to link the replacement. If the old drop had sales, coordinate the remaining per-wallet allocations with OpenSea before resuming. The replacement does not inherit those mint counts, so reusing the old wallet limits can let buyers mint their allocation again.
- Set the replacement's max supply to the remaining allocation, and configure its stages, prices and payouts in Studio after linking. Its counters start at zero, so do not reuse the original total allocation after earlier sales. A presale stage's
maxTokenSupplyForStagecaps cumulative sales across the adapter, not sales within that stage. It uses the adapter'stotalMinted(), not the target collection'stotalSupply(). Subtract the old adapter's finaltotalMinted()from each capped presale stage too: a cap of 300 after 120 old-adapter mints becomes 180 on the replacement. Leave stages whose caps were already reached closed. - Verify the replacement's configuration and delivery before resuming sales. Keep the old adapter disabled.
Show the drop on your collection
Once the adapter is deployed, contact OpenSea with your contract and adapter addresses, so the drop shows on your existing collection's page. OpenSea checks that the adapter was set up by your collection's owner before linking it.
After the drop
When the drop ends, revoke the adapter's minting rights on your contract. Each stage has its own end time, so ending the public sale leaves any allowlist stage open until it ends too. To stop every stage at once, call updateAllowedSeaDrop with an empty array. With the transfer adapter, call withdraw to take back queued tokens that didn't sell and rescue for unqueued tokens. Withdraw or rescue all inventory before renouncing the adapter's ownership, since only its owner can recover those tokens.
The adapters are new and haven't been audited. Test the full flow on a testnet before you use one on mainnet.
Updated about 21 hours ago