The problem OffsetGram solves

OffsetGram on Base
Despite growing awareness of climate responsibility, most onchain users don’t understand the emissions associated with their activity. There’s no accessible, decentralized way to take meaningful climate action within the crypto ecosystem. This gap is especially noticeable on fast-growing chains like Base, where transaction volume is high, but carbon accountability is low.

OffsetGram solves this by turning climate action into a giftable, onchain experience powered by smart contracts. Users can enter any Farcaster handle or Coinbase wallet address, instantly calculate that identity’s lifetime emissions on Base. Our smart contracts deployed on base L2 enable the purchasing and retiring of crypto carbon credits available on Base to enable anyone to automatically offsets their footprint. The offset is executed onchain: when stablecoin (e.g., USDC) is received by the contract, it programmatically retires carbon credits via Base-compatible protocols.

Our tool is fully decentralized and open to the entire Base community, but our 0→1 integration begins with Evrlink, enabling users to send a sustainability-focused gift card for Earth Day or any meaningful occasion. It’s more than just a climate offset, it’s a way to build community and raise awareness of SDG 13: Climate Action through personal, verifiable, and joyful onchain experiences.

Challenges we ran into

During development, we initially deployed OffsetZap to AWS Amplify. Despite successful builds, the frontend persistently returned 404 errors. Static routing from Next.js (with the App Router) wasn’t compatible with AWS’s export-based build settings, and even after multiple attempts and configuration tweaks—including modifying next.config.js, .amplify.yml, and rewiring routes—the app remained inaccessible. AWS technical support acknowledged the issue but couldn’t resolve it within a reasonable timeframe.

To avoid further delays, we migrated the deployment to Vercel, which offers first-class support for Next.js. Within minutes, the site deployed cleanly, with proper routing and zero configuration friction. This switch allowed us to move forward with testing and user demos without compromising velocity.