Inspiration
The current creator economy is plagued by high platform fees and fragmented payment systems. We wanted to build a platform that "solves the internet's original sin" by re-activating the long-dormant HTTP 402 (Payment Required) status code. Our goal was to create a "zero-middleman" environment where payments are as native to the web request as the data itself, enabling both humans and AI agents to transact instantly.
What it does
ContentHub is an end-to-end video monetization engine:
For Creators: An intuitive studio to upload content to decentralized storage (Lighthouse/IPFS) and register immutable access rights on the Base Sepolia blockchain.
For Consumers: A unified library to manage 24-hour rentals and lifetime subscriptions settled in USDC.
x402 Payment Flow: The hub serves content via the x402 standard. When an unauthenticated request (human or AI agent) hits a premium asset, the server responds with a 402 Payment Required header. The user then settles the transaction on-chain to unlock the resource.
How we built it
Frontend: Built with Next.js 15 and Tailwind CSS v4 for a high-performance, mobile-first experience.
On-Chain Logic: Developed custom Solidity contracts using Foundry on Base Sepolia to handle rental durations and on-chain access verification.
Identity: Integrated Privy for seamless, wallet-based authentication.
Storage: Leveraged Lighthouse/IPFS for decentralized storage, ensuring content remains under creator control.
Challenges we ran into
Implementing the x402 handshake was our biggest technical hurdle. We had to ensure the frontend could gracefully handle the "Payment Required" response, trigger a wallet signature, and retry the request with the X-PAYMENT header. Bridging this Web3 payment flow into a standard Next.js 15 environment required building custom middleware for real-time blockchain verification.
Accomplishments that we're proud of
Direct Monetization: Successfully enabling a flow where 100% of the revenue goes directly to the creator.
Seamless Rentals: Implementing on-chain time-locks that automatically expire access after 24 hours.
Agent-Readiness: By following the x402 specification, we have built an app that is "Agent-Native."
What we learned
We learned that the x402 protocol is the missing link for the machine-to-machine economy. By removing traditional checkouts, we make the internet more efficient for both creators and autonomous agents.
What's next
Autonomous Agent Consumption: Integrating with agent frameworks so AI agents can pay to watch/process content.
Dynamic Pricing Agents: Implementing smart contracts where rental prices fluctuate based on demand, managed by an autonomous "Governor Agent."
Built With
- base-sepolia
- foundry
- framer
- ipfs
- lighthouse
- next.js
- privy
- solidity
- viem
- x402
Log in or sign up for Devpost to join the conversation.