UnlimitedERC20 Unlimited ERC20 Tokens

See {IERC20-allowance}.

See {IERC20-approve}. Requirements: - `spender` cannot be the zero address.

See {IERC20-balanceOf}.

Destroys `amount` tokens from the caller. See {ERC20-_burn}.

Destroys `amount` tokens from `account`, deducting from the caller's allowance. See {ERC20-_burn} and {ERC20-allowance}. Requirements: - the caller must have allowance for ``accounts``'s tokens of at least `amount`.

Atomically decreases the allowance granted to `spender` by the caller. This is an alternative to {approve} that can be used as a mitigation for problems described in {IERC20-approve}. Emits an {Approval} event indicating the updated allowance. Requirements: - `spender` cannot be the zero address. - `spender` must have allowance for the caller of at least `subtractedValue`.

Function to stop minting new tokens. WARNING: it allows everyone to finish minting. Access controls MUST be defined in derived contracts.

Returns the admin role that controls `role`. See {grantRole} and {revokeRole}. To change a role's admin, use {_setRoleAdmin}.

Grants `role` to `account`. If `account` had not been already granted `role`, emits a {RoleGranted} event. Requirements: - the caller must have ``role``'s admin role.

Returns `true` if `account` has been granted `role`.

Atomically increases the allowance granted to `spender` by the caller. This is an alternative to {approve} that can be used as a mitigation for problems described in {IERC20-approve}. Emits an {Approval} event indicating the updated allowance. Requirements: - `spender` cannot be the zero address.

Function to mint tokens. WARNING: it allows everyone to mint new tokens. Access controls MUST be defined in derived contracts. - account: The address that will receive the minted tokens - amount: The amount of tokens to mint

undefined

Returns the name of the token.

Returns the address of the current owner.

Leaves the contract without owner. It will not be possible to call `onlyOwner` functions anymore. Can only be called by the current owner. NOTE: Renouncing ownership will leave the contract without an owner, thereby removing any functionality that is only available to the owner.

Revokes `role` from the calling account. Roles are often managed via {grantRole} and {revokeRole}: this function's purpose is to provide a mechanism for accounts to lose their privileges if they are compromised (such as when a trusted device is misplaced). If the calling account had been granted `role`, emits a {RoleRevoked} event. Requirements: - the caller must be `account`.

Revokes `role` from `account`. If `account` had been granted `role`, emits a {RoleRevoked} event. Requirements: - the caller must have ``role``'s admin role.

See {IERC165-supportsInterface}.

Returns the symbol of the token, usually a shorter version of the name.

See {IERC20-totalSupply}.

See {IERC20-transfer}. Requirements: - `recipient` cannot be the zero address. - the caller must have a balance of at least `amount`.

See {IERC20-transferFrom}. Emits an {Approval} event indicating the updated allowance. This is not required by the EIP. See the note at the beginning of {ERC20}. Requirements: - `sender` and `recipient` cannot be the zero address. - `sender` must have a balance of at least `amount`. - the caller must have allowance for ``sender``'s tokens of at least `amount`.

Transfers ownership of the contract to a new account (`newOwner`). Can only be called by the current owner.

This function returns the number of decimals used by the token, by calling the decimals function from the parent contracts. (autogenerated documentation)

This function mints new tokens to a specified account, and can only be called by a designated minter. (autogenerated documentation)

This function finishes the minting process by calling the parent function and can only be called by the contract owner. (autogenerated documentation)