Skip to content

Commit 6d06f77

Browse files
authored
Update README.md
1 parent 7e871af commit 6d06f77

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

patterns/erc20-compatibility/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
- [📜 Example Code](./ERC20Compatibility.sol)
44
- [🐞 Tests](../../test/ERC20Compatibility.t.sol)
55

6-
Inevitably, anyone writing smart contracts on Ethereum will have to interact with ERC20s. On its surface, the [standard](https://eips.ethereum.org/EIPS/eip-20) seems straight-forward enough, but inconsistencies in how the standard has been historically implemented can completely break critical components of a protocol. These inconsistencies aren't confined to uncommon tokens, either. For a real-world example, try trading [USDT on Uniswap V1](https://etherscan.io/address/0xc8313c965C47D1E0B5cDCD757B210356AD0e400C) 😉.
6+
Inevitably, anyone writing smart contracts on Ethereum will have to interact with ERC20s. On its surface the [standard](https://eips.ethereum.org/EIPS/eip-20) seems straight-forward enough, but inconsistencies in how the standard has been historically implemented can completely break critical components of a protocol. These inconsistencies aren't confined to uncommon tokens, either. For a real-world example, try trading [USDT on Uniswap V1](https://etherscan.io/address/0xc8313c965C47D1E0B5cDCD757B210356AD0e400C) 😉.
77

88
This guide will cover the two issues most developers working with arbitrary ERC20 tokens will run into and how to get around them.
99

0 commit comments

Comments
 (0)