ObjectID features
Digital identity, digital twins, document lifecycle and decentralized storage.
ObjectID provides four complementary feature families for organizations that need anonymous domain-linked identities, verifiable events and resilient data availability across physical assets, GS1 supply chains, documents and files.
Digital Identity
Every user who can create an Object receives an anonymous digital identity linked to a domain, making creation private, meaningful and verifiable.
Digital Twins
Create digital counterparts for objects and GS1 resources, then attach lifecycle events that make identity, provenance and state changes verifiable over time.
Documents
Assign a unique ObjectID to a document, typically a PDF, and use it to trace editing, approval, release and revoke processes.
Storage
Upload files to IPFS through the IOTA Distributed Oracle, with independent nodes responsible for pinning, verification and retention.
Digital Identity
Every user who can create an Object is assigned a digital identity. This identity is the basis for trusted creation, ownership history and verifiable lifecycle actions across the ObjectID ecosystem.
It is anonymous by design, because trust does not come from exposing personal data publicly. It comes from cryptographic proof and from control of the linked domain, which reduces impersonation risk while preserving privacy.
Anonymous and secure
Creators operate through a pseudonymous identity that can sign actions and prove authorship without publishing unnecessary personal information. This makes the system secure while keeping the identity lightweight and privacy-preserving.
Linked to a domain
The identity is meaningful because it is linked to an Internet domain. A created Object is therefore tied not just to a generic wallet, but to a verifiable organizational context such as a company, brand, institution or authorized project.
Digital Twins
ObjectID digital twins connect a real-world or logical resource to a persistent digital identity. The identity can collect events, state transitions and proofs, creating a reliable history that applications, partners and users can inspect.
From a security perspective, each event is associated with a controlled identity and a verifiable timeline. This reduces the risk of silent data manipulation, makes unauthorized changes easier to detect, and gives every stakeholder a shared source of evidence for the asset history.
Generic Objects
Generic Objects are flexible digital twins for assets, components, devices or products that do not need a GS1 data model. They can receive custom events such as creation, inspection, ownership change, maintenance, transfer, certification or decommissioning. Event history helps prove who did what, when it happened, and which state was valid at that point in time.
GS1 Resources
GS1 Resources are designed for supply-chain contexts where standards matter. They can receive GS1 EPCIS events, enabling interoperable traceability for production, aggregation, shipping, receiving, transformation and other EPCIS business steps. Standardized event semantics improve auditability across organizations and reduce ambiguity during recalls, compliance checks or dispute resolution.
Documents
ObjectID Documents are digital twins of files such as PDFs. A unique identifier is assigned to the document and can be embedded directly inside it, so the document can carry a durable reference to its own trusted lifecycle.
- Track editing and review steps across contributors and systems.
- Register approval and release events for auditable publication.
- Record revoke events when a document must no longer be considered valid.
- Link every relevant version or proof to the same document identity.
- Use hashes and lifecycle events to detect whether a released document still matches the approved version.
- Give recipients a reliable way to distinguish valid, superseded and revoked documents.
Storage
ObjectID Storage lets users upload files to IPFS through the IOTA Distributed Oracle. The service creates an oracle storage task, validates the file through deterministic hashes and asks independent oracle nodes to persist the content on IPFS.
IPFS storage with oracle-backed retention
The storage flow is based on CID and SHA-256 verification, multiple independent IPFS nodes, and scheduled retention logic. Nodes can be rotated every 30 days, reducing dependency on a single IPFS provider while keeping the file addressable through its CID and auditable through ObjectID records. Learn more at iota-distributed-oracle.org.
Integrity by design
Files are verified through deterministic hashes and IPFS CIDs. If content changes, the identifier changes too, so tampering can be detected instead of being silently accepted.
Independent execution
The IOTA Distributed Oracle assigns storage work to independent nodes. This avoids relying on a single backend and gives the storage process an external execution layer with auditable outcomes.
Operational resilience
Retention tasks, node rotation and repeated pinning checks improve continuity over time. The system is designed to preserve access even when individual IPFS endpoints or providers change.