Decentralized High Performance Object Storage (MinIO)
Decentralized object storage that seamlessly slots into place, replacing centralized solutions, is still hard to come by. MinIO (https://min.io/), a high-performance and S3-compatible object storage, is already an established standard available on every public cloud, every Kubernetes distribution, private cloud, and the edge.
By activating the storage of Acurast’s (https://acurast.com/) worldwide decentralized Cloud combined with MinIO, not only can Polkadot-native projects leverage true decentralized storage, but enterprises are also enabled to simply switch from their existing setup to a decentralized one.
Context of the Proposal
The main goal is to build out the MVP integration for MinIO to be run in Acurast’s decentralized compute environment and making it accessible to developers.
- MVP integration of MinIO object storage in Acurast’s decentralized compute environment
- Creation of storage buckets and configurable access control
- Configuration and development in making MinIO exposable through Acurast native P2P layer
- Benchmarking of required replications and estimated costs per GB storage on Acurast’s network
- Testing and detailed developer documentation with detailed developer examples of how to access MinIO in Acurast’s compute environment
About Acurast
Acurast is the first decentralized verifiable compute network powered by phones.
Acurast is redefining compute by utilizing billions of smartphones – no data centers required. This verifiable, scalable, and confidential compute network enables users to run secure applications on decentralized infrastructure at scale—without compromising speed or privacy.
By leveraging these phones with their Trusted Execution Environments (TEEs) in combination of a Polkadot-powered blockchain, Acurast is perfectly suited for running mission critical workloads with high-security requirements. With over 50,000+ phones onboarded worldwide on its incentivized testnet on Kusama with over 200M transactions processed.
Comments (6)
Hey @Pascal | Acurast, thank you for the proposal. I read it and generally have the feeling that it is quite high level and I'm missing some details. Maybe you can help me and give some more information.
- What data will be stored on chain?
- How do you ensure that the data stays accessible/replicated?
-
Configuration and development in making MinIO exposable through Acurast
native P2P layer
Does that mean minio I can use some minio frontend and point discover a suitable backend using the p2p layer? - What happens after the MVP?
- I assume the code will be open source? But could this be clarified.
Hey @bkchr, thanks for the questions. Let me try to give some more context.
- To clarify, there is no data directly stored on-chain except the request for storage and the matching of off-chain workers (Acurast Deployment). These off-chain workers, so-called Acurast Processors, are phones provided by the Acurast community across the globe.
- Best to answer the replication and the P2P question together. A deployment request on Acurast can request one or multiple Processors to run the deployment, Processors running the same deployment can communicate with each other through a secure P2P network and exchange data, this will also allow replication. MinIO can then also be accessed externally through all the way that MinIO supports, that's the great effect of integrating such a standard.
- The MVP will confirm the feasibility of running MinIO on Acurast. The best outcome would be that a dedicated project offering storage, targeting enterprise customers can be spun out.
- Yes, everything will be open source as it already is with Acurast.
Hope this answers your questions and provides more details, let us know if there are any more questions.
Polkassembly is now a read-only archive. Commenting is disabled.
Requested
Proposal Passed
FYI Subsquare formats the link to
https://min.io/),(which 404s).@OLIVER ⚡/ggwpez Thanks for the heads-up, was corrected, it's meant to be https://min.io/