The problem Noctwave solves

Creators are getting screwed, badly. Twitch, Patreon, and OF regularly skim 20-30% of every dollar, censor content on a whim, and track every subscriber through IP addresses and payment processors.

Fans want privacy but get doxxed. The creator economy keeps getting hit after hit.

Something has to change.

Challenges we ran into

We hit a few real technical walls, but the biggest ones were:

Cross-chain complexity: ENS lived on Ethereum Sepolia while the app ran on Base Sepolia, so we had to explicitly pin every contract read/write to the right network or things silently broke.

Swarm publishing and retrieval: getting uploads working in the browser was not enough — the Bee node had to stay server-side, and Swarm feeds turned out to overwrite state unless we merged and rewrote the full feed each time.

Video processing in the browser: ffmpeg.wasm needed extra browser isolation headers, which caused a lot of deployment friction before transcoding would run consistently.

In the end, we fixed it by separating what had to happen on-chain, what had to happen server-side, and what could safely happen in the browser.

That gave us a stable upload, subscribe, and playback flow that actually works in production.