Introduction
Project Name: Lume Web - LBRY Integration
Name of the organization or individual submitting the proposal: Hammer Technologies LLC
Describe your project.
LBRY is a content sharing platform where files are shared peer-to-peer. A major issue is that content can become unavailable and be lost forever if no one is actively sharing it.
This project will integrate LBRY with Sia through the Lume Web portal. This will allow the Sia network to act as a decentralized storage cloud for LBRY content, ensuring files remain consistently available for download even when no peers are online.
A key thing to note is that this integration focuses only on storing the LBRY file data itself. It does not involve interacting with the LBRY blockchain, and therefore does not violate the grants that require integration with non-Sia blockchains rule.
How does the projected outcome serve the Foundation’s mission of user-owned data?
True data ownership requires that your files are safe from being lost. Currently, LBRY creators risk their content disappearing, which undermines their control and ownership.
This project solves this by using Sia to ensure LBRY content remains persistent and reliably available. This provides LBRY creators with a complete solution for data ownership while bringing their entire creator economy and its storage needs to the Sia network.
We cannot provide grants to residents of jurisdictions under increased FATF monitoring, those that have active OFAC sanctions, or those that fail our bank compliance tests. We also cannot provide grants if your payment bank account is located in those same locations. Please review the following list.
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 reasonable breakdown of expenses: $10,000
- $9,330 - 2 months Developer fees for Derrick Hammer
- $670 - R&D Infrastructure
What are the goals of this small grant? Please provide a general timeline for completion.
- Month 1 (October, due 11/2/25): Build the protocol integration and the API
- Tasks:
- A new go library will need to be made based off the guts of GitHub - LBRYFoundation/reflector.go that will act as the foundation of the protocol backend support
- A portal plugin
portal-plugin-lbrywill be made - Testing of the protocol integration and the various ways to pin data
- Validations for this milestone will include:
- Being able to pin a blob from the network over REST API
- Being able to unpin a blob from the network over REST API
- Being able to upload a small file as a blob and access it with LBRY CLI tools
- Being able to upload a large file as a blob and access it with LBRY CLI tools
- Being able to use LBRY tools to upload a blob to the portal using the LBRY native reflector protocol. This will require supporting device (IP based) whitelisting in the API (and GUI in Month 2).
- All validations will be presented in the form of a CLI-based demo repo with instructions on testing each validation.
- Tasks:
- Month 2 (November, due 12/2/25): Build the frontend integration
- Tasks:
- Add LBRY as support for uploading data in the upload manager as a storage option
- Add a pinning interface support for LBRY blobs
- Add an
approved device listinterface support so that LBRY blobs can be uploaded via thereflector protocoland correctly associated to an account. - Testing functions and no obvious UX problems
- Validations for this milestone will include (UI focused):
- Being able to pin a blob
- Being able to unpin a blob
- Being able to upload a small file
- Being able to upload a large file
- Being able to use LBRY tools to upload a blob and see it show up in the blob list. Instructions for this validation will be provided in a demo repo.
- Tasks:
- All milestones will be testable at/against
pinner.xyz
Potential risks that will affect the outcome of the project:
- Any unexpected technical issues with the reflector protocol or other foundational LBRY P2P components.
- Any potential governance issues around cooperation with LBRY and the LBRY Foundation (
lbry.org). This isn’t likely.
Development Information
Will all of your project’s code be open-source? Yes
Leave a link where code will be accessible for review.
Do you agree to submit monthly progress reports? Yes
Contact info
Email: [email protected]