Knowledge Base
Security and Reliability Model for Storage
Security and Reliability Model for Storage
ObjectID Storage is designed around verifiable content, controlled on-chain actions and independent oracle execution. It improves reliability compared with a single upload server, but it should still be understood as decentralized infrastructure with explicit operational limits.
Integrity checks
- The upload flow computes a SHA-256 hash before the oracle task is created.
- The oracle task can validate declared file size and expected hash.
- IPFS CIDs are content-addressed: if the file changes, the CID changes.
- Storage objects retain file metadata, oracle task references and lifecycle changes for auditability.
Access and authorization
Storage object operations require the user’s identity controller capability. Move functions check ownership by DID before updating metadata, pin results, deletion status or retention. The backend also validates sponsored transaction contents and only accepts allowed storage Move calls.
Oracle independence
Storage work is delegated to IOTA Distributed Oracle nodes. Nodes are independent execution actors and the storage task specifies requested nodes and consensus expectations. This reduces reliance on a single backend and creates a separation between the ObjectID interface and the execution layer.
Reliability checks
- The Storage API can query whether a CID is pinned by the configured IPFS API.
- Provider lookup can use delegated routing or IPFS RPC to count visible providers.
- Gateway availability is checked with a range request against the configured gateway.
- Node rotation and repeated retention tasks reduce dependency on a single IPFS node or provider.
Important limits
ObjectID Storage improves resilience but does not make IPFS availability absolute. Gateway outages, task failures, expired retention, insufficient credits, network issues, unlawful content handling or third-party infrastructure problems can still affect access. The legal limits are described in the Storage Service Addendum and the IOTA Distributed Oracle EULA.