How otaviootavio/custom-hls works
Project type and purpose
• This is a multi‑component, decentralized video‑streaming platform with micropayments. It consists of four sub‑projects orchestrated by Docker Compose:
• eth‑payword: Ethereum smart contract (Hardhat) + React dApp
• extension: Browser extension for hash‑chain management
• mp4‑to‑hls: Command‑line utility to convert MP4 to HLS segments
• my‑hls‑app: Next.js frontend+API for streaming HLS with PayWord payments
High‑level component breakdown
• Ethereum Blockchain: Runs the PayWord smart contract
• Hardhat (eth‑payword/hardhat): Local dev/test node, contracts, tests, deployment scripts
• dApp Frontend (eth‑payword/frontend): React/TS UI for contract interaction
• Browser Extension (extension/src): React/TS popup, background, content scripts to manage and inject hash‑chains
• Video Conversion Utility (mp4‑to‑hls): Node.js script producing .m3u8 and .ts files
• Streaming App (my‑hls‑app): Next.js SSR/CSR pages, API routes, Prisma schema, HLS player
• Storage Layer: Local folder or S3 bucket for HLS segments
• Orchestration: docker‑compose for services (blockchain node, possibly IPFS or local file server)
• External Services: Ethereum node (Infura or local), Package registry (pnpm), CI/CD
Relationships and data‑flow
• User’s browser → my‑hls‑app UI → requests video playlist (.m3u8) & segments (.ts)
• my‑hls‑app → (optionally) fetches/updates payment state via its API routes → interacts with PayWord smart contract over web3
• dApp (eth‑payword/frontend) → direct contract interactions: open/close channels, issue hash‑chain
• Browser Extension → maintains local hash‑chain, injects it into dApp or my‑hls‑app pages, signs micropayment tokens
• mp4‑to‑hls utility → pre‑processes source videos into HLS assets stored in playlist directory or bucket
• Docker Compose → spins up blockchain node, streaming app, and any other services for local dev
Architectural patterns and design principles
• Monorepo style with clearly separated sub‑projects
• Frontend‑backend separation: Next.js for SSR + API, standalone React dApp, React extension UI
• Microservices / utility: mp4 converter as isolated CLI service
• Payment channel pattern: off‑chain hash‑chain generation, on‑chain settlement
• Context providers & hooks in React for global state (HashChainProvider, Wagmi, Zod schema validation)
Technologies & frameworks
• Smart contracts: Solidity, Hardhat, TypeScript
• Frontends & extension: React, TypeScript, Vite, Next.js, Tailwind CSS, Zod
• Storage & API: Prisma (PostgreSQL or other), Next.js API routes, local filesystem or S3
• Blockchain interaction: ethers.js, wagmi
• Orchestration & packaging: Docker Compose, pnpm, vite, tsconfig