The problem saywaht solves

1. Video Editing Accessibility & Privacy

Problem: Existing mainstream editors like CapCut and Adobe Premiere are either paywalled, subscription-based, or privacy-invasive (uploading content to centralized servers).

Solution:

A free, open-source video editor that works on web, desktop, and mobile.

Local-first editing (your videos stay on your device).

No subscriptions/watermarks, unlike CapCut.

Decentralized storage (IPFS) for permanent, censorship-resistant publishing.

Multiple export options (local rendering, hardware acceleration, or backend FFmpeg).

2. Creator Monetization in the Web3 Economy

Problem: Video creators struggle to earn directly from their content, relying on platforms (YouTube, TikTok) that take a large revenue cut and gate monetization with algorithms.

Solution:

Video tokenization – every video becomes a tradeable digital asset (“creator coin”) using Zora Protocol.

Direct creator-fan investment – supporters can buy and trade coins tied to creators.

Automatic rewards – creators earn from trading activity (50% of fees).

Uniswap integration – ensures liquidity and market-driven value.

In short:

It’s CapCut without the surveillance and paywalls, combined with a Web3-powered creator economy where every video doubles as both content and a financial asset.

Challenges I ran into

One of the biggest challenges I faced was working with the new Zora SDK. Since it’s still relatively fresh, the documentation and examples were limited, and I had to spend a lot of time experimenting and digging into the source code to really understand how to integrate it. At first, I tried to build everything frontend-only because I wanted to avoid maintaining a backend. That quickly became difficult once I got into handling video exports with FFmpeg, which turned out to be far more resource-intensive than I anticipated.

FFmpeg in the browser ended up soaking up close to 80% of my build time—from debugging WebAssembly issues to handling memory constraints. After hitting performance bottlenecks and running into stability issues, I finally gave in and set up a lightweight backend export service. Ironically, the thing I resisted the most ended up being the smoothest part of the final system. The backend made video exports faster, more reliable, and scalable, and I learned that sometimes leaning on a server-side solution is the right tradeoff.

Smart Contract Address(es)

n/a