---
# System prepended metadata

title: Decentralized Storage Evaluation
tags: [v3]

---

---
tags: v3
---

# Decentralized Storage Evaluation

## Different Solutions


## Current data storage solutions

##### Dao metadata
- data stored in airtable db
    - crud via serverless function apis
    - web3 signature of dao member required for updates 
- formatted and dropped into json in s3 buckets 
    - for easy access
    - gets around airtable rate limits
    - serverless functions jobs format and create the json
- data scope
    - general dao metadata
    - boost activation data
        - isActive
        - boost metadata
    - audit log tracking who made each update

API/Serverless function can easily be updated to use different storage solutions.



## Things to explore

### Textile
https://www.textile.io/
- s3 bucket alternative

### Ceramic
- ceramic spec: https://hackmd.io/L5oDlMepS72aR-04kSV7kw

### Arweave

#### Client Libraries
- Go
- PHP
- Scala
- Javascript/Typescript/Node

#### Description
- A seperate blockchain that stores data. The blocktime is about 2 minutes. Meaning it will take at least 2 minutes for persistance. There are storage limits for data to be indexed it seems like greater than [250mb](https://github.com/Bundlr-Network/arbundles) could be an issue.
- Login and authentication is handled by arweave's wallet.

#### Pros
- Many client libraries
- Blockchain gurantees persistence

#### Cons
- Long wait time for persistence
- Possible data limits


### Stoj

#### Client Libraries
- Go
- C
- Java
- Node
- Android

#### Description
- When files are uploaded they are encrypted,split into many chunks, and then distributed across the network. Data ownership does not seem user based, but more application based. There also seems to be no frontend authentication system.
- [Node Stats](https://storjstats.info/d/storj/storj-network-statistics?orgId=1)


#### Pros
- Data encrypted by default
- Easy integration with S3
- Cheap $4 per terabyte per month
- 

#### Cons
- No Discord Server
- No frontend authentication system for users
- Data owned by application

### Skynet


#### Client Libraries
- Javascript


#### Description
- Built on top of the Sia network, and allows for easier integration with that ecosystem.
- It has the concept of a a user account that gives a user single sign on and they can access their data
- There is a concept called portals where an individual needs to pay to access specific pieces of data
- All data is encrypted by default
- 


#### Pros
- Supports a static content hash that can point to a dynamic content hash
- Has a concept of single login


#### Cons
- Seems to be in earlier stages compared to IPFS
- Uncertainty around how all these pieces come together in an application
- It does not look like they have document schema support


### 0chain

- Documentation seems sparse

### Swarm



#### Client Libraries
- Javascript
- Go


#### Description
- Very similar to the other existing solutions. There are a network of bee nodes that hadle file storage, and we can upload/download files and directories.

#### Pros
- Nothing really over the mentioned solutins above

#### Cons
- Client libraries mention they are still in Beta


### OrbitDB

- Package mentions the project is still in alpha

### Aleph.im
- Python
- Javascript


#### Description
- Very interesting, has its own storage solution, but also a computation solution
- Data can be queried and stored in different formats

#### Pros
- Has computation solution and could probably replace lambda

#### Cons
- Currently has around 69 nodes
- Doesn't directly integrate with xDAI

### IPFS

- Too low level to use directly



## Resources

- https://ethereum.org/en/developers/docs/storage/
- https://www.youtube.com/watch?v=dadc3iySlsc