Gossipp Protocol

The problem it solves

The Problem It Solves

Traditional anonymous confession apps suffer from two major problems: sustainability and user ranking transparency. Most rely on distracting ads for monetization, and content feeds are rarely sorted by true community value, often letting quality content drown in noise.

Gossipp solves this by implementing x402 Protocol Micropayments directly on Base. It makes "spilling the tea" sustainable and self-moderating without ads.

---

Why Gossipp Works

Sustainable Monetization without Ads

Instead of selling user data or showing ads, Gossipp uses native Web3 micropayments ($0.01 USDC) to unlock premium content.
This aligns incentives:

• Creators post better content to get unlocked
• Readers pay pennies for high-quality entertainment

Viral Content Discovery

The built-in Unlock Count acts as a sybil-resistant ranking signal.
Since every unlock effectively costs money as proof of interest, the Hot and Viral rankings are tamper-proof and genuinely reflect community engagement, unlike bot-able upvotes.

Safe Anonymity

By hashing onchain identities (Wallet or FID) into daily-rotating Ghost IDs such as Ghost-A7B2users can express themselves freely without fear of permanent doxxing.
At the same time, the system maintains cryptographic provenance to prevent spam.

---

How People Can Use It

• Share Secrets Safely
  Vent about life, work, or relationships anonymously.

• Discover High-Quality Gossip
  Read strictly the most unlocked and verified viral stories first.

• Social Bragging
  Generate beautiful, data-backed Brag Cards showing how much tea you have sipped and share them on Farcaster or X.

• Web3 Onboarding
  A perfect low-stakes introduction to USDC and Base micropayments for non-financial fun.

Challenges we ran into

1. Farcaster Frame Context and Local Testing

Challenge
Local Farcaster Frame development is hard due to SSL requirements and strict manifest validation. Our frame failed to render in Warpcast, and debugging user context was unclear.

Solution

• Used ngrok to expose localhost:3000 over HTTPS
• Implemented a correct .well-known/farcaster.json with the exact signed key payload
• Mocked Frame context locally to iterate on UI without redeploying each change

---

2. OnchainKit Wallet UI Conflicts

Challenge
The default OnchainKit connect button styling and avatar conflicted with our custom pastel, minimal UI and cluttered the header.

Solution

• Applied targeted CSS overrides using data-testid="ockConnectWallet_Container"
• Hid the default avatar while keeping address display and dropdown intact
• Preserved OnchainKit logic while matching our custom design

---

3. Native Mobile Sharing vs Desktop

Challenge
Browsers do not allow attaching images directly to X share intents on desktop.

Solution

• Implemented a hybrid flow using the Web Share API
• Mobile: Opens native share sheet with the PNG attached
• Desktop: Falls back to downloading the image for manual sharing
• Ensures a smooth experience without breaking browser security rules

---

4. Next.js 16 Turbopack Compatibility

Challenge
Next.js 16 Turbopack flagged our custom Webpack config used for wallet SDK polyfills.

Solution

• Added an explicit turbopack: {} config
• Retained required webpack.externals and resolve.fallback settings
• Passed Vercel build checks while keeping crypto libraries functional