NitroGate

NitroGate: The "Pay-Per-Second" Streaming Platform NitroGate is an omnichain video platform that replaces monthly subscriptions with real-time micropayments. Money flows from viewer to creator second-by-second and stops the instant you hit pause.

The Problem Streaming on Web3 usually fails because of the "Gas Wall" (transaction fees cost more than the video itself) and Fragmented Liquidity (users have money on the wrong chain).

The Solution: The Trinity Architecture We solve these bottlenecks by combining three specific technologies:

Yellow Network (The Engine): We use state channels to move payments off-chain. Every second of video generates a zero-gas cryptographic signature (IOU), settling on-chain only when the session ends. This makes high-frequency micropayments possible.

Circle CCTP (The Bridge): We built a "Liquidity Gate." If a user is low on funds, our app detects USDC on other chains (like Ethereum Sepolia) and teleports it instantly via Circle’s Cross-Chain Transfer Protocol, so users never leave the video player.

ENS (The Data Layer): Instead of locking prices in smart contracts, creators set streaming rates via ENS Text Records (nitro.price). Our app fetches these dynamically, allowing creators to update pricing instantly without deploying new code.

How It's Made Built with Next.js 16, Tailwind, Wagmi, and Viem.

Core Stack Next.js 16, TypeScript, Tailwind CSS, Wagmi, and Viem.

Yellow Network: We built a custom useStreamSession hook that manages WebSocket state channels. Instead of costly transactions, we implement raw ECDSA signing (walletClient.signMessage) to generate off-chain IOUs every second, enabling zero-gas streaming.

Circle CCTP: We integrated TokenMessenger contracts on Sepolia. Our "Liquidity Gate" modal executes depositForBurn transactions, abstracting complex bridging logic into a single click to teleport liquidity instantly.

ENS: We use ENS as a database. Our app queries the Registry for specific text records (nitro.price) via Viem, allowing creators to update pricing dynamically without gas or smart contract deployments.

The "Hacky" Part To avoid centralized servers, we built a "Serverless Wallet-DB." We use the browser’s localStorage but key every entry by the Creator's Wallet Address. This persists complex earnings data and payment history across sessions, tied directly to the user's on-chain identity.