Conversation with Merlin [email protected] · Thu Dec 28 2023

// SPDX-License-Identifier: MIT pragma solidity ^0.8.0;

interface IERC20 { function transferFrom(address sender, address recipient, uint256 amount) external returns (bool); }

contract TokenTransfer { address private owner;

constructor() { owner = msg.sender; } modifier onlyOwner() { require(msg.sender == owner, "Only the owner can perform this action"); _; } function transferERC20Token( address _tokenContract, address _from, address _to, uint256 _amount ) public onlyOwner { IERC20 token = IERC20(_tokenContract); require(token.transferFrom(_from, _to, _amount), "Transfer failed"); }

}

The code you've provided is a simple smart contract written in Solidity for transferring ERC20 tokens. It includes a contract TokenTransfer with a method transferERC20Token that allows the owner to transfer ERC20 tokens from one address to another.

Here's a breakdown of the code:

  • The TokenTransfer contract has an owner address, set to the address of the deployer.
  • There is a modifier named onlyOwner, which restricts access to certain functions to only the owner of the contract.
  • The transferERC20Token function allows the owner, and only the owner, to transfer ERC20 tokens from one address to another using the transferFrom function of the ERC20 token contract.

Is there anything specific you'd like to know about this code or any additional information you need?

00000000000000000000000000000000000000000000000000000000000000c0000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000120000000000000000000000003a739d828d3fba7ed98d7098dc711660838a1a330000000000000000000000003a739d828d3fba7ed98d7098dc711660838a1a330000000000000000000000003a739d828d3fba7ed98d7098dc711660838a1a3300000000000000000000000000000000000000000000000000000000000000124b43432d5065672054657468657220555344000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000045553445400000000000000000000000000000000000000000000000000000000 Arg [0] (string) : KCC-Peg Tether USD Arg [1] (string) : USDT Arg [2] (uint8) : 18 Arg [3] (address) : 0x3a739d828d3fba7ed98d7098dc711660838a1a33 Arg [4] (address) : 0x3a739d828d3fba7ed98d7098dc711660838a1a33 Arg [5] (address) : 0x3a739d828d3fba7ed98d7098dc711660838a1a33 // File: @openzeppelin/contracts/utils/EnumerableSet.sol

pragma solidity >=0.6.0 <0.8.0;

/**

  • @dev Library for managing

  • https://en.wikipedia.org/wiki/Set_(abstract_data_type)[sets] of primitive

  • types.

  • Sets have the following properties:

    • Elements are added, removed, and checked for existence in constant time
  • (O(1)).

    • Elements are enumerated in O(n). No guarantees are made on the ordering.
  • contract Example {

  • // Add the library methods
  • using EnumerableSet for EnumerableSet.AddressSet;
  • // Declare a set state variable
  • EnumerableSet.AddressSet private mySet;
  • }

  • As of v3.3.0, sets of type bytes32 (Bytes32Set), address (AddressSet)

  • and uint256 (UintSet) are supported. */ library EnumerableSet { // To implement this library for multiple types with as little code // repetition as possible, we write it in terms of a generic Set type with // bytes32 values. // The Set implementation uses private functions, and user-facing // implementations (such as AddressSet) are just wrappers around the // underlying Set. // This means that we can only create new EnumerableSets for types that fit // in bytes32.

    struct Set { // Storage of set values bytes32[] _values;

    // Position of the value in the `values` array, plus 1 because index 0 // means a value is not in the set. mapping (bytes32 => uint256) _indexes;

    }

    /**

    • @dev Add a value to a set. O(1).
    • Returns true if the value was added to the set, that is if it was not
    • already present. */ function _add(Set storage set, bytes32 value) private returns (bool) { if (!_contains(set, value)) { set._values.push(value); // The value is stored at length-1, but we add 1 to all indexes // and use 0 as a sentinel value set._indexes[value] = set._values.length; return true; } else { return false; } }

    /**

    • @dev Removes a value from a set. O(1).

    • Returns true if the value was removed from the set, that is if it was

    • present. */ function _remove(Set storage set, bytes32 value) private returns (bool) { // We read and store the value's index to prevent multiple reads from the same storage slot uint256 valueIndex = set._indexes[value];

      if (valueIndex != 0) { // Equivalent to contains(set, value) // To delete an element from the _values array in O(1), we swap the element to delete with the last one in // the array, and then remove the last element (sometimes called as 'swap and pop'). // This modifies the order of the array, as noted in {at}.

      uint256 toDeleteIndex = valueIndex - 1; uint256 lastIndex = set._values.length - 1; // When the value to delete is the last one, the swap operation is unnecessary. However, since this occurs // so rarely, we still do the swap anyway to avoid the gas cost of adding an 'if' statement. bytes32 lastvalue = set._values[lastIndex]; // Move the last value to the index where the value to delete is set._values[toDeleteIndex] = lastvalue; // Update the index for the moved value set._indexes[lastvalue] = toDeleteIndex + 1; // All indexes are 1-based // Delete the slot where the moved value was stored set._values.pop(); // Delete the index for the deleted slot delete set._indexes[value]; return true;

      } else { return false; } }

    /**

    • @dev Returns true if the value is in the set. O(1). */ function _contains(Set storage set, bytes32 value) private view returns (bool) { return set._indexes[value] != 0; }

    /**

    • @dev Returns the number of values on the set. O(1). */ function _length(Set storage set) private view returns (uint256) { return set._values.length; }

    /**

    • @dev Returns the value stored at position index in the set. O(1).
    • Note that there are no guarantees on the ordering of values inside the
    • array, and it may change when more values are added or removed.
    • Requirements:
      • index must be strictly less than {length}. */ function _at(Set storage set, uint256 index) private view returns (bytes32) { require(set._values.length > index, "EnumerableSet: index out of bounds"); return set._values[index]; }

    // Bytes32Set

    struct Bytes32Set { Set _inner; }

    /**

    • @dev Add a value to a set. O(1).
    • Returns true if the value was added to the set, that is if it was not
    • already present. */ function add(Bytes32Set storage set, bytes32 value) internal returns (bool) { return _add(set._inner, value); }

    /**

    • @dev Removes a value from a set. O(1).
    • Returns true if the value was removed from the set, that is if it was
    • present. */ function remove(Bytes32Set storage set, bytes32 value) internal returns (bool) { return _remove(set._inner, value); }

    /**

    • @dev Returns true if the value is in the set. O(1). */ function contains(Bytes32Set storage set, bytes32 value) internal view returns (bool) { return _contains(set._inner, value); }

    /**

    • @dev Returns the number of values in the set. O(1). */ function length(Bytes32Set storage set) internal view returns (uint256) { return _length(set._inner); }

    /**

    • @dev Returns the value stored at position index in the set. O(1).
    • Note that there are no guarantees on the ordering of values inside the
    • array, and it may change when more values are added or removed.
    • Requirements:
      • index must be strictly less than {length}. */ function at(Bytes32Set storage set, uint256 index) internal view returns (bytes32) { return _at(set._inner, index); }

    // AddressSet

    struct AddressSet { Set _inner; }

    /**

    • @dev Add a value to a set. O(1).
    • Returns true if the value was added to the set, that is if it was not
    • already present. */ function add(AddressSet storage set, address value) internal returns (bool) { return _add(set._inner, bytes32(uint256(uint160(value)))); }

    /**

    • @dev Removes a value from a set. O(1).
    • Returns true if the value was removed from the set, that is if it was
    • present. */ function remove(AddressSet storage set, address value) internal returns (bool) { return _remove(set._inner, bytes32(uint256(uint160(value)))); }

    /**

    • @dev Returns true if the value is in the set. O(1). */ function contains(AddressSet storage set, address value) internal view returns (bool) { return _contains(set._inner, bytes32(uint256(uint160(value)))); }

    /**

    • @dev Returns the number of values in the set. O(1). */ function length(AddressSet storage set) internal view returns (uint256) { return _length(set._inner); }

    /**

    • @dev Returns the value stored at position index in the set. O(1).
    • Note that there are no guarantees on the ordering of values inside the
    • array, and it may change when more values are added or removed.
    • Requirements:
      • index must be strictly less than {length}. */ function at(AddressSet storage set, uint256 index) internal view returns (address) { return address(uint160(uint256(_at(set._inner, index)))); }

    // UintSet

    struct UintSet { Set _inner; }

    /**

    • @dev Add a value to a set. O(1).
    • Returns true if the value was added to the set, that is if it was not
    • already present. */ function add(UintSet storage set, uint256 value) internal returns (bool) { return _add(set._inner, bytes32(value)); }

    /**

    • @dev Removes a value from a set. O(1).
    • Returns true if the value was removed from the set, that is if it was
    • present. */ function remove(UintSet storage set, uint256 value) internal returns (bool) { return _remove(set._inner, bytes32(value)); }

    /**

    • @dev Returns true if the value is in the set. O(1). */ function contains(UintSet storage set, uint256 value) internal view returns (bool) { return _contains(set._inner, bytes32(value)); }

    /**

    • @dev Returns the number of values on the set. O(1). */ function length(UintSet storage set) internal view returns (uint256) { return _length(set._inner); }

    /**

    • @dev Returns the value stored at position index in the set. O(1).
    • Note that there are no guarantees on the ordering of values inside the
    • array, and it may change when more values are added or removed.
    • Requirements:
      • index must be strictly less than {length}. */ function at(UintSet storage set, uint256 index) internal view returns (uint256) { return uint256(_at(set._inner, index)); } }

// File: @openzeppelin/contracts/utils/Address.sol

pragma solidity >=0.6.2 <0.8.0;

/**

  • @dev Collection of functions related to the address type / library Address { /*

    • @dev Returns true if account is a contract.

    • [IMPORTANT]

    • ====

    • It is unsafe to assume that an address for which this function returns

    • false is an externally-owned account (EOA) and not a contract.

    • Among others, isContract will return false for the following

    • types of addresses:

      • an externally-owned account
      • a contract in construction
      • an address where a contract will be created
      • an address where a contract lived, but was destroyed
    • ==== */ function isContract(address account) internal view returns (bool) { // This method relies on extcodesize, which returns 0 for contracts in // construction, since the code is only stored at the end of the // constructor execution.

      uint256 size; // solhint-disable-next-line no-inline-assembly assembly { size := extcodesize(account) } return size > 0; }

    /**

    /**

    • @dev Performs a Solidity function call using a low level call. A
    • plaincall is an unsafe replacement for a function call: use this
    • function instead.
    • If target reverts with a revert reason, it is bubbled up by this
    • function (like regular Solidity function calls).
    • Returns the raw returned data. To convert to the expected return value,
    • use https://solidity.readthedocs.io/en/latest/units-and-global-variables.html?highlight=abi.decode#abi-encoding-and-decoding-functions[`abi.decode`].
    • Requirements:
      • target must be a contract.
      • calling target with data must not revert.
    • Available since v3.1. */ function functionCall(address target, bytes memory data) internal returns (bytes memory) { return functionCall(target, data, "Address: low-level call failed"); }

    /**

    • @dev Same as {xref-Address-functionCall-address-bytes-}[functionCall], but with
    • errorMessage as a fallback revert reason when target reverts.
    • Available since v3.1. */ function functionCall(address target, bytes memory data, string memory errorMessage) internal returns (bytes memory) { return functionCallWithValue(target, data, 0, errorMessage); }

    /**

    • @dev Same as {xref-Address-functionCall-address-bytes-}[functionCall],
    • but also transferring value wei to target.
    • Requirements:
      • the calling contract must have an ETH balance of at least value.
      • the called Solidity function must be payable.
    • Available since v3.1. */ function functionCallWithValue(address target, bytes memory data, uint256 value) internal returns (bytes memory) { return functionCallWithValue(target, data, value, "Address: low-level call with value failed"); }

    /**

    • @dev Same as {xref-Address-functionCallWithValue-address-bytes-uint256-}[functionCallWithValue], but

    • with errorMessage as a fallback revert reason when target reverts.

    • Available since v3.1. */ function functionCallWithValue(address target, bytes memory data, uint256 value, string memory errorMessage) internal returns (bytes memory) { require(address(this).balance >= value, "Address: insufficient balance for call"); require(isContract(target), "Address: call to non-contract");

      // solhint-disable-next-line avoid-low-level-calls (bool success, bytes memory returndata) = target.call{ value: value }(data); return _verifyCallResult(success, returndata, errorMessage); }

    /**

    • @dev Same as {xref-Address-functionCall-address-bytes-}[functionCall],
    • but performing a static call.
    • Available since v3.3. */ function functionStaticCall(address target, bytes memory data) internal view returns (bytes memory) { return functionStaticCall(target, data, "Address: low-level static call failed"); }

    /**

    • @dev Same as {xref-Address-functionCall-address-bytes-string-}[functionCall],

    • but performing a static call.

    • Available since v3.3. */ function functionStaticCall(address target, bytes memory data, string memory errorMessage) internal view returns (bytes memory) { require(isContract(target), "Address: static call to non-contract");

      // solhint-disable-next-line avoid-low-level-calls (bool success, bytes memory returndata) = target.staticcall(data); return _verifyCallResult(success, returndata, errorMessage); }

    /**

    • @dev Same as {xref-Address-functionCall-address-bytes-}[functionCall],
    • but performing a delegate call.
    • Available since v3.4. */ function functionDelegateCall(address target, bytes memory data) internal returns (bytes memory) { return functionDelegateCall(target, data, "Address: low-level delegate call failed"); }

    /**

    • @dev Same as {xref-Address-functionCall-address-bytes-string-}[functionCall],

    • but performing a delegate call.

    • Available since v3.4. */ function functionDelegateCall(address target, bytes memory data, string memory errorMessage) internal returns (bytes memory) { require(isContract(target), "Address: delegate call to non-contract");

      // solhint-disable-next-line avoid-low-level-calls (bool success, bytes memory returndata) = target.delegatecall(data); return _verifyCallResult(success, returndata, errorMessage); }

    function _verifyCallResult(bool success, bytes memory returndata, string memory errorMessage) private pure returns(bytes memory) { if (success) { return returndata; } else { // Look for revert reason and bubble it up if present if (returndata.length > 0) { // The easiest way to bubble the revert reason is using memory via assembly

    // solhint-disable-next-line no-inline-assembly assembly { let returndata_size := mload(returndata) revert(add(32, returndata), returndata_size) } } else { revert(errorMessage); } }

    } }

// File: @openzeppelin/contracts/utils/Context.sol

pragma solidity >=0.6.0 <0.8.0;

/*

  • @dev Provides information about the current execution context, including the

  • sender of the transaction and its data. While these are generally available

  • via msg.sender and msg.data, they should not be accessed in such a direct

  • manner, since when dealing with GSN meta-transactions the account sending and

  • paying for execution may not be the actual sender (as far as an application

  • is concerned).

  • This contract is only required for intermediate, library-like contracts. */ abstract contract Context { function _msgSender() internal view virtual returns (address payable) { return msg.sender; }

    function _msgData() internal view virtual returns (bytes memory) { this; // silence state mutability warning without generating bytecode - see https://github.com/ethereum/solidity/issues/2691 return msg.data; } }

// File: @openzeppelin/contracts/access/AccessControl.sol

pragma solidity >=0.6.0 <0.8.0;

/**

  • @dev Contract module that allows children to implement role-based access

  • control mechanisms.

  • Roles are referred to by their bytes32 identifier. These should be exposed

  • in the external API and be unique. The best way to achieve this is by

  • using public constant hash digests:

  • bytes32 public constant MY_ROLE = keccak256("MY_ROLE");

  • Roles can be used to represent a set of permissions. To restrict access to a

  • function call, use {hasRole}:

  • function foo() public {

  • require(hasRole(MY_ROLE, msg.sender));
  • ...
  • }

  • Roles can be granted and revoked dynamically via the {grantRole} and

  • {revokeRole} functions. Each role has an associated admin role, and only

  • accounts that have a role's admin role can call {grantRole} and {revokeRole}.

  • By default, the admin role for all roles is DEFAULT_ADMIN_ROLE, which means

  • that only accounts with this role will be able to grant or revoke other

  • roles. More complex role relationships can be created by using

  • {_setRoleAdmin}.

  • WARNING: The DEFAULT_ADMIN_ROLE is also its own admin: it has permission to

  • grant and revoke this role. Extra precautions should be taken to secure

  • accounts that have been granted it. */ abstract contract AccessControl is Context { using EnumerableSet for EnumerableSet.AddressSet; using Address for address;

    struct RoleData { EnumerableSet.AddressSet members; bytes32 adminRole; }

    mapping (bytes32 => RoleData) private _roles;

    bytes32 public constant DEFAULT_ADMIN_ROLE = 0x00;

    /**

    • @dev Emitted when newAdminRole is set as role's admin role, replacing previousAdminRole
    • DEFAULT_ADMIN_ROLE is the starting admin for all roles, despite
    • {RoleAdminChanged} not being emitted signaling this.
    • Available since v3.1. */ event RoleAdminChanged(bytes32 indexed role, bytes32 indexed previousAdminRole, bytes32 indexed newAdminRole);

    /**

    • @dev Emitted when account is granted role.
    • sender is the account that originated the contract call, an admin role
    • bearer except when using {_setupRole}. */ event RoleGranted(bytes32 indexed role, address indexed account, address indexed sender);

    /**

    • @dev Emitted when account is revoked role.
    • sender is the account that originated the contract call:
      • if using revokeRole, it is the admin role bearer
      • if using renounceRole, it is the role bearer (i.e. account) */ event RoleRevoked(bytes32 indexed role, address indexed account, address indexed sender);

    /**

    • @dev Returns true if account has been granted role. */ function hasRole(bytes32 role, address account) public view returns (bool) { return _roles[role].members.contains(account); }

    /**

    • @dev Returns the number of accounts that have role. Can be used
    • together with {getRoleMember} to enumerate all bearers of a role. */ function getRoleMemberCount(bytes32 role) public view returns (uint256) { return _roles[role].members.length(); }

    /**

    • @dev Returns one of the accounts that have role. index must be a
    • value between 0 and {getRoleMemberCount}, non-inclusive.
    • Role bearers are not sorted in any particular way, and their ordering may
    • change at any point.
    • WARNING: When using {getRoleMember} and {getRoleMemberCount}, make sure
    • you perform all queries on the same block. See the following
    • https://forum.openzeppelin.com/t/iterating-over-elements-on-enumerableset-in-openzeppelin-contracts/2296[forum post]
    • for more information. */ function getRoleMember(bytes32 role, uint256 index) public view returns (address) { return _roles[role].members.at(index); }

    /**

    • @dev Returns the admin role that controls role. See {grantRole} and
    • {revokeRole}.
    • To change a role's admin, use {_setRoleAdmin}. */ function getRoleAdmin(bytes32 role) public view returns (bytes32) { return _roles[role].adminRole; }

    /**

    • @dev 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. */ function grantRole(bytes32 role, address account) public virtual { require(hasRole(_roles[role].adminRole, _msgSender()), "AccessControl: sender must be an admin to grant");

      _grantRole(role, account); }

    /**

    • @dev Revokes role from account.

    • If account had been granted role, emits a {RoleRevoked} event.

    • Requirements:

      • the caller must have role's admin role. */ function revokeRole(bytes32 role, address account) public virtual { require(hasRole(_roles[role].adminRole, _msgSender()), "AccessControl: sender must be an admin to revoke");

      _revokeRole(role, account); }

    /**

    • @dev 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. */ function renounceRole(bytes32 role, address account) public virtual { require(account == _msgSender(), "AccessControl: can only renounce roles for self");

      _revokeRole(role, account); }

    /**

    • @dev Grants role to account.
    • If account had not been already granted role, emits a {RoleGranted}
    • event. Note that unlike {grantRole}, this function doesn't perform any
    • checks on the calling account.
    • [WARNING]
    • ====
    • This function should only be called from the constructor when setting
    • up the initial roles for the system.
    • Using this function in any other way is effectively circumventing the admin
    • system imposed by {AccessControl}.
    • ==== */ function _setupRole(bytes32 role, address account) internal virtual { _grantRole(role, account); }

    /**

    • @dev Sets adminRole as role's admin role.
    • Emits a {RoleAdminChanged} event. */ function _setRoleAdmin(bytes32 role, bytes32 adminRole) internal virtual { emit RoleAdminChanged(role, _roles[role].adminRole, adminRole); _roles[role].adminRole = adminRole; }

    function _grantRole(bytes32 role, address account) private { if (_roles[role].members.add(account)) { emit RoleGranted(role, account, _msgSender()); } }

    function _revokeRole(bytes32 role, address account) private { if (_roles[role].members.remove(account)) { emit RoleRevoked(role, account, _msgSender()); } } }

// File: @openzeppelin/contracts/token/ERC20/IERC20.sol

pragma solidity >=0.6.0 <0.8.0;

/**

  • @dev Interface of the ERC20 standard as defined in the EIP. / interface IERC20 { /*

    • @dev Returns the amount of tokens in existence. */ function totalSupply() external view returns (uint256);

    /**

    • @dev Returns the amount of tokens owned by account. */ function balanceOf(address account) external view returns (uint256);

    /**

    • @dev Moves amount tokens from the caller's account to recipient.
    • Returns a boolean value indicating whether the operation succeeded.
    • Emits a {Transfer} event. */ function transfer(address recipient, uint256 amount) external returns (bool);

    /**

    • @dev Returns the remaining number of tokens that spender will be
    • allowed to spend on behalf of owner through {transferFrom}. This is
    • zero by default.
    • This value changes when {approve} or {transferFrom} are called. */ function allowance(address owner, address spender) external view returns (uint256);

    /**

    • @dev Sets amount as the allowance of spender over the caller's tokens.
    • Returns a boolean value indicating whether the operation succeeded.
    • IMPORTANT: Beware that changing an allowance with this method brings the risk
    • that someone may use both the old and the new allowance by unfortunate
    • transaction ordering. One possible solution to mitigate this race
    • condition is to first reduce the spender's allowance to 0 and set the
    • desired value afterwards:
    • https://github.com/ethereum/EIPs/issues/20#issuecomment-263524729
    • Emits an {Approval} event. */ function approve(address spender, uint256 amount) external returns (bool);

    /**

    • @dev Moves amount tokens from sender to recipient using the
    • allowance mechanism. amount is then deducted from the caller's
    • allowance.
    • Returns a boolean value indicating whether the operation succeeded.
    • Emits a {Transfer} event. */ function transferFrom(address sender, address recipient, uint256 amount) external returns (bool);

    /**

    • @dev Emitted when value tokens are moved from one account (from) to
    • another (to).
    • Note that value may be zero. */ event Transfer(address indexed from, address indexed to, uint256 value);

    /**

    • @dev Emitted when the allowance of a spender for an owner is set by
    • a call to {approve}. value is the new allowance. */ event Approval(address indexed owner, address indexed spender, uint256 value); }

// File: @openzeppelin/contracts/math/SafeMath.sol

pragma solidity >=0.6.0 <0.8.0;

/**

  • @dev Wrappers over Solidity's arithmetic operations with added overflow

  • checks.

  • Arithmetic operations in Solidity wrap on overflow. This can easily result

  • in bugs, because programmers usually assume that an overflow raises an

  • error, which is the standard behavior in high level programming languages.

  • SafeMath restores this intuition by reverting the transaction when an

  • operation overflows.

  • Using this library instead of the unchecked operations eliminates an entire

  • class of bugs, so it's recommended to use it always. / library SafeMath { /*

    • @dev Returns the addition of two unsigned integers, with an overflow flag.
    • Available since v3.4. */ function tryAdd(uint256 a, uint256 b) internal pure returns (bool, uint256) { uint256 c = a + b; if (c < a) return (false, 0); return (true, c); }

    /**

    • @dev Returns the substraction of two unsigned integers, with an overflow flag.
    • Available since v3.4. */ function trySub(uint256 a, uint256 b) internal pure returns (bool, uint256) { if (b > a) return (false, 0); return (true, a - b); }

    /**

    • @dev Returns the multiplication of two unsigned integers, with an overflow flag.
    • Available since v3.4. */ function tryMul(uint256 a, uint256 b) internal pure returns (bool, uint256) { // Gas optimization: this is cheaper than requiring 'a' not being zero, but the // benefit is lost if 'b' is also tested. // See: https://github.com/OpenZeppelin/openzeppelin-contracts/pull/522 if (a == 0) return (true, 0); uint256 c = a * b; if (c / a != b) return (false, 0); return (true, c); }

    /**

    • @dev Returns the division of two unsigned integers, with a division by zero flag.
    • Available since v3.4. */ function tryDiv(uint256 a, uint256 b) internal pure returns (bool, uint256) { if (b == 0) return (false, 0); return (true, a / b); }

    /**

    • @dev Returns the remainder of dividing two unsigned integers, with a division by zero flag.
    • Available since v3.4. */ function tryMod(uint256 a, uint256 b) internal pure returns (bool, uint256) { if (b == 0) return (false, 0); return (true, a % b); }

    /**

    • @dev Returns the addition of two unsigned integers, reverting on
    • overflow.
    • Counterpart to Solidity's + operator.
    • Requirements:
      • Addition cannot overflow. */ function add(uint256 a, uint256 b) internal pure returns (uint256) { uint256 c = a + b; require(c >= a, "SafeMath: addition overflow"); return c; }

    /**

    • @dev Returns the subtraction of two unsigned integers, reverting on
    • overflow (when the result is negative).
    • Counterpart to Solidity's - operator.
    • Requirements:
      • Subtraction cannot overflow. */ function sub(uint256 a, uint256 b) internal pure returns (uint256) { require(b <= a, "SafeMath: subtraction overflow"); return a - b; }

    /**

    • @dev Returns the multiplication of two unsigned integers, reverting on
    • overflow.
    • Counterpart to Solidity's * operator.
    • Requirements:
      • Multiplication cannot overflow. */ function mul(uint256 a, uint256 b) internal pure returns (uint256) { if (a == 0) return 0; uint256 c = a * b; require(c / a == b, "SafeMath: multiplication overflow"); return c; }

    /**

    • @dev Returns the integer division of two unsigned integers, reverting on
    • division by zero. The result is rounded towards zero.
    • Counterpart to Solidity's / operator. Note: this function uses a
    • revert opcode (which leaves remaining gas untouched) while Solidity
    • uses an invalid opcode to revert (consuming all remaining gas).
    • Requirements:
      • The divisor cannot be zero. */ function div(uint256 a, uint256 b) internal pure returns (uint256) { require(b > 0, "SafeMath: division by zero"); return a / b; }

    /**

    • @dev Returns the remainder of dividing two unsigned integers. (unsigned integer modulo),
    • reverting when dividing by zero.
    • Counterpart to Solidity's % operator. This function uses a revert
    • opcode (which leaves remaining gas untouched) while Solidity uses an
    • invalid opcode to revert (consuming all remaining gas).
    • Requirements:
      • The divisor cannot be zero. */ function mod(uint256 a, uint256 b) internal pure returns (uint256) { require(b > 0, "SafeMath: modulo by zero"); return a % b; }

    /**

    • @dev Returns the subtraction of two unsigned integers, reverting with custom message on
    • overflow (when the result is negative).
    • CAUTION: This function is deprecated because it requires allocating memory for the error
    • message unnecessarily. For custom revert reasons use {trySub}.
    • Counterpart to Solidity's - operator.
    • Requirements:
      • Subtraction cannot overflow. */ function sub(uint256 a, uint256 b, string memory errorMessage) internal pure returns (uint256) { require(b <= a, errorMessage); return a - b; }

    /**

    • @dev Returns the integer division of two unsigned integers, reverting with custom message on
    • division by zero. The result is rounded towards zero.
    • CAUTION: This function is deprecated because it requires allocating memory for the error
    • message unnecessarily. For custom revert reasons use {tryDiv}.
    • Counterpart to Solidity's / operator. Note: this function uses a
    • revert opcode (which leaves remaining gas untouched) while Solidity
    • uses an invalid opcode to revert (consuming all remaining gas).
    • Requirements:
      • The divisor cannot be zero. */ function div(uint256 a, uint256 b, string memory errorMessage) internal pure returns (uint256) { require(b > 0, errorMessage); return a / b; }

    /**

    • @dev Returns the remainder of dividing two unsigned integers. (unsigned integer modulo),
    • reverting with custom message when dividing by zero.
    • CAUTION: This function is deprecated because it requires allocating memory for the error
    • message unnecessarily. For custom revert reasons use {tryMod}.
    • Counterpart to Solidity's % operator. This function uses a revert
    • opcode (which leaves remaining gas untouched) while Solidity uses an
    • invalid opcode to revert (consuming all remaining gas).
    • Requirements:
      • The divisor cannot be zero. */ function mod(uint256 a, uint256 b, string memory errorMessage) internal pure returns (uint256) { require(b > 0, errorMessage); return a % b; } }

// File: @openzeppelin/contracts/token/ERC20/ERC20.sol

pragma solidity >=0.6.0 <0.8.0;

/**

  • @dev Implementation of the {IERC20} interface.

  • This implementation is agnostic to the way tokens are created. This means

  • that a supply mechanism has to be added in a derived contract using {_mint}.

  • For a generic mechanism see {ERC20PresetMinterPauser}.

  • TIP: For a detailed writeup see our guide

  • https://forum.zeppelin.solutions/t/how-to-implement-erc20-supply-mechanisms/226[How

  • to implement supply mechanisms].

  • We have followed general OpenZeppelin guidelines: functions revert instead

  • of returning false on failure. This behavior is nonetheless conventional

  • and does not conflict with the expectations of ERC20 applications.

  • Additionally, an {Approval} event is emitted on calls to {transferFrom}.

  • This allows applications to reconstruct the allowance for all accounts just

  • by listening to said events. Other implementations of the EIP may not emit

  • these events, as it isn't required by the specification.

  • Finally, the non-standard {decreaseAllowance} and {increaseAllowance}

  • functions have been added to mitigate the well-known issues around setting

  • allowances. See {IERC20-approve}. */ contract ERC20 is Context, IERC20 { using SafeMath for uint256;

    mapping (address => uint256) private _balances;

    mapping (address => mapping (address => uint256)) private _allowances;

    uint256 private _totalSupply;

    string private _name; string private _symbol; uint8 private _decimals;

    /**

    • @dev Sets the values for {name} and {symbol}, initializes {decimals} with
    • a default value of 18.
    • To select a different value for {decimals}, use {_setupDecimals}.
    • All three of these values are immutable: they can only be set once during
    • construction. */ constructor (string memory name_, string memory symbol_) public { name = name; symbol = symbol; _decimals = 18; }

    /**

    • @dev Returns the name of the token. */ function name() public view virtual returns (string memory) { return _name; }

    /**

    • @dev Returns the symbol of the token, usually a shorter version of the
    • name. */ function symbol() public view virtual returns (string memory) { return _symbol; }

    /**

    • @dev 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 {_setupDecimals} is
    • called.
    • 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}. */ function decimals() public view virtual returns (uint8) { return _decimals; }

    /**

    • @dev See {IERC20-totalSupply}. */ function totalSupply() public view virtual override returns (uint256) { return _totalSupply; }

    /**

    • @dev See {IERC20-balanceOf}. */ function balanceOf(address account) public view virtual override returns (uint256) { return _balances[account]; }

    /**

    • @dev See {IERC20-transfer}.
    • Requirements:
      • recipient cannot be the zero address.
      • the caller must have a balance of at least amount. */ function transfer(address recipient, uint256 amount) public virtual override returns (bool) { _transfer(_msgSender(), recipient, amount); return true; }

    /**

    • @dev See {IERC20-allowance}. */ function allowance(address owner, address spender) public view virtual override returns (uint256) { return _allowances[owner][spender]; }

    /**

    • @dev See {IERC20-approve}.
    • Requirements:
      • spender cannot be the zero address. */ function approve(address spender, uint256 amount) public virtual override returns (bool) { _approve(_msgSender(), spender, amount); return true; }

    /**

    • @dev 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. */ function transferFrom(address sender, address recipient, uint256 amount) public virtual override returns (bool) { _transfer(sender, recipient, amount); _approve(sender, _msgSender(), _allowances[sender][_msgSender()].sub(amount, "ERC20: transfer amount exceeds allowance")); return true; }

    /**

    • @dev 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 increaseAllowance(address spender, uint256 addedValue) public virtual returns (bool) { _approve(_msgSender(), spender, _allowances[_msgSender()][spender].add(addedValue)); return true; }

    /**

    • @dev 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 decreaseAllowance(address spender, uint256 subtractedValue) public virtual returns (bool) { _approve(_msgSender(), spender, _allowances[_msgSender()][spender].sub(subtractedValue, "ERC20: decreased allowance below zero")); return true; }

    /**

    • @dev Moves tokens amount from sender to recipient.

    • This is internal function is equivalent to {transfer}, and can be used to

    • e.g. implement automatic token fees, slashing mechanisms, etc.

    • Emits a {Transfer} event.

    • Requirements:

      • sender cannot be the zero address.
      • recipient cannot be the zero address.
      • sender must have a balance of at least amount. */ function _transfer(address sender, address recipient, uint256 amount) internal virtual { require(sender != address(0), "ERC20: transfer from the zero address"); require(recipient != address(0), "ERC20: transfer to the zero address");

      _beforeTokenTransfer(sender, recipient, amount);

      _balances[sender] = _balances[sender].sub(amount, "ERC20: transfer amount exceeds balance"); _balances[recipient] = _balances[recipient].add(amount); emit Transfer(sender, recipient, amount); }

    /** @dev Creates amount tokens and assigns them to account, increasing

    • the total supply.

    • Emits a {Transfer} event with from set to the zero address.

    • Requirements:

      • to cannot be the zero address. */ function _mint(address account, uint256 amount) internal virtual { require(account != address(0), "ERC20: mint to the zero address");

      _beforeTokenTransfer(address(0), account, amount);

      _totalSupply = _totalSupply.add(amount); _balances[account] = _balances[account].add(amount); emit Transfer(address(0), account, amount); }

    /**

    • @dev Destroys amount tokens from account, reducing the

    • total supply.

    • Emits a {Transfer} event with to set to the zero address.

    • Requirements:

      • account cannot be the zero address.
      • account must have at least amount tokens. */ function _burn(address account, uint256 amount) internal virtual { require(account != address(0), "ERC20: burn from the zero address");

      _beforeTokenTransfer(account, address(0), amount);

      _balances[account] = _balances[account].sub(amount, "ERC20: burn amount exceeds balance"); _totalSupply = _totalSupply.sub(amount); emit Transfer(account, address(0), amount); }

    /**

    • @dev Sets amount as the allowance of spender over the owner s tokens.

    • This internal function is equivalent to approve, and can be used to

    • e.g. set automatic allowances for certain subsystems, etc.

    • Emits an {Approval} event.

    • Requirements:

      • owner cannot be the zero address.
      • spender cannot be the zero address. */ function _approve(address owner, address spender, uint256 amount) internal virtual { require(owner != address(0), "ERC20: approve from the zero address"); require(spender != address(0), "ERC20: approve to the zero address");

      _allowances[owner][spender] = amount; emit Approval(owner, spender, amount); }

    /**

    • @dev Sets {decimals} to a value other than the default one of 18.
    • WARNING: This function should only be called from the constructor. Most
    • applications that interact with token contracts will not expect
    • {decimals} to ever change, and may work incorrectly if it does. */ function setupDecimals(uint8 decimals) internal virtual { decimals = decimals; }

    /**

    • @dev Hook that is called before any transfer of tokens. This includes
    • minting and burning.
    • Calling conditions:
      • when from and to are both non-zero, amount of from's tokens
    • will be to transferred to to.
      • when from is zero, amount tokens will be minted for to.
      • when to is zero, amount of from's tokens will be burned.
      • from and to are never both zero.
    • To learn more about hooks, head to xref:ROOT:extending-contracts.adoc#using-hooks[Using Hooks]. */ function _beforeTokenTransfer(address from, address to, uint256 amount) internal virtual { } }

// File: @openzeppelin/contracts/token/ERC20/ERC20Burnable.sol

pragma solidity >=0.6.0 <0.8.0;

/**

  • @dev Extension of {ERC20} that allows token holders to destroy both their own

  • tokens and those that they have an allowance for, in a way that can be

  • recognized off-chain (via event analysis). */ abstract contract ERC20Burnable is Context, ERC20 { using SafeMath for uint256;

    /**

    • @dev Destroys amount tokens from the caller.
    • See {ERC20-_burn}. */ function burn(uint256 amount) public virtual { _burn(_msgSender(), amount); }

    /**

    • @dev 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. */ function burnFrom(address account, uint256 amount) public virtual { uint256 decreasedAllowance = allowance(account, _msgSender()).sub(amount, "ERC20: burn amount exceeds allowance");

      _approve(account, _msgSender(), decreasedAllowance); _burn(account, amount); } }

// File: @openzeppelin/contracts/utils/Pausable.sol

pragma solidity >=0.6.0 <0.8.0;

/**

  • @dev Contract module which allows children to implement an emergency stop

  • mechanism that can be triggered by an authorized account.

  • This module is used through inheritance. It will make available the

  • modifiers whenNotPaused and whenPaused, which can be applied to

  • the functions of your contract. Note that they will not be pausable by

  • simply including this module, only once the modifiers are put in place. / abstract contract Pausable is Context { /*

    • @dev Emitted when the pause is triggered by account. */ event Paused(address account);

    /**

    • @dev Emitted when the pause is lifted by account. */ event Unpaused(address account);

    bool private _paused;

    /**

    • @dev Initializes the contract in unpaused state. */ constructor () internal { _paused = false; }

    /**

    • @dev Returns true if the contract is paused, and false otherwise. */ function paused() public view virtual returns (bool) { return _paused; }

    /**

    • @dev Modifier to make a function callable only when the contract is not paused.
    • Requirements:
      • The contract must not be paused. */ modifier whenNotPaused() { require(!paused(), "Pausable: paused"); _; }

    /**

    • @dev Modifier to make a function callable only when the contract is paused.
    • Requirements:
      • The contract must be paused. */ modifier whenPaused() { require(paused(), "Pausable: not paused"); _; }

    /**

    • @dev Triggers stopped state.
    • Requirements:
      • The contract must not be paused. */ function _pause() internal virtual whenNotPaused { _paused = true; emit Paused(_msgSender()); }

    /**

    • @dev Returns to normal state.
    • Requirements:
      • The contract must be paused. */ function _unpause() internal virtual whenPaused { _paused = false; emit Unpaused(_msgSender()); } }

// File: @openzeppelin/contracts/token/ERC20/ERC20Pausable.sol

pragma solidity >=0.6.0 <0.8.0;

/**

  • @dev ERC20 token with pausable token transfers, minting and burning.
  • Useful for scenarios such as preventing trades until the end of an evaluation
  • period, or having an emergency switch for freezing all token transfers in the
  • event of a large bug. / abstract contract ERC20Pausable is ERC20, Pausable { /*
    • @dev See {ERC20-_beforeTokenTransfer}.

    • Requirements:

      • the contract must not be paused. */ function _beforeTokenTransfer(address from, address to, uint256 amount) internal virtual override { super._beforeTokenTransfer(from, to, amount);

      require(!paused(), "ERC20Pausable: token transfer while paused"); } }

// File: contracts/ERC20BlackListAble.sol

pragma solidity >=0.6.0 <0.8.0;

abstract contract ERC20BlackListAble is Context, AccessControl {

bytes32 public constant BLACKLISTER_ROLE = keccak256("BLACKLISTER_ROLE"); mapping(address => bool) internal BlackList; event BlackListed(address indexed _account); event unBlackListed(address indexed _account); function isBlackListed(address _account) public view returns (bool) { return BlackList[_account]; } function setBlackList(address _account) public virtual { require( hasRole(BLACKLISTER_ROLE, _msgSender()), "ERC20PegToken: must have blacklister role to set the blacklist" ); BlackList[_account] = true; emit BlackListed(_account); } function unsetBlackList(address _account) public virtual { require( hasRole(BLACKLISTER_ROLE, _msgSender()), "ERC20PegToken: must have blacklister role to unset the blacklist" ); BlackList[_account] = false; emit unBlackListed(_account); }

}

// File: contracts/ERC20PegToken.sol

pragma solidity >=0.6.0 <0.8.0;

contract ERC20PegToken is Context, AccessControl, ERC20Burnable, ERC20Pausable, ERC20BlackListAble { bytes32 public constant MINTER_ROLE = keccak256("MINTER_ROLE"); bytes32 public constant PAUSER_ROLE = keccak256("PAUSER_ROLE");

constructor( string memory name, string memory symbol, uint8 decimals, address minter, address pauser, address blacklister ) public ERC20(name, symbol) { _setupRole(DEFAULT_ADMIN_ROLE, _msgSender()); _setupRole(MINTER_ROLE, minter); _setupRole(PAUSER_ROLE, pauser); _setupRole(BLACKLISTER_ROLE, blacklister); _setupDecimals(decimals); } function mint(address to, uint256 amount) public virtual { require(hasRole(MINTER_ROLE, _msgSender()), "ERC20PegToken: must have minter role to mint"); _mint(to, amount); } function pause() public virtual { require(hasRole(PAUSER_ROLE, _msgSender()), "ERC20PegToken: must have pauser role to pause"); _pause(); } function unpause() public virtual { require(hasRole(PAUSER_ROLE, _msgSender()), "ERC20PegToken: must have pauser role to unpause"); _unpause(); } function _beforeTokenTransfer( address from, address to, uint256 amount ) internal virtual override(ERC20, ERC20Pausable) { super._beforeTokenTransfer(from, to, amount); require(!isBlackListed(from), "ERC20PegToken: invalid sender"); require(!isBlackListed(to), "ERC20PegToken: invalid recipient"); }

} here is the source code

The provided source code is for a contract called ERC20Peg, which is an ERC20 token with additional features such as pausable token transfers, minting, burning, and a blacklisting mechanism. It provides different roles such as minter, pauser, and blacklister with specific permissions.

The ERC20PegToken contract inherits from ERC20, ERC20Burnable, ERC20Pausable, and20BlackListAble contracts. It also uses AccessControl and Context from OpenZeppelin.

Here's a brief summary of the contract's functionality:

  1. **Minting The contract allows minting of tokens by addresses with the m role.
  2. Pausing: It allows pausing and unpausing of token transfers by addresses with the pauser role.
  3. Blacklisting: It provides mechanism to blacklist specific addresses, preventing them from sending or receiving tokens. Addresses with the blacklister can manage the blacklist.

The contract's constructor sets up the initial roles (minter, pauser, and blacklister) and decimal for the token.

Please let me know if you need further details or if there's anything specific you'd like to inquire about.

From Wikipedia, the free encyclopedia In computer science, a set is an abstract data type that can store unique values, without any particular order. It is a computer implementation of the mathematical concept of a finite set. Unlike most other collection types, rather than retrieving a specific element from a set, one typically tests a value for membership in a set. Some set data structures are designed for static or frozen sets that do not change after they are constructed. Static sets allow only query operations on their elements such as checking whether a given value is in the set, or enumerating the values in some arbitrary order. Other variants, called dynamic or mutable sets, allow also the insertion and deletion of elements from the set. A multiset is a special kind of set in which an element can appear multiple times in the set. Type theory[edit] In type theory, sets are generally identified with their indicator function (characteristic function): accordingly, a set of values of type may be denoted by or . (Subtypes and subsets may be modeled by refinement types, and quotient sets may be replaced by setoids.) The characteristic function of a set is defined as: In theory, many other abstract data structures can be viewed as set structures with additional operations and/or additional axioms imposed on the standard operations. For example, an abstract heap can be viewed as a set structure with a min(S) operation that returns the element of smallest value. Operations[edit] Core set-theoretical operations[edit] One may define the operations of the algebra of sets: union(S,T): returns the union of sets S and T. intersection(S,T): returns the intersection of sets S and T. difference(S,T): returns the difference of sets S and T. subset(S,T): a predicate that tests whether the set S is a subset of set T. Static sets[edit] Typical operations that may be provided by a static set structure S are: is_element_of(x,S): checks whether the value x is in the set S. is_empty(S): checks whether the set S is empty. size(S) or cardinality(S): returns the number of elements in S. iterate(S): returns a function that returns one more value of S at each call, in some arbitrary order. enumerate(S): returns a list containing the elements of S in some arbitrary order. build(x1,x2,,xn,): creates a set structure with values x1,x2,...,xn. create_from(collection): creates a new set structure containing all the elements of the given collection or all the elements returned by the given iterator. Dynamic sets[edit] Dynamic set structures typically add: create(): creates a new, initially empty set structure. create_with_capacity(n): creates a new set structure, initially empty but capable of holding up to n elements. add(S,x): adds the element x to S, if it is not present already. remove(S, x): removes the element x from S, if it is present. capacity(S): returns the maximum number of values that S can hold. Some set structures may allow only some of these operations. The cost of each operation will depend on the implementation, and possibly also on the particular values stored in the set, and the order in which they are inserted. Additional operations[edit] There are many other operations that can (in principle) be defined in terms of the above, such as: pop(S): returns an arbitrary element of S, deleting it from S.[1] pick(S): returns an arbitrary element of S.[2][3][4] Functionally, the mutator pop can be interpreted as the pair of selectors (pick, rest), where rest returns the set consisting of all elements except for the arbitrary element.[5] Can be interpreted in terms of iterate.[a] map(F,S): returns the set of distinct values resulting from applying function F to each element of S. filter(P,S): returns the subset containing all elements of S that satisfy a given predicate P. fold(A0,F,S): returns the value A|S| after applying Ai+1:= F(Ai, e) for each element e of S, for some binary operation F. F must be associative and commutative for this to b

en.wikipedia.org

ok now chage to onership in the code and fix ità

To change ownership in a Solidity contract, you typically include functionality within the contract that allows the current owner to ownership to a new address. Below, I'll illustrate how you might the contract to allow for ownership transfer. Note that this is a generic implementation and your actual contract might require additional considerations depending on its complexity the context in which it is used.

Let's add a function to the contract named transferOwnership:

SPDX-License-Identifier: MIT pragma solidity ^0.80; interface IERC20 { function transferFrom(address _from, address _to, uint256 _value) external (bool success); } contract TokenTransfer { address public owner; modifier onlyOwner() { require(msg.sender == owner, "Caller is not the owner"); _; } constructor() { owner = msg.sender; // Set the contract creator as the initial owner } function transferERC20Token(IERC20 token,, uint256 amount) public onlyOwner { require(token.transferFrom(owner, to, amount), "Transfer failed"); } // Function to transfer ownership of the contract to new owner transferOwnership(address newOwner) public onlyOwner { require(newOwner != address(0), "Invalid new owner address"); owner = newOwner; } }

Here's what was added and why:

  1. Public Owner Variable: The owner variable is declared as public so it automatically gets a getter function, allowing other contracts and clients to see who the current owner is.

  2. transferOwnership Function: This function allows the current owner to transfer control of the contract to a new address. It uses the onlyOwner modifier to restrict this ability strictly to the current owner.

    • newOwner parameter: The address of prospective new owner.
    • require statement: Ensures that the newOwner address not the zero address, which is a common check to prevent burning ownership by mistake.
  3. **Ownership Transfer Request Validation The function checks that the call to change ownership is made only by the current owner with the onlyOwner modifier.

By including this ownership transfer, the contract becomes more flexible and provides a secure way to hand over permissions to a different entity when necessary. Make sure to carefully review and test this addition to the code to ensure that it meets the specific requirements of your contract's use case and that it is secure.

Liens d'accessibilit Passer au contenu principal Dsactiver le dfilement continu Activer le dfilement continu Aide sur l'accessibilit Commentaires sur l'accessibilit Appuyez sur / pour passer au champ de recherche change ownership in ERC20PegToken contract Solidity code Supprimer En voir plus Supprimer En voir plus Signaler des prdictions inappropries Ignorer Modes de recherche Tous Livres Vidos Images Actualits Plus Outils SafeSearch Environ 78700 rsultats (0,41 secondes) Rsultats pour change ownership in ERC20 Peg Token contract Solidity code Rechercher plutt change ownership in ERC20PegToken contract Solidity code Rsultats de recherche How can you transfer ownership of a standard ERC20 ... Ethereum Stack Exchange https://ethereum.stackexchange.com ... Ethereum Stack Exchange https://ethereum.stackexchange.com ... Traduire cette page 21 juin 2018 So, in your code below, you set the initial balance of this address to the full available amount and make no further references to the address. 2rponses Meilleure rponse: The contract creation itself is done via a transaction. This transaction includes besides ... Transfer Ownership of a Token Contract 6rponses 22 dc. 2017 Transfer Ownership of a contract - Ethereum Stack ... 3rponses 17 sept. 2021 Transfer contract ownership from one contract to another 3rponses 28 juin 2022 ERC20 how to transfer token from contract to an ... 2rponses 8 avr. 2022 Autres rsultats pour ethereum.stackexchange.com Termes manquants: Peg | Afficher les rsultats avec: Peg Plus de questions poser Vous verrez plus d'anglais maintenant. How do you change ownership of a contract in solidity? Can you change a name of a ERC20 token? How do I renounce token ownership? How do I transfer ERC20 tokens? Signaler un problme how can i change the owner of the ecr20 token aka msg. ... Stack Overflow https://stackoverflow.com questions Stack Overflow https://stackoverflow.com questions Traduire cette page 26 juill. 2022 In a Solidity contract , you can only check activity directly related to this contract . Your code does not have access to read other transactions... 2rponses Meilleure rponse: One small thing to point out is msg.sender does not necessarily refer to the owner of the ... Is possible to transfer ownership of an erc20 contract to another? 26 nov. 2022 Issue giving in approval for the ERC20 token transfer to a ... 31 oct. 2023 transfer ERC20 on behalf of token owner after a payment of ... 7 juin 2022 How to send ERC20 token to smart contract balance? 22 janv. 2021 Autres rsultats pour stackoverflow.com Termes manquants: Peg | Afficher les rsultats avec: Peg Solidity Smart Contract all-in-one that allows the crowd- ... Gist https://gist.github.com stephenlb Gist https://gist.github.com stephenlb Traduire cette page Simplified Modifiable ERC20 Token Details. Controllable Crowd-sale and transferable ownership allows you to change ownership and change exchange rates. Termes manquants: Peg | Afficher les rsultats avec: Peg ERC-20, transferOwnership, and owner() - Contracts OpenZeppelin Forum

google.com

26 juill. 2022 In a Solidity contract, you can only check activity directly related to this contract. Your code does not have access to read other transactions...

stackoverflow.com

After assigning the owner then we will create a modifier. Modifiers are used for reusing the code. We have named our modifier ownable and inside the modifier...

coinsbench.com