frens

Building /frens, a crypto messaging app. 

Spent the week on a caching system for tokens (like erc20s) based around CAIP-19 cross-chain ids. Motivation was to have a standardized unique identifier that had all the data necessary so we wouldn’t have to refactor from the ground up for Solana or Bitcoin.

CAIP-19 defines a way to identify assets like erc20 tokens in a human readable way:
"{{chain_id}}{{asset_namespace}}{{asset_reference}}"

For example, USDC on Base would be defined as:
"eip155:8453/erc20:0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"

Shoutout to @pedrouid.eth and others for their amazing work:

Building @frens | @orangedao | @a16zcrypto CSS

CAIP-19 defines a way to identify assets like erc20 tokens in a human readable way:
"{{chain_id}}{{asset_namespace}}{{asset_reference}}"

For example, USDC on Base would be defined as:
"eip155:8453/erc20:0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"

Shoutout to @pedrouid.eth and others for their amazing work:
https://github.com/ChainAgnostic/CAIPs/blob/main/CAIPs/caip-19.md

This works for chain names that are fairly standardized like "base", but can get very frustrating when new L3s emerge and one platform chooses to represent it as "degen" and another chooses to use "degenchain".

APIs should do more to simplify this for developers. Below shows the id for $DEGEN on Base across APIs:

Zerion: "0x4ed4e862860bed51a9570b96d89af5e1b0efefed-base-asset-asset"
CoinGecko: "base_0x4ed4e862860bed51a9570b96d89af5e1b0efefed"
SimpleHash: "base.0x4ed4e862860bed51a9570b96d89af5e1b0efefed"