Data Asset Storage Options

You choose where you want to store your Data, the Itheum Protocol does the rest!

Ultimately, you can store your data anywhere you choose to and the Itheum protocol does not mandate or require any specific storage solutions. You can choose to mint Static (files that never change) or Dynamic (files that change and evolve), store them centrally on services like AWS S3 and use domain/DNS services like CloudFlare, or use decentralized storage and naming technology like IPFS, Arweave, IPNS, DNSLink, etc. The choice is yours! After you store your data, you will need to make sure that your data assets are publicly available via (what the Itheum protocol refers to as) a Data Stream URL. There are some specific rules your Data Stream URL will need to follow and we will explore them in the next section. To get you started in your Data Asset storage journey, you can pick some recommended options below and follow our guides to get you started.

1) Zedge Storage

Decentralized DYNAMIC/STATIC Storage

Seamless decentralized static and dynamic Data Stream storage for your Data NFTs.

Read Guide:

2) AWS S3 + CloudFlare

Centrazlied DYNAMIC/STATIC namic Storage Use AWS S3 to store your data and CloudFlare as a DNS service to public your Data Stream URLs.

Read Guide:

3) Akord via Akord

Decentralized STATIC Storage

Use Akord to store static files on Arweave. Read Guide: Arweave - Akord

1) MultiversX Native Auth Protected API

Centralized protectected DYNAMIC Storage

Run a web server and implement an authentication and authorization-enabled Data Stream URL. Perfect for complex web3 infrastructure use-cases like loyalty cards, XP systems, data vaults, etc. Read Guide: MultiversX Native Auth Protected API

Last updated