dice.fun

Problem Statement

dice.fun is a Web3-first streaming platform where creators keep99.5%of revenue, receiveinstant on-chain tips, and store content permanently on Filecoin, all while keeping identity private via ZK verification. Built on Kadena’s Chainweb EVM for low/no gas friction and real-time settlement.What it isdice.fun is a creator-first live streaming and content platform that removes gatekeeping, eliminates long payment delays, and puts ownership and privacy back in creators’ hands. It combines real-time on-chain payments (KDA), decentralized storage (Filecoin/IPFS), and ZK-powered identity verification (Self Protocol) so creators can stream from Day 1, get tipped instantly, and keep their content forever.The problem we solveHigh platform take(YouTube/Twitch ~30–45%) cuts creator revenue.Monetization barriers: thresholds for earnings (subs/watch hours) lock out new creators.Payment delays: 30–60 days for payouts is unacceptable for small payments and living creators.Censorship & lock-in: centralized hosting risks content loss or takedowns.Privacy-invasive KYCfor verification excludes privacy-minded creators.dice.fun fixes all of the above with a privacy-first, low-fee, instant-payment streaming experience.Core product & featuresInstant monetization:start earning on Day 1 no subscriber/watch thresholds.Real-time tips & settlements:wallet-to-wallet KDA transfers that settle instantly on Kadena Chainweb EVM.0.5% platform fee:creators keep 99.5% of tips/revenue.Decentralized storage:every upload archived to Filecoin/IPFS with PieceCIDs and multi-provider redundancy.ZK verification (Self Protocol):verify humanity/identity without revealing personal data.Creator registry & reputation:on-chain registry to discover creators, support authenticity, and enable subscriptions/tokens.Mobile + web clients:low-latency streaming UIs with wallet integrations (MetaMask/Kadena wallets).API & SDKs:developer-friendly SDKs for tipping, content uploads, and pieceCID retrieval.Analytics & dashboard:creator dashboards with payout history, retention, and tipping analytics (privacy-preserving).How a tip / payout worksViewer connects wallet (MetaMask or compatible Kadena EVM wallet).Viewer clickstipon live stream UI and signs a transaction (tip amount + stream/creator id).Tipping smart contract (simple forwarding contract) processes the tx andimmediately transfers KDAto creator wallet (minus 0.5% fee routed to platform treasury).Transaction confirmed on Chainweb EVM; UI shows instant settlement.Tip metadata (anonymized) optionally stored on-chain for receipts/audit.ArchitectureFrontend:Next.js + React + TypeScript + Tailwind. Wallet integration via MetaMask/Wagmi.Streaming layer:WebRTC or low-latency CDN for live stream ingest + HLS for replays.Payments layer:Kadena Chainweb EVM smart contracts (tipping, creator registry, revenue share).Storage layer:IPFS + Filecoin for permanent storage and PieceCID assignment. Uploads are verifiable and replicated across providers.Identity layer:Self Protocol for ZK-powered verification; issuance of privacy-preserving attestations.Backend services:Minimal serverless microservices for indexing, push notifications, analytics aggregation, and gateway to Filecoin deals.Dev/API:Public REST + GraphQL endpoints and SDKs for integration and dev-rel use cases.Tech specifics & example network infoChain:Kadena Chainweb EVM (EVM-compatible)Example testnet:Chain ID5920(chain 20), RPChttps://evm-testnet.chainweb.com/chainweb/0.0/evm-testnet/chain/20/evm/rpc(as provided)Storage:Filecoin / IPFS with PieceCID assignment and retrieval via public gatewaysIdentity:Self Protocol ZK attestations (no raw KYC documents stored)Suggested smart contract interfacesTipping contract (solidity-like pseudocode):function tip(address creator, address token, uint256 amount) external payable { // accept native KDA or ERC-20 // collect 0.5% platform fee // forward remainder to creator immediately emit Tip(msg.sender, creator, amount, token, txhash); }Creator registry:registerCreator(creatorAddr, metadataCID, attestations) stores reference to on-chain registry + metadata CID on IPFS/Filecoin.(These are templates implement with Kadena-compatible tooling and security audits.)Filecoin + upload flowUser uploads file via frontend (client-side chunking).File is processed & content-addressed → PieceCID generated.Frontend shows upload progress & PieceCID.Backend orchestrates Filecoin deal(s) across providers for redundancy.PieceCID + proof-of-storage are logged and retrievable for verification.UI and API expose permanent access URLs via multiple IPFS gateways.Demo flow (dev-rel):Upload profile pic → display PieceCID → verify piece exists on Filecoin via proof endpoint.Identity & privacySelf Protocolissues ZK attestations proving attributes (e.g., “real human”) without exposing PII.No invasive KYC by default.Only request minimal KYC for certain monetization features (if/when required by law).User control:identity attestations are self-sovereign, revocable by user, and never centrally stored in raw form.Revenue & tokenomicsPlatform fee:0.5% of transaction volume.Monetization streams:tipping, paid subscriptions (on-chain), creator tokens, optional platform-native features (badges, boosts).Treasury:collects fees for ops, liquidity provisioning, and grants.Goal:transparent, predictable, and extremely creator-favorable economics.Security, compliance & moderationSecurity:smart contract audits, bug bounty program, hardened private key handling, rate limiting for RPCs.Compliance:privacy-first defaults; comply with local regulations when required (e.g., AML/KYC for large withdrawals). Provide legal playbooks for creators.Moderation:decentralized content policy with tools for community governance; removal requests processed with transparent appeals.Go-to-marketPhase 1: Crypto natives:target Web3 creators via Twitter, Discord, hackathons, and integrations with existing wallets.Phase 2: Micro-influencers:onboarding programs, referral incentives, and creator grants.Phase 3: Mainstream migration:partnerships, creator conferences, mobile apps, PR campaigns highlighting 99.5% economics.RoadmapMVP (done): live streaming + tipping + basic Filecoin backup + ZK verification.Next: mobile app, creator dashboard, advanced analytics, subscriptions, creator tokens.Longer: DAO governance, cross-chain wallets, NFT/gated content, global expansion.Key metrics to trackActive streamers, daily active users, total tipped volume, median tip size, creator retention, UAC, uptime, storage proof reliability, NPS.For developers / devrelAPIs:tip, registerCreator, uploadToFilecoin, getPieceCID, getProof.SDKs:JS/TS SDK for frontend, simple CLI for Filecoin deal creation, example Next.js app with MetaMask + streaming integration.Open source:provide example repo showing profile upload → PieceCID → on-chain registration.FAQsCan I withdraw immediately?Yes tips go directly to creator wallet. Withdrawals depend on user’s wallet/exchange.What about gas fees?Kadena EVM is chosen for minimal/no user-visible gas friction tiny gas costs for contract ops compared to traditional chains.Is content really permanent?Files are stored with Filecoin deals and replicated; permanent access depends on deal renewals and redundancy policies we manage.How private is ZK verification?Attestations prove attributes without exposing underlying PII; the platform does not retain raw KYC docs.

Solution

We built this project using a combination of blockchain and web technologies. The backend leverages Kadena smart contracts to handle transparent transactions with low fees. We integrated Filecoin for decentralized storage of streaming-related metadata and assets, ensuring scalability and permanence. For the frontend, we used Next.js and TypeScript to create a fast, responsive, and user-friendly interface.During development, we faced multiple challenges, particularly in understanding Kadena’s tooling and integrating it with our system. We consulted with Kadena’s team several times to clarify contract logic and transaction flows. Filecoin integration also required extensive troubleshooting to align with our storage needs.Despite the struggles, including working long hours without rest, we were able to bring the components together into a functional product. The process demanded persistence, constant iteration, and creative problem-solving, especially in managing the complexities of blockchain interoperability.