MineToken

Description:

Multi-signature wallet contract requiring multiple confirmations for transaction execution.

Blockchain: Ethereum

Source Code: View Code On The Blockchain

Solidity Source Code:

{{
  "language": "Solidity",
  "sources": {
    "MineToken.sol": {
      "content": "// SPDX-License-Identifier: MIT\r
// File: @openzeppelin\contracts\	oken\ERC20\IERC20.sol\r
\r
// OpenZeppelin Contracts (last updated v4.9.0) (token/ERC20/IERC20.sol)\r
\r
pragma solidity ^0.8.0;\r
\r
/**\r
 * @dev Interface of the ERC20 standard as defined in the EIP.\r
 */\r
interface IERC20 {\r
    /**\r
     * @dev Emitted when `value` tokens are moved from one account (`from`) to\r
     * another (`to`).\r
     *\r
     * Note that `value` may be zero.\r
     */\r
    event Transfer(address indexed from, address indexed to, uint256 value);\r
\r
    /**\r
     * @dev Emitted when the allowance of a `spender` for an `owner` is set by\r
     * a call to {approve}. `value` is the new allowance.\r
     */\r
    event Approval(\r
        address indexed owner,\r
        address indexed spender,\r
        uint256 value\r
    );\r
\r
    /**\r
     * @dev Returns the amount of tokens in existence.\r
     */\r
    function totalSupply() external view returns (uint256);\r
\r
    /**\r
     * @dev Returns the amount of tokens owned by `account`.\r
     */\r
    function balanceOf(address account) external view returns (uint256);\r
\r
    /**\r
     * @dev Moves `amount` tokens from the caller's account to `to`.\r
     *\r
     * Returns a boolean value indicating whether the operation succeeded.\r
     *\r
     * Emits a {Transfer} event.\r
     */\r
    function transfer(address to, uint256 amount) external returns (bool);\r
\r
    /**\r
     * @dev Returns the remaining number of tokens that `spender` will be\r
     * allowed to spend on behalf of `owner` through {transferFrom}. This is\r
     * zero by default.\r
     *\r
     * This value changes when {approve} or {transferFrom} are called.\r
     */\r
    function allowance(\r
        address owner,\r
        address spender\r
    ) external view returns (uint256);\r
\r
    /**\r
     * @dev Sets `amount` as the allowance of `spender` over the caller's tokens.\r
     *\r
     * Returns a boolean value indicating whether the operation succeeded.\r
     *\r
     * IMPORTANT: Beware that changing an allowance with this method brings the risk\r
     * that someone may use both the old and the new allowance by unfortunate\r
     * transaction ordering. One possible solution to mitigate this race\r
     * condition is to first reduce the spender's allowance to 0 and set the\r
     * desired value afterwards:\r
     * https://github.com/ethereum/EIPs/issues/20#issuecomment-263524729\r
     *\r
     * Emits an {Approval} event.\r
     */\r
    function approve(address spender, uint256 amount) external returns (bool);\r
\r
    /**\r
     * @dev Moves `amount` tokens from `from` to `to` using the\r
     * allowance mechanism. `amount` is then deducted from the caller's\r
     * allowance.\r
     *\r
     * Returns a boolean value indicating whether the operation succeeded.\r
     *\r
     * Emits a {Transfer} event.\r
     */\r
    function transferFrom(\r
        address from,\r
        address to,\r
        uint256 amount\r
    ) external returns (bool);\r
}\r
\r
// File: @openzeppelin\contracts\	oken\ERC20\extensions\IERC20Metadata.sol\r
\r
// OpenZeppelin Contracts v4.4.1 (token/ERC20/extensions/IERC20Metadata.sol)\r
\r
pragma solidity ^0.8.0;\r
\r
/**\r
 * @dev Interface for the optional metadata functions from the ERC20 standard.\r
 *\r
 * _Available since v4.1._\r
 */\r
interface IERC20Metadata is IERC20 {\r
    /**\r
     * @dev Returns the name of the token.\r
     */\r
    function name() external view returns (string memory);\r
\r
    /**\r
     * @dev Returns the symbol of the token.\r
     */\r
    function symbol() external view returns (string memory);\r
\r
    /**\r
     * @dev Returns the decimals places of the token.\r
     */\r
    function decimals() external view returns (uint8);\r
}\r
\r
// File: @openzeppelin\contracts\utils\Context.sol\r
\r
// OpenZeppelin Contracts (last updated v4.9.4) (utils/Context.sol)\r
\r
pragma solidity ^0.8.0;\r
\r
/**\r
 * @dev Provides information about the current execution context, including the\r
 * sender of the transaction and its data. While these are generally available\r
 * via msg.sender and msg.data, they should not be accessed in such a direct\r
 * manner, since when dealing with meta-transactions the account sending and\r
 * paying for execution may not be the actual sender (as far as an application\r
 * is concerned).\r
 *\r
 * This contract is only required for intermediate, library-like contracts.\r
 */\r
abstract contract Context {\r
    function _msgSender() internal view virtual returns (address) {\r
        return msg.sender;\r
    }\r
\r
    function _msgData() internal view virtual returns (bytes calldata) {\r
        return msg.data;\r
    }\r
\r
    function _contextSuffixLength() internal view virtual returns (uint256) {\r
        return 0;\r
    }\r
}\r
\r
// File: @openzeppelin\contracts\	oken\ERC20\ERC20.sol\r
\r
// OpenZeppelin Contracts (last updated v4.9.0) (token/ERC20/ERC20.sol)\r
\r
pragma solidity ^0.8.0;\r
\r
/**\r
 * @dev Implementation of the {IERC20} interface.\r
 *\r
 * This implementation is agnostic to the way tokens are created. This means\r
 * that a supply mechanism has to be added in a derived contract using {_mint}.\r
 * For a generic mechanism see {ERC20PresetMinterPauser}.\r
 *\r
 * TIP: For a detailed writeup see our guide\r
 * https://forum.openzeppelin.com/t/how-to-implement-erc20-supply-mechanisms/226[How\r
 * to implement supply mechanisms].\r
 *\r
 * The default value of {decimals} is 18. To change this, you should override\r
 * this function so it returns a different value.\r
 *\r
 * We have followed general OpenZeppelin Contracts guidelines: functions revert\r
 * instead returning `false` on failure. This behavior is nonetheless\r
 * conventional and does not conflict with the expectations of ERC20\r
 * applications.\r
 *\r
 * Additionally, an {Approval} event is emitted on calls to {transferFrom}.\r
 * This allows applications to reconstruct the allowance for all accounts just\r
 * by listening to said events. Other implementations of the EIP may not emit\r
 * these events, as it isn't required by the specification.\r
 *\r
 * Finally, the non-standard {decreaseAllowance} and {increaseAllowance}\r
 * functions have been added to mitigate the well-known issues around setting\r
 * allowances. See {IERC20-approve}.\r
 */\r
contract ERC20 is Context, IERC20, IERC20Metadata {\r
    mapping(address => uint256) private _balances;\r
\r
    mapping(address => mapping(address => uint256)) private _allowances;\r
\r
    uint256 private _totalSupply;\r
\r
    string private _name;\r
    string private _symbol;\r
\r
    /**\r
     * @dev Sets the values for {name} and {symbol}.\r
     *\r
     * All two of these values are immutable: they can only be set once during\r
     * construction.\r
     */\r
    constructor(string memory name_, string memory symbol_) {\r
        _name = name_;\r
        _symbol = symbol_;\r
    }\r
\r
    /**\r
     * @dev Returns the name of the token.\r
     */\r
    function name() public view virtual override returns (string memory) {\r
        return _name;\r
    }\r
\r
    /**\r
     * @dev Returns the symbol of the token, usually a shorter version of the\r
     * name.\r
     */\r
    function symbol() public view virtual override returns (string memory) {\r
        return _symbol;\r
    }\r
\r
    /**\r
     * @dev Returns the number of decimals used to get its user representation.\r
     * For example, if `decimals` equals `2`, a balance of `505` tokens should\r
     * be displayed to a user as `5.05` (`505 / 10 ** 2`).\r
     *\r
     * Tokens usually opt for a value of 18, imitating the relationship between\r
     * Ether and Wei. This is the default value returned by this function, unless\r
     * it's overridden.\r
     *\r
     * NOTE: This information is only used for _display_ purposes: it in\r
     * no way affects any of the arithmetic of the contract, including\r
     * {IERC20-balanceOf} and {IERC20-transfer}.\r
     */\r
    function decimals() public view virtual override returns (uint8) {\r
        return 18;\r
    }\r
\r
    /**\r
     * @dev See {IERC20-totalSupply}.\r
     */\r
    function totalSupply() public view virtual override returns (uint256) {\r
        return _totalSupply;\r
    }\r
\r
    /**\r
     * @dev See {IERC20-balanceOf}.\r
     */\r
    function balanceOf(\r
        address account\r
    ) public view virtual override returns (uint256) {\r
        return _balances[account];\r
    }\r
\r
    /**\r
     * @dev See {IERC20-transfer}.\r
     *\r
     * Requirements:\r
     *\r
     * - `to` cannot be the zero address.\r
     * - the caller must have a balance of at least `amount`.\r
     */\r
    function transfer(\r
        address to,\r
        uint256 amount\r
    ) public virtual override returns (bool) {\r
        address owner = _msgSender();\r
        _transfer(owner, to, amount);\r
        return true;\r
    }\r
\r
    /**\r
     * @dev See {IERC20-allowance}.\r
     */\r
    function allowance(\r
        address owner,\r
        address spender\r
    ) public view virtual override returns (uint256) {\r
        return _allowances[owner][spender];\r
    }\r
\r
    /**\r
     * @dev See {IERC20-approve}.\r
     *\r
     * NOTE: If `amount` is the maximum `uint256`, the allowance is not updated on\r
     * `transferFrom`. This is semantically equivalent to an infinite approval.\r
     *\r
     * Requirements:\r
     *\r
     * - `spender` cannot be the zero address.\r
     */\r
    function approve(\r
        address spender,\r
        uint256 amount\r
    ) public virtual override returns (bool) {\r
        address owner = _msgSender();\r
        _approve(owner, spender, amount);\r
        return true;\r
    }\r
\r
    /**\r
     * @dev See {IERC20-transferFrom}.\r
     *\r
     * Emits an {Approval} event indicating the updated allowance. This is not\r
     * required by the EIP. See the note at the beginning of {ERC20}.\r
     *\r
     * NOTE: Does not update the allowance if the current allowance\r
     * is the maximum `uint256`.\r
     *\r
     * Requirements:\r
     *\r
     * - `from` and `to` cannot be the zero address.\r
     * - `from` must have a balance of at least `amount`.\r
     * - the caller must have allowance for ``from``'s tokens of at least\r
     * `amount`.\r
     */\r
    function transferFrom(\r
        address from,\r
        address to,\r
        uint256 amount\r
    ) public virtual override returns (bool) {\r
        address spender = _msgSender();\r
        _spendAllowance(from, spender, amount);\r
        _transfer(from, to, amount);\r
        return true;\r
    }\r
\r
    /**\r
     * @dev Atomically increases the allowance granted to `spender` by the caller.\r
     *\r
     * This is an alternative to {approve} that can be used as a mitigation for\r
     * problems described in {IERC20-approve}.\r
     *\r
     * Emits an {Approval} event indicating the updated allowance.\r
     *\r
     * Requirements:\r
     *\r
     * - `spender` cannot be the zero address.\r
     */\r
    function increaseAllowance(\r
        address spender,\r
        uint256 addedValue\r
    ) public virtual returns (bool) {\r
        address owner = _msgSender();\r
        _approve(owner, spender, allowance(owner, spender) + addedValue);\r
        return true;\r
    }\r
\r
    /**\r
     * @dev Atomically decreases the allowance granted to `spender` by the caller.\r
     *\r
     * This is an alternative to {approve} that can be used as a mitigation for\r
     * problems described in {IERC20-approve}.\r
     *\r
     * Emits an {Approval} event indicating the updated allowance.\r
     *\r
     * Requirements:\r
     *\r
     * - `spender` cannot be the zero address.\r
     * - `spender` must have allowance for the caller of at least\r
     * `subtractedValue`.\r
     */\r
    function decreaseAllowance(\r
        address spender,\r
        uint256 subtractedValue\r
    ) public virtual returns (bool) {\r
        address owner = _msgSender();\r
        uint256 currentAllowance = allowance(owner, spender);\r
        require(\r
            currentAllowance >= subtractedValue,\r
            "ERC20: decreased allowance below zero"\r
        );\r
        unchecked {\r
            _approve(owner, spender, currentAllowance - subtractedValue);\r
        }\r
\r
        return true;\r
    }\r
\r
    /**\r
     * @dev Moves `amount` of tokens from `from` to `to`.\r
     *\r
     * This internal function is equivalent to {transfer}, and can be used to\r
     * e.g. implement automatic token fees, slashing mechanisms, etc.\r
     *\r
     * Emits a {Transfer} event.\r
     *\r
     * Requirements:\r
     *\r
     * - `from` cannot be the zero address.\r
     * - `to` cannot be the zero address.\r
     * - `from` must have a balance of at least `amount`.\r
     */\r
    function _transfer(\r
        address from,\r
        address to,\r
        uint256 amount\r
    ) internal virtual {\r
        require(from != address(0), "ERC20: transfer from the zero address");\r
        require(to != address(0), "ERC20: transfer to the zero address");\r
\r
        _beforeTokenTransfer(from, to, amount);\r
\r
        uint256 fromBalance = _balances[from];\r
        require(\r
            fromBalance >= amount,\r
            "ERC20: transfer amount exceeds balance"\r
        );\r
        unchecked {\r
            _balances[from] = fromBalance - amount;\r
            // Overflow not possible: the sum of all balances is capped by totalSupply, and the sum is preserved by\r
            // decrementing then incrementing.\r
            _balances[to] += amount;\r
        }\r
\r
        emit Transfer(from, to, amount);\r
\r
        _afterTokenTransfer(from, to, amount);\r
    }\r
\r
    /** @dev Creates `amount` tokens and assigns them to `account`, increasing\r
     * the total supply.\r
     *\r
     * Emits a {Transfer} event with `from` set to the zero address.\r
     *\r
     * Requirements:\r
     *\r
     * - `account` cannot be the zero address.\r
     */\r
    function _mint(address account, uint256 amount) internal virtual {\r
        require(account != address(0), "ERC20: mint to the zero address");\r
\r
        _beforeTokenTransfer(address(0), account, amount);\r
\r
        _totalSupply += amount;\r
        unchecked {\r
            // Overflow not possible: balance + amount is at most totalSupply + amount, which is checked above.\r
            _balances[account] += amount;\r
        }\r
        emit Transfer(address(0), account, amount);\r
\r
        _afterTokenTransfer(address(0), account, amount);\r
    }\r
\r
    /**\r
     * @dev Destroys `amount` tokens from `account`, reducing the\r
     * total supply.\r
     *\r
     * Emits a {Transfer} event with `to` set to the zero address.\r
     *\r
     * Requirements:\r
     *\r
     * - `account` cannot be the zero address.\r
     * - `account` must have at least `amount` tokens.\r
     */\r
    function _burn(address account, uint256 amount) internal virtual {\r
        require(account != address(0), "ERC20: burn from the zero address");\r
\r
        _beforeTokenTransfer(account, address(0), amount);\r
\r
        uint256 accountBalance = _balances[account];\r
        require(accountBalance >= amount, "ERC20: burn amount exceeds balance");\r
        unchecked {\r
            _balances[account] = accountBalance - amount;\r
            // Overflow not possible: amount <= accountBalance <= totalSupply.\r
            _totalSupply -= amount;\r
        }\r
\r
        emit Transfer(account, address(0), amount);\r
\r
        _afterTokenTransfer(account, address(0), amount);\r
    }\r
\r
    /**\r
     * @dev Sets `amount` as the allowance of `spender` over the `owner` s tokens.\r
     *\r
     * This internal function is equivalent to `approve`, and can be used to\r
     * e.g. set automatic allowances for certain subsystems, etc.\r
     *\r
     * Emits an {Approval} event.\r
     *\r
     * Requirements:\r
     *\r
     * - `owner` cannot be the zero address.\r
     * - `spender` cannot be the zero address.\r
     */\r
    function _approve(\r
        address owner,\r
        address spender,\r
        uint256 amount\r
    ) internal virtual {\r
        require(owner != address(0), "ERC20: approve from the zero address");\r
        require(spender != address(0), "ERC20: approve to the zero address");\r
\r
        _allowances[owner][spender] = amount;\r
        emit Approval(owner, spender, amount);\r
    }\r
\r
    /**\r
     * @dev Updates `owner` s allowance for `spender` based on spent `amount`.\r
     *\r
     * Does not update the allowance amount in case of infinite allowance.\r
     * Revert if not enough allowance is available.\r
     *\r
     * Might emit an {Approval} event.\r
     */\r
    function _spendAllowance(\r
        address owner,\r
        address spender,\r
        uint256 amount\r
    ) internal virtual {\r
        uint256 currentAllowance = allowance(owner, spender);\r
        if (currentAllowance != type(uint256).max) {\r
            require(\r
                currentAllowance >= amount,\r
                "ERC20: insufficient allowance"\r
            );\r
            unchecked {\r
                _approve(owner, spender, currentAllowance - amount);\r
            }\r
        }\r
    }\r
\r
    /**\r
     * @dev Hook that is called before any transfer of tokens. This includes\r
     * minting and burning.\r
     *\r
     * Calling conditions:\r
     *\r
     * - when `from` and `to` are both non-zero, `amount` of ``from``'s tokens\r
     * will be transferred to `to`.\r
     * - when `from` is zero, `amount` tokens will be minted for `to`.\r
     * - when `to` is zero, `amount` of ``from``'s tokens will be burned.\r
     * - `from` and `to` are never both zero.\r
     *\r
     * To learn more about hooks, head to xref:ROOT:extending-contracts.adoc#using-hooks[Using Hooks].\r
     */\r
    function _beforeTokenTransfer(\r
        address from,\r
        address to,\r
        uint256 amount\r
    ) internal virtual {}\r
\r
    /**\r
     * @dev Hook that is called after any transfer of tokens. This includes\r
     * minting and burning.\r
     *\r
     * Calling conditions:\r
     *\r
     * - when `from` and `to` are both non-zero, `amount` of ``from``'s tokens\r
     * has been transferred to `to`.\r
     * - when `from` is zero, `amount` tokens have been minted for `to`.\r
     * - when `to` is zero, `amount` of ``from``'s tokens have been burned.\r
     * - `from` and `to` are never both zero.\r
     *\r
     * To learn more about hooks, head to xref:ROOT:extending-contracts.adoc#using-hooks[Using Hooks].\r
     */\r
    function _afterTokenTransfer(\r
        address from,\r
        address to,\r
        uint256 amount\r
    ) internal virtual {}\r
}\r
\r
// File: @openzeppelin\contracts\access\Ownable.sol\r
\r
// OpenZeppelin Contracts (last updated v4.9.0) (access/Ownable.sol)\r
\r
pragma solidity ^0.8.0;\r
\r
/**\r
 * @dev Contract module which provides a basic access control mechanism, where\r
 * there is an account (an owner) that can be granted exclusive access to\r
 * specific functions.\r
 *\r
 * By default, the owner account will be the one that deploys the contract. This\r
 * can later be changed with {transferOwnership}.\r
 *\r
 * This module is used through inheritance. It will make available the modifier\r
 * `onlyOwner`, which can be applied to your functions to restrict their use to\r
 * the owner.\r
 */\r
abstract contract Ownable is Context {\r
    address private _owner;\r
\r
    event OwnershipTransferred(\r
        address indexed previousOwner,\r
        address indexed newOwner\r
    );\r
\r
    /**\r
     * @dev Initializes the contract setting the deployer as the initial owner.\r
     */\r
    constructor() {\r
        _transferOwnership(_msgSender());\r
    }\r
\r
    /**\r
     * @dev Throws if called by any account other than the owner.\r
     */\r
    modifier onlyOwner() {\r
        _checkOwner();\r
        _;\r
    }\r
\r
    /**\r
     * @dev Returns the address of the current owner.\r
     */\r
    function owner() public view virtual returns (address) {\r
        return _owner;\r
    }\r
\r
    /**\r
     * @dev Throws if the sender is not the owner.\r
     */\r
    function _checkOwner() internal view virtual {\r
        require(owner() == _msgSender(), "Ownable: caller is not the owner");\r
    }\r
\r
    /**\r
     * @dev Leaves the contract without owner. It will not be possible to call\r
     * `onlyOwner` functions. Can only be called by the current owner.\r
     *\r
     * NOTE: Renouncing ownership will leave the contract without an owner,\r
     * thereby disabling any functionality that is only available to the owner.\r
     */\r
    function renounceOwnership() public virtual onlyOwner {\r
        _transferOwnership(address(0));\r
    }\r
\r
    /**\r
     * @dev Transfers ownership of the contract to a new account (`newOwner`).\r
     * Can only be called by the current owner.\r
     */\r
    function transferOwnership(address newOwner) public virtual onlyOwner {\r
        require(\r
            newOwner != address(0),\r
            "Ownable: new owner is the zero address"\r
        );\r
        _transferOwnership(newOwner);\r
    }\r
\r
    /**\r
     * @dev Transfers ownership of the contract to a new account (`newOwner`).\r
     * Internal function without access restriction.\r
     */\r
    function _transferOwnership(address newOwner) internal virtual {\r
        address oldOwner = _owner;\r
        _owner = newOwner;\r
        emit OwnershipTransferred(oldOwner, newOwner);\r
    }\r
}\r
\r
// File: contracts\MineToken.sol\r
\r
pragma solidity ^0.8.0;\r
\r
contract MineToken is ERC20, Ownable {\r
    address public operator;\r
\r
    event OperatorSet(address indexed operator);\r
\r
    constructor() ERC20("Lendep Coin", "LDC") {}\r
\r
    modifier onlyOperator() {\r
        require(msg.sender == operator, "Not operator");\r
        _;\r
    }\r
\r
    function setOperator(address _operator) external onlyOwner {\r
        operator = _operator;\r
        emit OperatorSet(_operator);\r
    }\r
\r
    function mint(address to, uint256 amount) external onlyOperator {\r
        _mint(to, amount);\r
    }\r
}"
    }
  },
  "settings": {
    "optimizer": {
      "enabled": true,
      "runs": 200
    },
    "outputSelection": {
      "*": {
        "*": [
          "evm.bytecode",
          "evm.deployedBytecode",
          "devdoc",
          "userdoc",
          "metadata",
          "abi"
        ]
      }
    },
    "remappings": [],
    "evmVersion": "prague"
  }
}}

Tags:
ERC20, Multisig, Mintable, Multi-Signature, Factory|addr:0x044ca854fa227e27e07652b7f6a6b578703f3945|verified:true|block:23731528|tx:0x8dc83a82db1b7cc9d948dd2f2f37418115cd1bb892fcfd1a346c0dc80be01ba5|first_check:1762345869

Submitted on: 2025-11-05 13:31:11

Comments

Log in to comment.

No comments yet.