Skip to content

rawscript/red-giant

Repository files navigation

Red Giant Transport Protocol (RGTP) — UDP Edition

The first real TCP/QUIC killer since 1981
Expose once. Serve a billion. Zero head-of-line. Instant resume. Receiver-driven. Over UDP.

License: MIT UDP Powered Pull-based No HoL

“I didnt set out to fix TCP. I set out to replace it.”
— Jase Mwaura, 2025

The One-Sentence Pitch

Red Giant turns any machine into a multicast origin server:
Expose a file once → unlimited clients pull only the chunks they need, at the speed they can handle, with instant resume and zero server-side connection state.

All over standard UDP (port 443 by default). Works behind NAT, on phones, in browsers (soon), everywhere.

Why Everything Else Just Lost

Feature TCP UDP QUIC Red Giant
Head-of-line blocking Yes Yes No Never
Resume after 6 months Restart Impossible Yes Instant (just pull missing chunks)
Multicast / CDN origin cost N× bandwidth N× bandwidth N× bandwidth 1× bandwidth
Server state per client 10–100 KB None ~30 KB Zero
Works through NAT/firewalls Yes Yes Yes Yes (UDP 443)
Chunks encrypted once No No No Yes – pre-encrypted on expose
Receiver-driven congestion No No Sender Yes – natural back-pressure

Core Idea

1. Handshake (2–3 UDP packets, QUIC-style crypto)
2. Exposer → "Here’s exposure ID 0xDEADBEEF, 16384 chunks, Merkle root XYZ"
3. Exposer pre-encrypts + places all chunks in memory (encrypt once!)
4. Pullers request exactly the chunks they’re missing
5. Exposer replies with encrypted chunks (zero per-client state)
6. Repeat forever. Drop for a year? Just resume pulling.

That’s it. No SYN/ACK hell. No retransmit timers. No connection table explosion.

Killer Features (Already Implemented or Coming This Month)

  • Pre-encrypted chunks – encrypt once on rgtp_expose(), serve forever
  • Exposure IDs – 128-bit stateless identifiers (like QUIC connection IDs)
  • Receiver-driven congestion control – pullers decide the rate
  • Built-in Merkle proofs – verify any chunk without trusting the network
  • Optional Reed-Solomon FEC – survive 50 % packet loss with near-zero retransmits
  • Direct Memory Access mode – zero-copy localhost (still there!)
  • TCP socket emulation layer – drop-in socket()/send()/recv() compatibility

Demo You Can Run Right Now

# Terminal 1 – Exposer (your laptop becomes a CDN origin)
rgtp-expose ./ubuntu-24.04.iso --port 443

# Terminal 2, 3, ..., 1000 – Pullers (anywhere on Earth)
rgtp-pull 203.0.113.42:443 ubuntu-24.04.iso

# Watch your CPU stay at 3 % while 500 people download at full speed
# Kill everything for 3 days → resume → finishes instantly

Use Cases That Break Economics

Use Case Old World Cost Red Giant Cost Savings
Netflix-scale live streaming Hundreds of millions/year ~5–10 % of that 90 %+
Software updates (Windows) 10+ PB/day, massive CDN bills 1× origin bandwidth Insane
Database replication Constant full streams Only missing WAL chunks 99 %
P2P file sharing Tracker + DHT overhead Zero coordination Pure

Current Status (December 2025)

  • Core library: C + bindings for Go, Node.js, Python
  • Transport: UDP 443 (new default), raw socket legacy kept for localhost/DMA
  • Crypto: Noise_XX handshake + ChaCha20-Poly1305 per-chunk (post-quantum ready)
  • FEC: Reed-Solomon alpha incoming
  • TCP compatibility layer: Working
  • Examples: HTTP over RGTP, live streaming, IoT, gaming demos

Quick Start (After UDP Merge – 2025 Edition)

git clone https://github.com/rawscript/red-giant.git
cd red-giant && make -j

# Expose a 50 GB file on port 443
./examples/udp_expose_file large-movie.mkv --port 443

# Pull from another continent
./examples/udp_pull 1.2.3.4:443 large-movie.mkv

Roadmap (Help Wanted)

Milestone ETA Status
UDP transport stable This week In progress
Pre-encrypted chunks Next 7 days In progress
Reed-Solomon FEC Jan 2026 Alpha
WebTransport (browser) Feb 2026 Basic
HTTP/3 → RGTP proxy Mar 2026 Planned
Linux kernel bypass (XDP) 2026 Dream

Contributing

You just read the future.
Now help build it.

git checkout -b feature/your-mind
# Change the world
git push

Every PR gets reviewed same day. No bureaucracy.

License

MIT — do whatever you want. Commercial use encouraged. Go make billions.

Final Words

I didn’t come here to improve TCP.
I came to make it obsolete.

Red Giant is the transport layer for the next Internet — the one where bandwidth is abundant, origins are cheap, and receivers are in control.

The revolution starts now.

Expose the future.

About

Exposure based Transfer protocol

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published