StorageHub’s Codebase Audit
Beneficiary:What is StorageHub?
As part of the Decentralized Futures program sponsored by the Web3 Foundation, Moonsong Labs has been awarded a grant to develop the open-source codebase for a decentralized storage solution, optimized for larger data sets and file-based storage, that has been affectionately dubbed “StorageHub”. StorageHub is designed to integrate seamlessly with Polkadot’s native functionalities, promoting robustness, scalability, and interoperability.
Why StorageHub?
- Seamless Integration: Unlike current solutions that require complex setups or rely on external systems, StorageHub's design aims to offer a fully integrated, native experience within Polkadot.
- Dual Provider Model: Introduces Main and Backup Storage Providers, enhancing flexibility and ensuring data unstoppability without compromising on decentralization.
- Simplified Payments: Through continuous payment streams, StorageHub's design seeks to simplify the user experience, balancing the ease of one-time payments with sustainable, incentive-aligned ongoing contributions.
- Community and Ecosystem Growth: StorageHub's codebase not only aims to serve as a foundational infrastructure for storage, but also seeks to support the growth of the Polkadot ecosystem by hopefully providing a platform for innovative decentralized applications.
Proposal Overview:
As engineers, we strongly believe that auditing new code is not only best practice, but that is also in Polkadot’s best interest. Audits were not funded under the Decentralized Futures grant and therefore this proposal specifically seeks funding for the audit of this decentralized storage codebase. This audit, conducted by SRLabs, a leader in blockchain security, is essential to ensure that StorageHub's codebase meets the highest standards of security and reliability. This collaborative effort with SRLabs highlights our commitment to best practices in engineering and our dedication to enhancing Polkadot's infrastructure.
Engage with Us:
- Read the Full Proposal: For a detailed understanding of the context of this proposal, the identified problem, and StorageHub's ideas to solve it, read our full draft proposal here.
- Explore More: For technical details and ongoing updates, check out our GitHub repository here (currently under development).
- Learn About Moonsong Labs: Discover more about our team and our vision on our website.
- Learn About SRLabs: Security Research Labs is a cybersecurity consultancy committed to making the world more secure. Discover more about them on their website.
We Need Your Feedback:
How can we improve our proposal? What features do you believe are most critical for StorageHub's codebase? Your input will help us refine our approach to better serve the Polkadot community.
Comments (8)
Proposal Passed
3
of 3Summary
0%
Aye
0%
Nay
Aye (37)0.0 DOT
Support0.0 DOT
Nay (42)0.0 DOT
Voting Data
Approval%
Support%
Threshold0.00%
Threshold0.00%
Comments (8)
With Crust, we would already have had a working solution, which we rejected. Instead, the treasury funded the building of a separate storage solution and is now asking for a ridiculous amount to do an audit.
Technical proposal appears sound and well-structured. Seems like a Polkadot native alternative for GCP buckets storage with distributed providers. It won't really mention much about encryption of the data so I expect that is left to app/service developers to be done in clientside/frontend.
Potential use case could be enabling chains and services to back up their data on StorageHub during longer periods of inactivity, thereby avoiding pruning (which might occur after 28 days) and preserving their existence. It's good to note that with JAM, every account in the ecosystem will function as a programmable service account, which should radically increase users' ability to take full advantage of this storage option.
With Crust, we would already have had a working solution, which we rejected. Instead, the treasury funded the building of a separate storage solution and is now asking for a ridiculous amount to do an audit.
Technical proposal appears sound and well-structured. Seems like a Polkadot native alternative for GCP buckets storage with distributed providers. It won't really mention much about encryption of the data so I expect that is left to app/service developers to be done in clientside/frontend.
Potential use case could be enabling chains and services to back up their data on StorageHub during longer periods of inactivity, thereby avoiding pruning (which might occur after 28 days) and preserving their existence. It's good to note that with JAM, every account in the ecosystem will function as a programmable service account, which should radically increase users' ability to take full advantage of this storage option.