Skip to content

Latest commit

 

History

History
343 lines (291 loc) · 10 KB

IERC20.md

File metadata and controls

343 lines (291 loc) · 10 KB

IERC20.sol

View Source: openzeppelin-solidity/contracts/token/ERC20/IERC20.sol

↘ Derived Contracts: ERC20, ICxToken, IERC20Detailed, IERC20Metadata, IVault

IERC20

Interface of the ERC20 standard as defined in the EIP.

Events

event Transfer(address indexed from, address indexed to, uint256  value);
event Approval(address indexed owner, address indexed spender, uint256  value);

Functions

totalSupply

Returns the amount of tokens in existence.

function totalSupply() external view
returns(uint256)

Arguments

Name Type Description
Source Code
function totalSupply() external view returns (uint256);

balanceOf

Returns the amount of tokens owned by account.

function balanceOf(address account) external view
returns(uint256)

Arguments

Name Type Description
account address
Source Code
function balanceOf(address account) external view returns (uint256);

transfer

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 nonpayable
returns(bool)

Arguments

Name Type Description
recipient address
amount uint256
Source Code
function transfer(address recipient, uint256 amount) external returns (bool);

allowance

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)

Arguments

Name Type Description
owner address
spender address
Source Code
function allowance(address owner, address spender) external view returns (uint256);

approve

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: ethereum/EIPs#20 (comment) Emits an {Approval} event.

function approve(address spender, uint256 amount) external nonpayable
returns(bool)

Arguments

Name Type Description
spender address
amount uint256
Source Code
function approve(address spender, uint256 amount) external returns (bool);

transferFrom

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 nonpayable
returns(bool)

Arguments

Name Type Description
sender address
recipient address
amount uint256
Source Code
function transferFrom(
        address sender,
        address recipient,
        uint256 amount
    ) external returns (bool);

Contracts