Request form
Simple ERC20 Token
  • Token
  • ERC20
  • Fixed Supply
  • Audited
  • No-Code Deploy
  • Docs
    Source
    ChefGPT

    Simple ERC20 Token

    ERC20 token with the following features: -Premint your total supply. -No minting function. This allows users to comfortably know the future supply of the token.

    allowance(address,address) :
    See {IERC20-allowance}.
    approve(address,uint256) :
    See {IERC20-approve}. NOTE: If `amount` is the maximum `uint256`, the allowance is not updated on `transferFrom`. This is semantically equivalent to an infinite approval. Requirements: - `spender` cannot be the zero address.
    balanceOf(address) :
    See {IERC20-balanceOf}.
    decimals() :
    Returns the number of decimals used to get its user representation. For example, if `decimals` equals `2`, a balance of `505` tokens should be displayed to a user as `5.05` (`505 / 10 ** 2`). Tokens usually opt for a value of 18, imitating the relationship between Ether and Wei. This is the value {ERC20} uses, unless this function is overridden; NOTE: This information is only used for _display_ purposes: it in no way affects any of the arithmetic of the contract, including {IERC20-balanceOf} and {IERC20-transfer}.
    decreaseAllowance(address,uint256) :
    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`.
    increaseAllowance(address,uint256) :
    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.
    name() :
    Returns the name of the token.
    symbol() :
    Returns the symbol of the token, usually a shorter version of the name.
    totalSupply() :
    See {IERC20-totalSupply}.
    transfer(address,uint256) :
    See {IERC20-transfer}. Requirements: - `to` cannot be the zero address. - the caller must have a balance of at least `amount`.
    transferFrom(address,address,uint256) :
    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}. NOTE: Does not update the allowance if the current allowance is the maximum `uint256`. Requirements: - `from` and `to` cannot be the zero address. - `from` must have a balance of at least `amount`. - the caller must have allowance for ``from``'s tokens of at least `amount`.
    simple-token.sol
    ERC20.sol
    IERC20.sol
    IERC20Metadata.sol
    Context.sol
    ABI:
    Bytecode:

    4963 downloads

    Solidity Version

    0.8.12
    OpenZeppelin / Simple ERC20 Token
  • Token
  • ERC20
  • Fixed Supply
  • Audited
  • No-Code Deploy
  • Docs
    Source
    ChefGPT
    Expand
    Share

    Simple ERC20 Token

    ERC20 token with the following features: -Premint your total supply. -No minting function. This allows users to comfortably know the future supply of the token.

    allowance(address,address) :
    See {IERC20-allowance}.
    approve(address,uint256) :
    See {IERC20-approve}. NOTE: If `amount` is the maximum `uint256`, the allowance is not updated on `transferFrom`. This is semantically equivalent to an infinite approval. Requirements: - `spender` cannot be the zero address.
    balanceOf(address) :
    See {IERC20-balanceOf}.
    decimals() :
    Returns the number of decimals used to get its user representation. For example, if `decimals` equals `2`, a balance of `505` tokens should be displayed to a user as `5.05` (`505 / 10 ** 2`). Tokens usually opt for a value of 18, imitating the relationship between Ether and Wei. This is the value {ERC20} uses, unless this function is overridden; NOTE: This information is only used for _display_ purposes: it in no way affects any of the arithmetic of the contract, including {IERC20-balanceOf} and {IERC20-transfer}.
    decreaseAllowance(address,uint256) :
    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`.
    increaseAllowance(address,uint256) :
    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.
    name() :
    Returns the name of the token.
    symbol() :
    Returns the symbol of the token, usually a shorter version of the name.
    totalSupply() :
    See {IERC20-totalSupply}.
    transfer(address,uint256) :
    See {IERC20-transfer}. Requirements: - `to` cannot be the zero address. - the caller must have a balance of at least `amount`.
    transferFrom(address,address,uint256) :
    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}. NOTE: Does not update the allowance if the current allowance is the maximum `uint256`. Requirements: - `from` and `to` cannot be the zero address. - `from` must have a balance of at least `amount`. - the caller must have allowance for ``from``'s tokens of at least `amount`.
    simple-token.sol
    ERC20.sol
    IERC20.sol
    IERC20Metadata.sol
    Context.sol
    ABI:
    Bytecode:

    Get Cookin'
    star icon4963

    4963 downloads

    Solidity Version

    0.8.12