Skip to main content

​
Overview

Render Stream is a Solana‑native studio designed to replace traditional desktop encoders with a web‑first, creator‑focused workflow. It powers Always‑On channels, low‑latency ingest, and wallet‑controlled automation that ties directly into the 555 OS (CTRL, Gamification, Monetization, Expand).
Key benefits: Always‑On programming, extended session uptime, low‑latency routing, wallet‑configured controls, and direct integration with CTRL, 555 Engine, and the Monetization pipeline.

​
Key Capabilities

Resilient Uptime

Continuous, failover‑ready ingest with auto‑recovery and health checks.

Low-Latency Servers

Choose regional servers to minimize end-to-end delay for interactive streams.

Crypto-Native Controls

Configure permissions and actions from your wallet; wire in gamification and on‑chain triggers.

Always‑On Programming

Keep your channel active when you’re offline with scheduled clips, mini‑games, raids/quests, and the 555 Lottery.

Auto Pilot Scheduling

Let the Render Agent recommend and rotate programming, ad breaks, and quests to maximize engagement and revenue.

Stream‑Level 555 Lottery

Enable a lottery for your own channel so your viewers and holders can participate without the global threshold.

​
Setup

​
Option A: Native Render Stream (Studio Beta)

Use the web control surface and wallet auth to start a stream without desktop encoders.
1

Auto‑Optimized Routing

We automatically route your stream to the best region and server based on audience distribution and live health metrics. Manual override is available in advanced settings if needed.
2

Connect Wallet & Configure Access

Connect your Solana wallet to set stream ownership and define controller permissions (e.g., moderator wallets). If integrating Pump.fun, ensure the project wallet has the required scopes.
3

Start Stream & Monitor Health

Start the session from the control surface. Monitor ingest health, bitrate, dropped frames, and auto-recovery status.
4

Schedule Always‑On (Optional)

Add a basic offline schedule: clips (from past streams and social channels), mini‑games, raids/quests, and 555 Lottery windows. You can also hand this off to Auto Pilot.

​
Option B: OBS Browser Source (Fallback)

If you are transitioning from OBS or need a hybrid setup, add the Render overlay as a browser source while you migrate scenes. 
# OBS Browser Source (example)
# 1) Sources → Add → Browser Source
# 2) Name: "Render Overlay"
# 3) URL: https://555.rendernet.work/overlay
# 4) Width: 1920, Height: 1080
# 5) Enable "Shutdown source when not visible"
Prefer the native Render Stream path for lowest latency and simpler operations. Use the OBS Browser Source during migration only.

​
Creator Token Integration

If you already have a Creator Token, connect it to add token trading fees into your revenue stream. If you don’t, you can mint a Creator Token with Render Expand — it wires your token into the flywheel automatically.
  • Staker eligibility: all stakers are eligible for revenue sharing based on their staked amount
  • Staking choice: creators may configure staking to their own token or to $555
  • Buybacks: a minimum of 20% of all creator revenue is used to buy back the staked token (creators can raise this above 20%)
  • Controls: gate actions (chat modes, overlay triggers) behind $555 or Creator Token thresholds; associate moderator wallets for management
See also: Creator Tokens · Fee Distribution (10/20/70)

​
Operations & Reliability

  • Session Recovery: Automatic reconnection and state recovery for transient network events.
  • Health Metrics: Ingest health, frame drops, CPU/network load recommendations, bitrate guidance.
  • Failover & Regions: Region selection with hot fallback; published bitrate and resolution limits per region (subject to change as capacity grows).

​
Roadmap: Decentralized Stream

  • Peer‑assisted distribution and resilient ingest
  • Community‑operated nodes with performance and reputation metrics
  • Censorship‑resistant architecture governed by a future DAO
⌘I