Picture this: you're building the next big thing on @ethereum Your app allows users to __ ERC20 tokens. Cats, dogs, penguins, the US dollar, you name it, anything that's a token, users can __. They click the button. Something breaks. Let's explore the dark side of ERC20s👇🧵

Did you know some tokens store their details as bytes32 instead of strings? Famous example of this was @SkyEcosystem’s OG $MKR token.

@rauchg You need a new pen, that looks like an outdated ▲ logo right there 👀

RT @razgraf: Picture this: you're building the next big thing on @ethereum Your app allows users to __ ERC20 tokens. Cats, dogs, penguins,…

H/t to @MirceaGavriliu, @sy100x for ideas and feedback + @PaulRBerg for recommending I write this thread. -- What other ERC20 unexpected mechanics have you uncovered?

→Token details, string vs bytes32 Most ERC20s return name/symbol as strings. To optimize gas, devs may choose to represent these in bytes32. The switch can cause failing queries, or worst, failing infra when indexers like @graphprotocol or @envio_indexer stop parsing events ✋

Fancy a long-form option you can bookmark and enjoy later? Head over to the @Sablier blog to get the full piece. Or keep reading for some not-so-easy to spot pitfalls with ERC20 tokens.

Picture this: you're building the next big thing on @ethereum Your app allows users to __ ERC20 tokens. Cats, dogs, penguins, the US dollar, you name it, anything that's a token, users can __. They click the button. Something breaks. Let's explore the dark side of ERC20s👇🧵