Context
The product stays undisclosed, so what is worth describing is the constraint. The UI ran inside a Chrome extension, and the wallet flows had to work under the rules the browser sets for extension code.
Extension / dApp — 2024
Chrome extension & Web3
A Chrome extension with wallet connection built into it. I built the extension on CRXJS and the wallet layer on top of it, across the extension’s origin boundary.
What I built
The extension itself, built on CRXJS (the Vite plugin for Chrome extensions). On top of it, the wallet layer: connect a wallet, confirm the account and the network, and react when either changes.
Architecture
An extension is not a web page, and that decides the design. Its UI runs on an extension origin, where a wallet does not inject a provider the way it does into a site — so wallet access had to be explicit, not a grab at whatever the page provides. wagmi’s connector model and Dynamic’s SDK carry that layer: connectors, the active account, the current chain, and events when any of them change. MetaMask is one of the wallets reached through that layer.
Outcome
The extension shipped to users in 2024. The Web3 work here is integration, not token launches or tokenomics.
Have a product to ship?
Send the idea, the repo or the half-built thing. I answer with questions first, then a written scope. Hiring? Tell me which role.