ERC 20 Wrapper
Extension of the ERC20 token contract to support token wrapping. Users can deposit and withdraw "underlying tokens" and receive a matching number of "wrapped tokens". This is useful in conjunction with other modules. For example, combining this wrapping mechanism with {ERC20Votes} will allow the wrapping of an existing "basic" ERC20 into a governance token. Available since v4.2.
Methods
allowance
See {IERC20-allowance}.
Parameters
owner
address
undefined
spender
address
undefined
Returns
_0
uint256
undefined
approve
See {IERC20-approve}. Requirements: - spender
cannot be the zero address.
Parameters
spender
address
undefined
amount
uint256
undefined
Returns
_0
bool
undefined
balanceOf
See {IERC20-balanceOf}.
Parameters
account
address
undefined
Returns
_0
uint256
undefined
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}.
Returns
_0
uint8
undefined
decreaseAllowance
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
.
Parameters
spender
address
undefined
subtractedValue
uint256
undefined
Returns
_0
bool
undefined
depositFor
Allow a user to deposit underlying tokens and mint the corresponding number of wrapped tokens.
Parameters
account
address
undefined
amount
uint256
undefined
Returns
_0
bool
undefined
increaseAllowance
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.
Parameters
spender
address
undefined
addedValue
uint256
undefined
Returns
_0
bool
undefined
name
Returns the name of the token.
Returns
_0
string
undefined
symbol
Returns the symbol of the token, usually a shorter version of the name.
Returns
_0
string
undefined
totalSupply
See {IERC20-totalSupply}.
Returns
_0
uint256
undefined
transfer
See {IERC20-transfer}. Requirements: - recipient
cannot be the zero address. - the caller must have a balance of at least amount
.
Parameters
recipient
address
undefined
amount
uint256
undefined
Returns
_0
bool
undefined
transferFrom
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
.
Parameters
sender
address
undefined
recipient
address
undefined
amount
uint256
undefined
Returns
_0
bool
undefined
underlying
Returns
_0
contract IERC20
undefined
withdrawTo
Allow a user to burn a number of wrapped tokens and withdraw the corresponding number of underlying tokens.
Parameters
account
address
undefined
amount
uint256
undefined
Returns
_0
bool
undefined
Events
Approval
Parameters
owner indexed
address
undefined
spender indexed
address
undefined
value
uint256
undefined
Transfer
Parameters
from indexed
address
undefined
to indexed
address
undefined
value
uint256
undefined
Last updated