Difference between revisions of "ERC2612"

From CryptoWiki

m (1 revision imported)
m
 
Line 1: Line 1:
* Permit extension for [[ERC20]]
* Permit extension for [[ERC20]]
* [https://github.com/ethereum/EIPs/blob/8a34d644aacf0f9f8f00815307fd7dd5da07655f/EIPS/eip-2612.md From] the [[Github]] (25-4-2020):
* [https://github.com/ethereum/EIPs/blob/8a34d644aacf0f9f8f00815307fd7dd5da07655f/EIPS/eip-2612.md From] the [[Github]] (25-4-2020):
''"A function <code>permit</code> extending ERC-20 which allows for approvals to be made via <code>secp256k1</code> [[signature|signatures]]. This kind of "account abstraction for ERC-20" brings about two main benefits:''
''"A function <code>permit</code> extending ERC-20 which allows for approvals to be made via <code>secp256k1</code> [[signature|signatures]]. This kind of "[[account abstraction]] for ERC-20" brings about two main benefits:''
* ''transactions involving ERC-20 operations can be paid using the [[token]] itself rather than [[ETH]],''
* ''transactions involving ERC-20 operations can be paid using the [[token]] itself rather than [[ETH]],''
* ''approve and pull operations can happen in a single transaction instead of two consecutive transactions,''
* ''approve and pull operations can happen in a single transaction instead of two consecutive transactions,''
''while adding as little as possible over the existing ERC-20 standard."''
''while adding as little as possible over the existing ERC-20 standard."''
[[Category:Jargon/Various]]
[[Category:Jargon/Various]]

Latest revision as of 04:25, 19 March 2023

"A function permit extending ERC-20 which allows for approvals to be made via secp256k1 signatures. This kind of "account abstraction for ERC-20" brings about two main benefits:

  • transactions involving ERC-20 operations can be paid using the token itself rather than ETH,
  • approve and pull operations can happen in a single transaction instead of two consecutive transactions,

while adding as little as possible over the existing ERC-20 standard."