Sonic Logo
Mantle

Contract Functions

DropERC721

A contract for managing a collection of non-fungible tokens (NFTs) with a drop mechanism.

Version 1.0.1

DropERC721 Contract

The DropERC721 contract enables the creation and management of a collection of ERC721 NFTs with a drop mechanism. This means that tokens are initially unavailable and are only released at a specific point in time. This is useful for creating limited-edition collections or managing the release of NFTs over time.

Features

  • **Drop Mechanism:** Allows for controlled release of NFTs at a specified time.
  • **Minting Functionality:** Enables the creation of new NFTs within the collection.
  • **Claim Functionality:** Provides a mechanism for users to claim their NFTs after the drop.
  • **ERC721 Compliance:** Adheres to the ERC721 standard for non-fungible tokens.
  • **Base URI Management:** Allows for setting and updating the base URI for token metadata.

    • Usage

    To use the DropERC721 contract, you can interact with it through its public functions. Here are some key examples:

  • **`initializeDrop(uint256 _maxTotalMintable)`: Set the maximum number of NFTs that can be minted in the collection.
  • **`setBaseURI(string memory _baseURI)`: Set the base URI for token metadata.
  • **`startDrop()`: Start the drop, making NFTs claimable.
  • **`claim()`: Claim an NFT from the collection. This can be called by users after the drop has started.
  • **`mint()`: Mint a new NFT (can be called by the owner of the contract). This function is typically used to add additional NFTs to the collection after the drop has started.

    • Implementation Details

    The DropERC721 contract is implemented using the ERC721 standard. It includes functions for minting, transferring, and managing NFTs. The drop mechanism is implemented through the ` + '`' + `_dropStarted` + '`' + ` variable, which indicates whether the drop has started.

    Best Practices

  • Ensure sufficient gas for the `claim()` function, as the transaction might require a significant amount of gas.
  • Consider implementing a whitelist or allowlist mechanism for controlled access to the drop.
  • Test the contract thoroughly before deploying it to a live network.

    • Functions

    initializeDrop

    initializeDrop(uint256)

    setBaseURI

    setBaseURI(string)

    startDrop

    startDrop()

    claim

    claim()

    mint

    mint()
    Ask about contract functions, security, or implementation details

    Press Enter to send your query

    Resources

    ERC721 StandardOpenZeppelin ERC721 DocumentationDrop Contract OverviewERC20 StandardERC1155 StandardOpenZeppelin Merkle Proof LibraryOpenZeppelin Access Control LibraryEthereum.org - Smart ContractsSolidity DocumentationRemix IDEHardhat DocumentationTruffle DocumentationEthers.js DocumentationWeb3.js Documentation

    Source Code

    1