ChainAuth

Inspiration

Web3 onboarding is broken. Users shouldn't need to install wallets, write down seed phrases, or understand cryptography just to try a blockchain app. I wanted to make Polkadot as easy to access as any web2 application.

What it does

ChainAuth lets users create a Polkadot wallet and send transactions using just their Google account. Login with Google, get an instant Westend wallet with your own address, check your balance, and send WND tokens. No extensions, no seed phrases, no friction.

How I built it

Next.js frontend with Web3Auth for social login integration. Web3Auth generates a private key from the user's OAuth token, which I use with Polkadot.js to create a real Westend wallet. The app connects to Westend RPC to fetch balances and broadcast transactions. Tailwind CSS for the interface.

Challenges I ran into

Web3Auth's MetaMask connector pulled in React Native dependencies that broke webpack compilation. Spent hours debugging chunk loading errors and module resolution. Also had to figure out the right Web3Auth configuration for Polkadot since most examples assume EVM chains.

Accomplishments that I'm proud of

I actually made it work. You can genuinely go from zero to sending Polkadot transactions in under a minute using just Google login. No wallet software required. That's the kind of UX that could actually bring normal users to Web3.

What I learned

Social login for Web3 is possible and powerful, but the tooling isn't mature yet. I learned how to bridge Web3Auth's key generation with Polkadot's cryptography, handle sr25519 key pairs, and work around dependency conflicts in modern build tools.

What's next for ChainAuth

Add more login providers (Twitter, Discord, email). Support multiple Polkadot parachains. Build a simple DApp store where users can try Polkadot applications without any setup. Make Web3 accessible to everyone.

Built With

• api
• css
• lucide
• next.js
• polkadot.js
• react
• tailwind
• typescript
• web3auth