ADO Idea Proposal - Decentralized Storage Contract
Contact Information
Name: (MK)
Discord: (-)
Email Address: (-)
ADO Summary - What is the goal of this ADO and how does it function?
The goal of this ADO is to provide a secure and trustless storage contract that allows users to store data on decentralized storage networks. The ADO will support three storage options: Arweave and IPFS (potentially with pinning capabilities). Users will be able to upload data to the contract, specifying the desired storage network. The contract will handle interactions with the chosen network, ensuring data integrity and accessibility.
Does it need to work with another ADO or is it standalone? Also, does it implement any modules?
This ADO is primarily standalone, but it could potentially benefit from modules like Rates to allow for charging fees for storage services.
Are you planning to build this ADO yourself, or will it be developed by the Andromeda team?
(myself)
Credits/Associations - Is this ADO based upon a previous project or ADO or in partnership with any other groups or developers? If so, please list here and provide a link if possible.
ADO Flow Breakdown - Please list and provide descriptions of each step in the ADO flow sequence (show us how to work with the ADO and associated workflow, visuals are great here):
Instantiation:
Define the owner of the contract.
(Optional) Define the address of an external Rates contract if charging fees is desired.
Execution:
Upload Data: Users send a message containing the data to be stored and the desired storage network (Filecoin, Arweave, IPFS).
Retrieve Data: Users send a message with the data identifier (hash) to retrieve the stored data.
Update Storage Network: (Optional) The owner can update the storage network (e.g., from Filecoin to Arweave) for existing data if desired.
Queries:
Data Exists: Check if a specific data hash is stored.
Get Data Size: Retrieve the size of stored data.
Get Storage Network: Retrieve the network being used for a specific data hash.
Get Storage Cost: (Optional) If a Rates module is used, query the cost of storing data for a specific network.
Considerations/Concerns - What factors should be considered to mitigate risk of misuse, abuse, or other unintended scenarios, if any?
Data Integrity and Tamper-Proofing: Implement mechanisms to ensure data integrity and prevent malicious modification.
Data Availability: The success of the ADO relies on the stability and availability of the underlying decentralized storage network. Consider strategies to mitigate network outages or failures.
Access Control: Implement robust access control mechanisms to restrict data access and prevent unauthorized modification.
Fee Structure: If using the Rates module, carefully design the fee structure to ensure fairness and sustainability.
Possible Next Iterations/Future Work - How can this ADO be further enhanced?
Additional Storage Networks: Support additional decentralized storage networks as they emerge.
Data Encryption: Implement data encryption before storing it on the blockchain for added privacy and security.
IPFS Pinning: Explore pinning mechanisms to ensure data permanence on IPFS.
Data Access Control: Implement granular data access control, allowing users to set permissions for different users or groups.
Any Dependencies or Third Party Integrations? (Ex. Will this ADO need to work with anything off chain, a different app, etc?):
Arweave API: Integration with the Arweave API for uploading and retrieving data.
IPFS API: Integration with the IPFS API for uploading and retrieving data.
ADO Idea Proposal - Decentralized Storage Contract
Contact Information
ADO Summary - What is the goal of this ADO and how does it function?
The goal of this ADO is to provide a secure and trustless storage contract that allows users to store data on decentralized storage networks. The ADO will support three storage options: Arweave and IPFS (potentially with pinning capabilities). Users will be able to upload data to the contract, specifying the desired storage network. The contract will handle interactions with the chosen network, ensuring data integrity and accessibility.
Does it need to work with another ADO or is it standalone? Also, does it implement any modules?
This ADO is primarily standalone, but it could potentially benefit from modules like
Ratesto allow for charging fees for storage services.Are you planning to build this ADO yourself, or will it be developed by the Andromeda team? (myself)
Credits/Associations - Is this ADO based upon a previous project or ADO or in partnership with any other groups or developers? If so, please list here and provide a link if possible.
This ADO could be inspired by existing decentralized storage contracts, such as the idea behind Storage Contracts on Filecoin though Filecoin is not Cosmos friendly, or Arweave's SmartWeave.
Can you provide any docs/articles/research that explains the main idea of the ADO and how/why it is used?
ADO Flow Breakdown - Please list and provide descriptions of each step in the ADO flow sequence (show us how to work with the ADO and associated workflow, visuals are great here):
Ratescontract if charging fees is desired.Upload Data: Users send a message containing the data to be stored and the desired storage network (Filecoin, Arweave, IPFS).Retrieve Data: Users send a message with the data identifier (hash) to retrieve the stored data.Update Storage Network: (Optional) The owner can update the storage network (e.g., from Filecoin to Arweave) for existing data if desired.Data Exists: Check if a specific data hash is stored.Get Data Size: Retrieve the size of stored data.Get Storage Network: Retrieve the network being used for a specific data hash.Get Storage Cost: (Optional) If aRatesmodule is used, query the cost of storing data for a specific network.Considerations/Concerns - What factors should be considered to mitigate risk of misuse, abuse, or other unintended scenarios, if any?
Ratesmodule, carefully design the fee structure to ensure fairness and sustainability.Possible Next Iterations/Future Work - How can this ADO be further enhanced?
Any Dependencies or Third Party Integrations? (Ex. Will this ADO need to work with anything off chain, a different app, etc?):