token-lists VS zod

Uniswap tokenlist format

We’re thrilled to announce that the Crypto.com DeFi Wallet has integrated Token Lists!

I know that in order to get the addresses of every ERC20 token, https://etherscan.io/ and https://tokenlists.org/ are the way to go.

It's important to note that Uniswap is decentralized and anyone can "list" anything for trading without asking anyone or going through any process. This means there are thousands of tokens, probably millions in the future, available to trade.

Users do not see these tokens unless they actively search them out. Uniswap uses the TokenList standard (https://tokenlists.org/) and by default users only see tokens such as the top 100 projects on CoinGecko. There are many lists created by reputable players such as Aave and Gemini which cover the entire gamut of projects users want to trade without exposing end users to scam tokens.

I believe this is a good system and has worked well as having any kind of listing process or even a DAO introduces subjectivity and provides points of capture for bad actors. With an open listing process and standards like TokenLists we can say that Uniswap is truly a public good and will be around as long as we need it which provides a guaranteed way to swap any asset for any other asset no matter who created it or how controversial it is which is a good primitive for humanity to be able to rely on.

This should get you there.

Zod is an open-source schema declaration and validation library that emphasizes TypeScript. It can refer to any data type, from simple to complex. Zod eliminates duplicative type declarations by inferring static TypeScript types and allows easy composition of complex data structures from simpler ones. It has no dependencies, is compatible with Node.js and modern browsers, and has a concise, chainable interface. Zod is lightweight (8kb when zipped), immutable, with methods returning new instances. It encourages parsing over validation and is not limited to TypeScript but works well with JavaScript as well.

Zod is a TypeScript-first schema declaration and validation library. It helps create schemas for any data type and is very developer-friendly. Zod has the functional approach of "parse, don't validate." It supports coercion in all primitive types.

Link: https://zod.dev/

You can check out their documentation here.

You can learn more about Zod on their website here.

In JS, it's a good idea anyway to use some JSON parsing library instead of JSON.parse.

With Zod, you can use z.bigint() parser. If you take the "parse any JSON" snippet https://zod.dev/?id=json-type and change z.number() to z.bigint(), it should do what you are looking for.

We will validate our input using client-side zod. Zod handles TypeScript-first schema validation with static type inference. This means that it will not only validate your fields, it will also set types on validated fields.

A word of warning: while discriminated unions are very powerful, there's an ongoing discussion on whether discriminated unions should be deprecated and replaced with a different API.

I was first introduced to Zod by Adam Bobrow - a colleague of mine and a dear friend. Adam was sick and tired from JavaScript's brittleness, and about two years ago he started migrating our code base to TypeScript. But that wasn't enough for him. He kept complaining: "What good are my types, if some other service decides to send me bad data and breaks my code?". That's when he discovered Zod.