Blockhead: ETHOnline 2022

Blockhead is a super-interface for EVM blockchains, DeFi, and web3 protocols, consisting of a crypto/DeFi/NFT portfolio tracker ("Portfolio"), a cross-EVM block explorer ("Explorer"), and data explorers for DeFi apps and web3 protocols ("Apps"). Built as a data-agnostic, fully client-side web app, Blockhead is tightly integrated with a wide variety of indexing solutions and infrastructure providers across the decentralized web, putting YOU in full control of the data sources that power the views and dashboards. It's a web3-native frontend experience purpose-built for customizability, transparency, redundancy, accessibility, and decentralization!

Fun fact: Blockhead started two years ago as a hack for ETHOnline 2020 (https://showcase.ethglobal.com/ethonline/blockhead), and I've continued to iterate and integrate new data providers at hackathons ever since!

Follow me on Twitter and Gitcoin Grants:

• twitter.com/darryl__yeo

• twitter.com/0xBlockhead

• gitcoin.co/grants/2966/blockhead

Changes made during ETHOnline 2022:

• Aurora: Added Aurora to the "Portfolio" and "Explorer" views to allow users to view their token balances, DeFi balances, NFTs, and smart contract activity on Aurora.

• Covalent: Refactored the logic for fetching token and NFT balances using TypeScript types to make internal data structures more consistent with other data providers. (Data normalization is a hard problem!)

• Cronos: Added Cronos to the "Portfolio" and "Explorer" views to allow users to view their token balances, DeFi balances, NFTs, and smart contract activity on Cronos.

• ENS: Added QuickNode as an "On-Chain Data" provider which resolves users' ENS names over JSON-RPC. Upgraded Blockhead's ENS explorer (powered by the hosted ENS subgraph) to the latest version of Houdini (a GraphQL client for Svelte) which fetches and caches GraphQL schemas and generates TypeScript bindings automatically as part of the local dev and build processes!

• IPFS: Published Blockhead as a static web app on the Valist Registry (powered by Polygon and IPFS).

• NFTPort: Refactored the logic for fetching NFT balances using TypeScript types to make internal data structures more consistent with other data providers. (Data normalization is a hard problem!)

• Optimism: Added QuickNode as an "On-Chain Data" (JSON-RPC) provider for Optimism (used to fetch native currency balances in "Portfolio" and query historical transaction data in "Explorer"). Refactored the logic for fetching token and NFT balances using TypeScript types to make internal data structures more consistent across data providers.

• Polygon: Published Blockhead as a static web app on the Valist Registry (powered by Polygon and IPFS). Added QuickNode as an "On-Chain Data" (JSON-RPC) provider for Polygon.

• QuickNode: Added QuickNode as a "Token Balances" provider to fetch users' Ethereum token balances via QuickNode's custom "qn_getWalletTokenBalance" JSON-RPC method. Added QuickNode as an "On-Chain Data" provider for Ethereum, Polygon, and Optimism (JSON-RPC data is used throughout Blockhead to resolve ENS names, fetch native currency balances, query historical transaction data, and query Ethereum DeFi balances through Zerion's smart contracts). I plan to implement the "qn_fetchNFTs" method so I can add QuickNode as an "NFT" provider as well!

• The Graph: Upgraded to the latest version of Houdini (a GraphQL client for Svelte) that fetches and caches GraphQL schemas and generates TypeScript bindings automatically as part of the local dev and build processes! Upgraded Blockhead's ENS explorer (powered by the hosted ENS subgraph) accordingly.

• Valist: Published Blockhead as a static web app on the Valist Registry (powered by Polygon and IPFS).

Paying off tech debt:

• Upgraded SvelteKit to 1.0.0-next.405 (a major breaking change).

• Upgraded to the latest version of Houdini (a GraphQL client for Svelte) adjacent to the SvelteKit upgrades.

• Replaced Zapper's deprecated v1 API with Zapper's v2 API (powering "Account" views in "Apps", "Balances" and "DeFi Balances" in "Portfolio").

• Lots of internal renaming of variables and data structures, especially for views with swappable data providers. (Data normalization is a hard problem!)