Large Grant: Fabstir Web3 Media Player #3

Grants Rejected
6

Large Grant Proposal

Introduction

Project Name: Fabstir Web3 Media Player #3

Name of the organisation submitting the proposal: Fabstir

Describe your project:

Fabstir Media Player is entering a new phase focused on bringing real-world adoption whilst helping to ensure S5 scales effectively with production use cases. The primary objectives are to increase adoption of Sia.tech’s decentralised storage and develop additional software integrations for Sia within Web3.

The project will:

  • Develop an OrbitDB storage adapter for Sia to enable decentralised graph database capabilities
  • Implement comprehensive S5 network scalability testing and integration
  • Create backup/sync functionality using S5 for transcoder and AI
  • Undergo security audits and implementation for MetaMask Snaps marketplace listing

Previous grant proposals: #1 and #2

Who benefits from your project?

  1. Sia ecosystem:

    • Expands Sia’s presence in Web3 through production-ready OrbitDB integration
    • Provides proven scalability testing of S5 network with real-world video streaming use cases
    • Demonstrates Sia’s capability to handle enterprise-grade workloads through film festival platform
    • Positions Sia as viable alternative to IPFS, particularly for media streaming where IPFS struggles
    • Introduces Sia to MetaMask’s 30+ million monthly active users through Snaps marketplace
    • Brings professional filmmakers and content creators to Sia for transcoding and archiving content
    • Create reusable open-source tools for Sia integration that other developers can leverage
    • Provides documented performance benchmarks for enterprise-level storage solutions
    • Expands Sia’s utility through AI search capabilities built on its storage
    • Attract NFT marketplace users through support for movie-length video NFTs
    • Helps establish Sia in the entertainment industry through support of multiple video formats
    • Creates a bridge between traditional content platforms and Web3 through Sia storage
    • Increases Sia network usage through peer-to-peer video streaming
    • Demonstrate Sia’s cost-effectiveness compared to traditional cloud storage for media

  2. Content creators and distributors:

    • Professional filmmakers and music creators gain decentralised distribution
    • Automated transcoding to multiple formats/resolutions
    • Content distribution companies can leverage Web3 capabilities
    • Content creators get enhanced ownership controls
    • Integration with existing NFT marketplaces
    • Access to decentralised subscription marketplaces for permissionless access
    • End-to-end encryption and cost effective redundancy backup options

  3. Web3 developers:

    • Access to documented Sia integrations
    • Open-source tools for building on Sia
    • Enterprise-ready distributed database solutions
    • MetaMask Snaps integration examples

  4. End users:

    • Enhanced media streaming capabilities
    • Improved content discovery through AI search
    • Better data ownership and control
    • Simple onboarding to Web3 through social login (Gmail, Git, Discord, etc.)
    • Cross-device access to content library
    • Transparent content ownership through NFTs without technical barrier

How does the project serve the Foundation’s mission of user-owned data?

The project advances user-owned data by:

  1. Decentralised Storage:

    • Stores media content on Sia network
    • Enterprise-grade graph database storage of data to Sia storage
    • Enables user control of encryption keys
    • Provides redundant storage across nodes
    • Allows direct content retrieval via advanced indexing and S5

  2. Data Sovereignty:

    • Selective data sharing permissions
    • Private key-based access control
    • Control of permissionless and permissioned access to markets
    • Self-hosted node options
    • Users maintain control of their AI search indices

  3. Open Standards:

    • Implements NFT standards for ownership
    • Uses open-source storage protocols
    • Provides transparent data formats
    • Enables data portability

Are you a resident of any jurisdiction on that list? No

Will your payment bank account be located in any jurisdiction on that list? No

Grant Specifics

Amount of money requested and justification with a comprehensive breakdown of expenses:

Total requested: $124,940 for 12 months

Detailed breakdown:

Item Cost ($) Justification
Full-stack Web3 developer 85,000 Primary development of all components
UI developer and designer 4,000 Interface design and implementation
Devops engineer and support 5,000 Cloud infrastructure management
AI developer 2,000 AI integration specialist
Security Audits & Implementation 14,000 Professional security auditing
GPU & CPU cloud 11,940 Infrastructure costs detailed below
Software licences & tools 1,000 Development tools and services
Legal/accounting 1,000 Compliance and financial management
Contingency 1,000 Buffer for unexpected costs

GPU & CPU Cloud Cost Breakdown:

  • GPU cloud (NVIDIA A16): $350/month × 6 = $2,100
  • GPU cloud (NVIDIA L40S): $1,220/month × 6 = $7,320
  • Cloudflare Business: $250/month × 7 = $1,750
  • Hetzner EX101: $100/month × 7 = $770

Timeline with measurable objectives and goals:

Q1 (Months 1-3): Foundation Development

Month 1:

  • Complete OrbitDB adapter architecture design
  • Implement basic S5 streams integration
  • Set up initial testing framework for S5 network
  • Implement core OrbitDB operations with S5

Month 2:

  • Complete OrbitDB-S5 conflict resolution
  • Begin smart contract security improvements
  • Complete radix tree implementation

Month 3:

  • Finish initial security audit phase
  • Begin MetaMask Snap security enhancements
  • Optimise OrbitDB performance

Q2 (Months 4-6): Integration & Testing

Month 4:

  • Deploy load testing infrastructure
  • Implement analytics monitoring
  • Scale testing with concurrent users
  • Improve backup/restore mechanisms
  • Implement feedback from security audits

Month 5:

  • Complete MetaMask Snap marketplace requirements
  • Switch from Base Sepolia testnet to Base Mainnet
  • Implement advanced analytics features
  • Complete integration testing phase
  • Implement feedback and fixes from real-world short film festival

Month 6:

  • Set up hosted Sia node
  • Set up hosted S5 node
  • Finalise security monitoring dashboard
  • Real-world deployment testing for movie-length 4K

Q3 (Months 7-9): Optimisation & Scaling

Month 7:

  • Complete production deployment for L40S cloud infrastructure
  • Complete security post-audit implementation
  • Fine-tune pod load balancing
  • Optimise streaming performance
  • Deploy production monitoring systems

Month 8:

  • Deploy AI search engine backup system
  • Implement AI vector embeddings sync
  • Integrate versioning system for AI backups
  • Enhance AI search pod synchronisation

Month 9:

  • Help and support for film industry participants
  • Test full system under load
  • Implement feedback and fix any issues

Q4 (Months 10-12): Production & Documentation

Month 10:

  • Start comprehensive documentation
  • Finalise all security implementations

Month 11:

  • Complete all documentation
  • Address any remaining issues
  • Final system optimisation

Month 12:

  • Overall maintenance, scaling and security tasks

Potential risks that will affect the outcome of the project:

Technical Risks:

  • S5 network performance under concurrent load is untested at scale
  • Integration complexity between OrbitDB and S5 streams
  • MetaMask Snaps marketplace approval timeline uncertainties
  • AI model integration complexity with distributed storage

Operational Risks:

  • GPU cloud costs may fluctuate based on market demand
  • Resource allocation for concurrent transcoding loads
  • Timeline dependencies on third-party security audits
  • Initial user adoption rate uncertainties

Mitigation Strategies:

  • Comprehensive testing framework implementation
  • Staged rollout of features with monitoring
  • Regular communication with S5 author Redsolver
  • Flexible architecture allowing rapid adjustments

Development Information

Will all of your project’s code be open-source?

Yes, all code developed for this grant will be open-source and available on GitHub under MIT licence. The project uses some closed-source components (ffmpeg for transcoding, MetaMask for wallet integration) but all code developed will be open-source.

Leave a link where code will be accessible for review:

Do you agree to submit monthly progress reports?

Yes, I agree to submit monthly progress reports in the forum following the required format.

Do you agree to designate a point of contact for committee questions and concerns?

Yes. Jules Lai (Founder and CTO of Fabstir) will be the primary point of contact.

Provide links to previous work or code from all team members:

Previous Sia grant work:

Monthly progress reports:

Have you developed a proof of concept for this idea already?

Yes. The Fabstir Media Player is already operational and was developed under previous Sia grants. This proposal builds upon that foundation to scale the implementation and add new capabilities. Previous work can be seen in the monthly progress reports and GitHub repositories linked above.

Do you agree to participate in a demo at our monthly community call at significant milestones or after the grant’s completion?

Yes, I agree to participate in a demo at our monthly community call at significant milestones or after the grant’s completion.

Contact Info

Email: jlai[at]fabstir.com

Any other preferred contact methods:
Telegram: Telegram: Contact @JulesL78