Coinpedia

Screenshots

Problem Statement

The ERC-20 spec gives only minimal information about a coin, just a symbol and a name (e.g., AERO and "Aerodrome"). When you want to show information about a coin, you typically also want an icon, description and links to the official website and social channels.Coinpedia stores this data and allows updates to it in a mostly permissionless way, while making sure that the quality of this metadata is trustworthy.If ERC-20 contracts have an owner, the owner can submit updates to the metadata at any moment. Offchain APIs can also be used to update metadata, and currently importing data for coins that were launched through ape.store is supported. Any user who's not the coin contract owner can also submit updates to metadata, but then there need to be safeguards against malicious users submitting spam or links to phishing sites. The current implementation charges 0.01 ETH for those updates to disincentivize submitting false data.

Solution

Sign protocol collects the attestations of coin metadata. The sign protocol indexer can then be used to look up the latest submitted metadata for any coin address. A custom hook for the Sign schema makes sure that the attesting user is either the coin owner or a whitelisted address. A custom facade in front of the Sign main contract handles the vetting of community updates which due to time constraints is just a payment of 0.01 ETH in the current implementation.Lit protocol automates importing coin metadata from trusted external APIs (with ape.store implemented as an example) -Envio HyperSync collects the top transferred coins to show for Base & Base SepoliaSvelteKit serves the frontend (source code in the web/ directory)web3-onboard for connecting the walletviem for interacting with the blockchain