[Small Grant] RelayStream: Native Sia-renterd Media Orchestration & Ingestion Engine

Grants Proposed
1

[Small Grant] RelayStream: Native Sia-renterd Media Orchestration & Ingestion Engine

Introduction

Project Name: Open-STRM Ingestion Engine (for RelayStream)

Applicant: Michael Lipson | Val IT Tech Solutions

Contact: [email protected] | X: @RelayStream_net

GitHub: GitHub - tvmateocmd-design/open-strm-standard: An open-source framework for orchestrating high-speed 'Relay Tunnels' between Solana and DePIN networks (Sia, Theta, RENDER). · GitHub

Background:

Lead Systems Architect with a track record in real-time data synchronization. Previously developed the EMS Companion App (linked below), orchestrating high-velocity data via Firebase. Current focus: The Open-STRM Indexing Standard, designed to eliminate the “Latency Paradox” of decentralized media streaming.

Project Description:

The Open-STRM Ingestion Engine is an automated bridge that moves Hollywood-grade 4K media from raw storage to the Sia network. It transmuxes heavy video files into HLS-compatible segments and utilizes the Sia renterd SDK to automate contract creation and encrypted chunk distribution. This eliminates the need for manual orchestration, allowing creators to host professional video libraries on Sia with a single command.

Mission Alignment:

This project directly serves the mission of user-owned data. By replacing centralized cloud giants (AWS/GCP), we empower creators to hold their own storage contracts directly. RelayStream solves the “Storage Latency Paradox” by combining Sia’s cost-effective storage with 0G Aristotle’s high-speed indexing.

Grant Specifics

Amount Requested: $10,000 USD

Architecture Components:

  • Component A - The Transmuxer: Automated FFmpeg pipeline that slices 4K MKV content into encrypted .ts HLS segments. (Status: Milestone 1 Proof complete—229 chunks created).

  • Component B - renterd Bridge: A Node.js service utilizing the Sia SDK to automate bucket creation, contract funding, and segment uploading.

  • Component C - Integrity Layer: 0G Merkle Root anchoring (0x2e6ac921b62d2) to provide tamper-proof verification for segments in transit.

  • Component D - Discovery Standard: Documentation of the Open-STRM standard for ecosystem-wide adoption of Sia-hosted video.

Security Best Practices:

We utilize Sia’s native encryption-at-rest. The engine is non-custodial; the creator retains full authority over private keys and storage contracts. Cross-network integrity is enforced via Merkle Root commitments.

Goals & Timeline:

  • Month 1 (Foundation): Finalize HLS-to-renterd uploader module logic. (Success: Confirmed Sia uploads via SDK).

  • Month 2 (Data Layer): Implement automated contract renewal and segment redundancy checks.

  • Month 3 (Standardization): Public release of Ingestion Engine, Open-STRM documentation, and public MIT repo.

Risks & Mitigations:

  • Sia Host Volatility: Mitigation via Reed-Solomon erasure coding (30/10) managed by renterd Autopilot.

  • Network Latency: Mitigation via 0G Aristotle indexing for sub-500ms segment retrieval.

Development Information

Open Source: Yes, released under the MIT License.

RelayStream Repo: GitHub - tvmateocmd-design/open-strm-standard: An open-source framework for orchestrating high-speed 'Relay Tunnels' between Solana and DePIN networks (Sia, Theta, RENDER). · GitHub

Proof of Shipping (EMS): https://github.com/tvmateocmd-design/EMS_Overlay_MASTER_FINAL

Screenshot (578)
Screenshot (578)1931×1080 208 KB

Monthly Reports: I agree to submit monthly reports to the forum.

2

Continuing on our short chat on the forums;

You said you are planning to use the Go SDK to interact with Renterd. The SDK is for Indexd, not Renterd.

On top of that, Renterd proposals are no longer accepted as per the new guidelines.

Why not use the autopilot for this? In your risks you’re mentioning using the Autopilot.

Your screenshot shows minting NFT’s on Solana, what’s the purpose of this? To add to this; building on top of other chains is also not funded.

1 Like
3

I have seen various spins of this over the years that can be seen in past proposals. as far as I can see your trying to create a media transcoder system that sends all data to Sia.

That idea alone IMO isn’t exactly bad, but the whole proposal is based around outdated assumptions and would need to be honestly binned and re-thought for how indexd works…

And broadly this type of thing would have to be self-hosted since doing media pipelines in the browser would not be a good idea as this lands in cloud/SaaS infra territory due to the compute needed… For the user to be in full control and not compromise their account (non custodial), it would have to be their infra running anything

Additionally you left out who the target user is and what your plans are for the project.

See Small Grant Proposal Template | Sia.

1 Like
4

HI @relaystream - welcome to the Sia community! Please let me know when the above from other community members has been addressed so this proposal can be re-reviewed - especially when the missing elements of our Small Grant Proposal template have been included.

We’ve reached capacity for next week’s Grants Committee meeting, so this proposal will need to be edited by May 20th to be considered for review at the next meeting on May 26th.