PEPU Dev Kit
Pepe Unchained is taking its chain consumer-first. Users sign in with Google and just tap: no seed phrase, no wallet popup, no gas. A vision like that needs infrastructure underneath it, and tools that make it the default for every builder. We built both, and delivered their full developer roadmap as one kit.
- Client
- Pepe Unchained
- Year
- 2026
- Timeline
- Sep — Oct 2026
- Status
- Live
- Role
- Protocol infra · Developer tools · AI tooling · Docs
- Stack
- TypeScript · viem · Privy · ZeroDev · ERC-4337 · MCP
Consumer-first is easy to say and hard to ship. It takes gasless transactions, sessions that don't ask for a signature on every tap, and a path smooth enough that builders get it right without trying. None of that existed on PEPU yet.
Infrastructure first
We stood up the layer that makes apps gasless and popup-free, so the experience is a property of the chain, not a workaround inside each app.
One source of truth
A single SDK sits underneath everything, and the CLI, templates, docs and AI tooling are all built on it, so they never drift apart.
Proven on the real chain
Every address, flow and edge case was verified on PEPU mainnet. Nothing was copied from another chain and hoped for.
Built for AI-native builders
Coding agents like Claude get their own tools and skills, so they build on PEPU correctly from the first prompt.
Gasless by default
Hosted services that pay users' network fees for them.
The PEPU SDK
One package for sign-in, sessions, smart accounts and sponsorship.
AI-native tooling
An MCP server, agent skills and a Claude Code plugin.
Start in one command
A CLI and six starter apps, from simple to fully sponsored.
Core contracts
Deployed and verified on PEPU mainnet.
The developer docs
docs.pepeunchained.com, end to end.
