📄️ getBalance
The getBalance method fetches the balance of a specific Ethereum address for the associated ERC20 token. This method belongs to the ERC20Instance object returned by the getERC20Instance method of EdexaClient.
📄️ getAllowance
The getAllowance method determines the amount of tokens an owner has permitted another Ethereum address to expend on their behalf. This method often finds use in tandem with token approvals, especially in scenarios such as granting a smart contract the capability to move tokens on one's behalf. The method is an attribute of the ERC20Instance object, derived from the getERC20Instance function of the EdexaClient.
📄️ transfer
The transfer method allows token holders to send a specified amount of tokens to another Ethereum address. This is one of the fundamental operations of any ERC20 token. The method belongs to the ERC20Instance object, which is returned by the getERC20Instance method of EdexaClient.
📄️ approve
The approve method is used by token holders to give permission to another Ethereum address (typically a contract) to spend a specified amount of tokens on their behalf. This is a common operation in various Ethereum protocols and dApps, especially when tokens are used as part of another system (like decentralized exchanges or lending platforms). The method belongs to the ERC20Instance object, which is returned by the getERC20Instance method of EdexaClient.
📄️ burn
The burn method is used by token holders to destroy or "burn" a specified amount of their tokens, effectively removing them from circulation. Burning tokens can serve various purposes, including reducing the overall supply or fulfilling specific protocol requirements. The method typically belongs to objects or contracts that incorporate a burning functionality, as seen in ERC20 or ERC721 token standards.
📄️ burnFrom
The burnFrom method is designed to permit a user (or contract) to burn or destroy a specified quantity of tokens from another user's account. This action requires the prior consent of the token owner, usually obtained via the approve method. The capability to burn tokens from another user's account can be incorporated in specific token contracts for particular use cases, such as staking or governance scenarios.
📄️ mint
The mint method is employed to produce and assign a determined quantity of tokens to a specific Ethereum address. This function is predominantly associated with Mintable ERC20 tokens. Typically, only particular roles, like the owner or minter role within a token contract, can execute this function. The availability and operation of this method hinge on the unique implementation of the ERC20 token. Here, we're assuming the method is a feature of the ERC20Instance object, which is derived from the getERC20Instance function of the EdexaClient.
📄️ pause
The pause function is specifically crafted to temporarily suspend specific functionalities within a contract, contingent upon its underlying code. Operations such as transfers, approvals, or other contract-related tasks might be impacted. Typically, the pause method is activated during emergencies or for upkeep. The authority to initiate this function is generally reserved for contract proprietors or selected admins.
📄️ unpause
The unpause function is commonly associated with Pausable smart contracts in the Ethereum ecosystem. It allows specific authorized accounts (often the contract owner or designated admin) to resume the contract's operations after they've been paused, ensuring that normal contract functionalities can continue. This is especially useful in emergent scenarios where the contract needs to be temporarily halted to address issues.
📄️ renounceOwnership
The renounceOwnership method allows the current owner of a smart contract to relinquish their ownership rights. Once executed, the contract will have no owner, and certain functionalities that are typically restricted to the owner might become inaccessible. This operation is irreversible, and extreme caution should be exercised before using this method. This method is often found in contracts that implement the Ownable pattern.
📄️ transferOwnership
The transferOwnership method allows the current owner of a contract (often a deployer) to transfer control of the contract to another Ethereum address. This can be useful in scenarios such as transferring control to a governance mechanism or upgrading contracts. The new owner will have the ability to execute critical functions that may be restricted to the owner only.