📄️ getBalance
The getBalance method for the ERC-721 token standard provides the number of tokens owned by a specific Ethereum address. Unlike ERC20's balance, which reflects a quantity, the balance for ERC-721 reflects the count of unique, non-fungible tokens owned by an address. The method is part of the ERC721Instance object, which is obtainable via an appropriate method of the EdexaClient or the corresponding library.
📄️ getApproved
The getApproved method is specific to the ERC-721 token standard. It allows users to query which Ethereum address (if any) is currently approved to transfer a specific ERC-721 token. Each non-fungible token (NFT) can have only one approved address at a time, besides its owner who can always transfer the token. This method is part of the ERC721Instance object, which can be acquired via an appropriate method of the client library (e.g., EdexaClient or similar).
📄️ ownerOf
The ownerOf method is specific to the ERC-721 token standard and is used to determine the current owner of a specific non-fungible token (NFT). Given a unique token identifier, this method will return the Ethereum address that currently owns the token. This function is essential for various operations and checks related to ownership within the ERC-721 ecosystem. The method is a member of the ERC721Instance object, which can be retrieved using the appropriate function from the client library (e.g., EdexaClient or a similar one).
📄️ tokenURI
The tokenURI method is specific to the ERC-721 token standard. It retrieves a Uniform Resource Identifier (URI) for a given token ID. This URI typically points to metadata about the token, such as a JSON file containing attributes like the token's name, description, image, and other attributes. The method is an integral part of the ERC721Instance object, which can be acquired via an appropriate method of the client library (e.g., EdexaClient or similar).
📄️ burn
The burn method, commonly found in some ERC-721 token implementations, allows for the permanent removal of a non-fungible token (NFT) from circulation. Once a token is burned, it can no longer be transferred, and its data is effectively deleted. This action is irreversible. The burn method is part of the ERC721Instance object, obtainable through the appropriate client library (e.g., EdexaClient or equivalent).
📄️ pause
The pause method is relevant to ERC-721 tokens that incorporate the "Pausable" functionality. This function allows the contract's owner or designated pausers to temporarily halt certain actions within the contract, such as transferring or minting tokens. This can be useful in emergency scenarios or for maintenance. The pause method is part of the ERC721Instance object, which can be obtained via appropriate methods from the client library (e.g., EdexaClient or similar).
📄️ renounceOwnership
The renounceOwnership method is part of the ownership management feature common to some ERC-721 token implementations. By invoking this method, the current owner of the contract relinquishes control, effectively making the contract ownerless. This action is irreversible, and once executed, certain administrative functionalities originally reserved for the owner will be permanently inaccessible. This method is a part of the ERC721Instance object.
📄️ transferOwnership
The transferOwnership method is specific to the ERC-721 token standard, allowing current owners of a non-fungible token (NFT) to transfer ownership of that token to another Ethereum address. This operation is vital for selling, gifting, or otherwise transferring the rights and control of an individual NFT. It is a part of the ERC721Instance object, accessible through client libraries like EdexaClient.
📄️ unpause
The unpause method pertains to the ERC-721 token standard, particularly for implementations that incorporate the Pausable design pattern. The Pausable design pattern allows for certain operations or functionalities of a contract to be paused, often for administrative or emergency reasons. The unpause method, when called, resumes the functionalities that were previously halted. This method is part of the ERC721Instance object, which can be derived via an appropriate method of the client library (e.g., EdexaClient or its equivalent).
📄️ safeMint
The safeMint method is particular to the ERC-721 token standard, which represents non-fungible tokens (NFTs) on the Ethereum blockchain. This method allows the minting of a new NFT and assigns it to a specified Ethereum address. The "safe" in safeMint ensures that the destination address can securely receive NFTs, checking if the recipient address has implemented the required functions to accept ERC-721 tokens.
📄️ approve
The approve method, in the context of the ERC-721 token standard, permits the owner of a specific non-fungible token (NFT) to approve another Ethereum address to transfer said NFT on their behalf. Each NFT can have only one approved address at any given time. This method belongs to the ERC721Instance object, obtainable from the appropriate client library (like EdexaClient or its equivalent).
📄️ safeTransferFrom
The safeTransferFrom method pertains to the ERC-721 token standard (often associated with non-fungible tokens or NFTs). This method allows for the secure transfer of a specific NFT from one Ethereum address to another. The "safe" in its name implies that this method also checks to ensure that the receiving address is capable of handling ERC-721 tokens, adding an extra layer of protection against accidental loss of tokens. The method is part of the ERC721Instance object, typically accessible through client libraries such as EdexaClient.