← Back to Docs Index

ObjectID Storage Overview

ObjectID Storage is the ObjectID service dedicated to IPFS-oriented file persistence. It lets a user upload a file, create an on-chain OIDStorageObject, and request decentralized storage work through the IOTA Distributed Oracle.

What the service does

• Accepts a temporary file upload through the ObjectID Storage backend.
• Computes and records the file metadata, including file name, MIME type, size and SHA-256 hash.
• Creates an on-chain storage object linked to the user’s DID and ObjectID controller capability.
• Creates or references an IOTA Distributed Oracle task of type STORAGE.
• Uses oracle nodes to fetch the temporary payload, verify it, and persist it on IPFS.
• Stores the resulting IPFS CID and gateway information in the storage lifecycle.

Main components

• ObjectID Storage dApp: user interface at storage.objectid.io.
• Storage API: temporary upload, sponsored transaction support and IPFS status checks.
• OID_STORAGE_CREDIT: credit token consumed when creating or extending storage tasks.
• OIDStorageObject: on-chain object containing file metadata, oracle references, CID, retention status and change log.
• IOTA Distributed Oracle: decentralized execution layer used for IPFS storage tasks.
• IPFS: content-addressed storage layer where the file is pinned and retrieved by CID.

Storage is not a simple upload

The uploaded file is only temporarily held by the ObjectID backend. The persistent reference is the IPFS CID produced by the oracle storage flow. This distinction is important: the temporary upload URL is an input to the oracle task, while the CID is the durable content address used after pinning.