kin-o.live

Don't just tip — back live talent early with private participation and verifiable 50/50 vault growth.

Comment

Inspiration

Live streaming money is broken in two opposite ways:

  1. Fully public chains turn tips, balances, and strategies into a permanent public dossier — bad for normal fans and serious brands.
  2. Web2 platforms take opaque cuts, trap creators, and give brands weak proof that a sponsorship actually delivered.

Creators need culture that feels public and finances that stay private. Brands need verifiable delivery without leaking strategy. Supporters want to back talent early without doxxing their wallet.

What it does

kin-o is a Kick-style live platform with LiveFi economics and privacy-first design:

  1. Watch & chat — real live rooms, multi-quality HLS, real-time chat, points, predictions.
  2. Support with 50/50 routing — half to the streamer (claimable), half into the streamer vault.
  3. Community milestones, not public ledgers — vault progress and unlocks are social; individual balances stay private.
  4. Bind — AI brand concierge matches brands ↔ streamers, runs deal workspace, activates on-stream overlays, and verifies proof-of-performance.
  5. Midnight data protection — sensitive financial, identity, and brand data use selective disclosure: prove the important facts (split applied, milestone met, eligible, deliverable verified) without exposing underlying private state.

How we built it

Layer Implementation
Product UI Next.js App Router, Kick-inspired dark theme, stream room + studio + brand surfaces
API / realtime Express + native WebSocket chat, Postgres durable state, Redis hot state
Streaming OBS → RTMP → node-media-server → FFmpeg → HLS ABR
Support / vault 50/50 support routing, channel identity, vault progress, claim paths, yield distribution plumbing
Bind + AI OpenRouter LLMs for brand research/matching/coaching; proof-worker + vision on HLS chunks
Privacy (Midnight) Selective disclosure model for private balances, vault positions, brand terms, and AI features; public verifiable community facts

Monorepo: frontend/, backend/, contracts/, streaming/, proof-worker/, e2e/.

How we use Midnight (for judges)

Midnight solves the core LiveFi tension: verify without oversharing.

User need Midnight-aligned design in kin-o
Fans support without public humiliation economics Private individual tip/position data; public community energy
Streamers claim earnings safely Claimable fee state protected; policy-verifiable claims
Vault growth is trustworthy Prove 50/50 routing & milestone thresholds without dumping every private transfer
Brands run deals Confidential deal terms + escrow lifecycle; public campaign status when intended
AI matching Process sensitive briefs/features without exposing raw personal or brand corpora

Selective disclosure examples we highlight in the demo:

  • Prove support obeyed 50/50 without revealing every peer’s exact amount.
  • Prove vault hit a milestone without publishing the full private contribution map.
  • Prove PoPP / campaign completion without revealing full brand strategy docs.
  • Prove eligibility for community windows without leaking full identity attributes.

This is Midnight’s product thesis applied to live streaming: data protection for real applications.

Challenges we ran into

  • Keeping streaming UX as polished as Kick while wiring real settlement + privacy semantics.
  • Making PoPP honest (real HLS + vision) instead of fake “always pass” simulation.
  • Designing copy so normal users see “support / vault / campaigns,” not crypto jargon.
  • Aligning public culture (chat, milestones, overlays) with private money (balances, deals).
  • Full-stack reliability: RTMP, WS chat, Postgres, Redis, AI workers, and chain surfaces all at once.

Accomplishments we’re proud of

  • A working live product at kin-o.live.
  • End-to-end loop: stream → chat → support/vault → Bind campaign → proof.
  • Clear privacy story for LiveFi that matches Midnight’s selective-disclosure model.
  • AI sponsorship workflow that brands and creators can actually operate.
  • Documentation and local ./scripts/dev-local.sh path for other builders.

What we learned

  • Privacy is a product feature, not only a chain feature — UI must show milestones without exposing individuals.
  • AI + sponsorship needs proof, not vibes — PoPP closes the trust gap.
  • Midnight-style selective disclosure is the right primitive for social-fi: public energy, private money.
  • Shipping a monorepo streaming stack under hackathon pressure teaches ruthless prioritization.

What's next

  • Deeper Compact / Midnight-native private state for vault positions and deal terms
  • Mainnet-ready privacy settlement with production key management
  • Expanded Bind measurement + more creator tools
  • Whitelist → private beta cohort → vault participation programs
  • Legal/security review before advanced season modules

Built With

  • ai`
  • compact
  • css`
  • docker`
  • express`
  • ffmpeg`
  • hardhat`
  • hls`
  • llms
  • midnight`
  • next.js`
  • openrouter`
  • playwright
  • postgresql`
  • privy`
  • react`
  • redis`
  • rtmp`
  • solidity`
  • tailwind
  • typescript`
  • websockets`
Share this project:

Updates