Skip to content

Commit 487b3f9

Browse files
authored
Update IERC20Permit.sol
1 parent c1c95aa commit 487b3f9

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

contracts/token/ERC20/extensions/IERC20Permit.sol

+2-2
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ pragma solidity ^0.8.20;
1515
*
1616
* There are two important considerations concerning the use of `permit`. The first is that a valid permit signature
1717
* expresses an allowance, and it should not be assumed to convey additional meaning. In particular, it should not be
18-
* considered as an intention to spend the approval in any specific way. The second is that because permits have
18+
* considered as an intention to spend the allowance in any specific way. The second is that because permits have
1919
* built-in replay protection and can be submitted by anyone, they can be frontrun. A protocol that uses permits should
2020
* take this into consideration and allow a `permit` call to fail. Combining these two aspects, a pattern that may be
2121
* generally recommended is:
@@ -32,7 +32,7 @@ pragma solidity ^0.8.20;
3232
* }
3333
* ```
3434
*
35-
* Observe that: 1) `msg.sender` is used as the owner, leaving no ambiguity as to the signer intent, 2) the use of
35+
* Observe that: 1) `msg.sender` is used as the owner, leaving no ambiguity as to the signer intent, and 2) the use of
3636
* `try/catch` allows the permit to fail and makes the code tolerant to frontrunning. (See also
3737
* {SafeERC20-safeTransferFrom}).
3838
*

0 commit comments

Comments
 (0)