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.
burn
Allows the authorized bridges (checked via the factory) to burn tokens on withdrawals Required user: bridge
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.
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.
initialize
Initializes the token with factory variabls Required user: factory
mint
Allows the authorized bridges (checked via the factory) to mint tokens on deposits Required user: bridge
transfer
See IERC20-transfer. Requirements: - to cannot be the zero address. - the caller must have a balance of at least amount.
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. 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.