Explore FAQ

All thirdweb prebuilt contracts are audited and can be recognized via green audit badge on the contract page.

To see a list of supported chains, see here. See here for details on how to add your EVM chain to thirdweb’s Chainlist.

When deploying a contract from the contracts publish page, in the Network / Chain tab of the deploy section, you can select add custom network from the drop down section. There you will be able to update the chainId, RPC and explorer URL for the custom chain you wish to deploy to.

By default, our prebuilt contracts are immutable once deployed. To upgrade the contract, a new contract with the upgraded code needs to be deployed. One exception to this, however, is the v2.0.0 version of our MarketplaceV3 contract is upgradeable, meaning you can make updates to the base contract code after the contract has been deployed.

All drop contracts now allow for updatable metadata straight from the explorer page.

Yes, we have a prebuilt Open Edition ERC 721 NFT contract here. You are able to deploy this contract to any EVM chain supported by thirdweb. To see a list of supported chains, see here. For example, to deploy the OE contract to Polygon mainnet you just have to select Polygon in the list of chains next to the deploy button.

Publishing your contract is the best way to get your contracts in front of our 70k+ community of web3 developers. You can learn more about Publish here. After you publish, contact our protocol team.

Deploying a contract published on Explore is around 10 times cheaper in terms of gas compared to deploying a custom contract. This is because the logic common to our pre-built contracts is delegated to a base contract, reducing the amount of code that needs to be deployed.

All of thirdweb’s NFT contracts support creator royalties. When deploying your contract, you can set your desired royalty percentage when your NFTs are traded on a secondary marketplace.

All of thirdweb’s Marketplace contract support NFT contract fees when NFTs are exchanged on the marketplace.

Not all third-party marketplaces support creator royalties, however. OpenSea announced that they're sunsetting their 'Operator Filter' https://opensea.io/blog/articles/creator-fees-update

Opensea will enforce the preferred creator royalty fee on secondary sales until February 29th, 2024. After this date, creator royalties will not be enforced on this marketplace.

To enforce royalties on secondary sales you can enable

You can share royalties or split revenue using our Split smart contract.

The Split contract lets you specify multiple wallet addresses that are recipients of any revenue or royalty split.

You define what percentage of any funds that get sent to the split contract address is sent to each recipient. For example, you could define 0x1 and 0x2 as recipients, and configure them to receive 50% of the funds sent to the split contract.

The split contract will store the funds, and when any user calls the distribute function, the funds will be distributed to the recipients according to the percentages you define.

Yes! On your NFT contract dashboard, select the Permissions tab, scroll to the bottom of the screen and select the Transferable / Non-Transferable.

Once deployed, Split contracts are immutable so it’s not possible to add additional addresses to the split. However, you can deploy a new Split contract and update your royalty settings to use that contract address to for future transactions.