Live operations.
Verifiable identity.
Auditable history.
ObjectID connects industrial telemetry to a persistent on-chain identity without forcing operational data onto a public ledger. Each Twin can combine realtime MQTT data, role-based control, signed commands and independently verifiable lifecycle evidence.
A Digital Twin should prove more than what an asset is doing.
One identity across the lifecycle
The OIDTwin object and its IOTA identity remain the stable subject for metadata, states, evidence, datasets and future integrations.
Roles enforced on-chain
Owner, creator and steward relationships are not dashboard labels. Mutations are signed and checked again by the ObjectID Move contracts.
Operational data stays useful
Telemetry, models and large payloads remain in MQTT, S3-compatible or private customer infrastructure; hashes and provenance provide verifiable evidence.
Public verification and private operations remain independent.
The stack is split into replaceable layers. A public QR link can always resolve the Twin identity and public evidence; realtime data appears only when the Webview backend can securely reach the configured Integration Server.
Public path
Canonical URLs and QR codes expose public metadata and on-chain evidence without revealing private integration credentials, device passwords or private locations.
Authenticated path
A DID proves control through a one-time signed challenge. The same Twin URL upgrades to the authorized workspace, realtime source and permitted controls.
From discovery to safe operational control.
Map, QR and canonical links
Discover public Twins geographically, open a stable Twin URL and pin Twins you need to follow even when you do not own them.
Live MQTT observations
Versioned JSON payloads carry timestamps, sequence numbers, operating state and measurements with explicit engineering units.
Revisioned evidence
Lifecycle events, state changes, dataset references and transaction evidence form a continuity-checked, auditable history.
Controlled intent, not remote E-stop
Catalogued commands are signed locally, policy-checked, persisted before MQTT dispatch and correlated with acknowledgement and result messages.
Explainable technical checks
Profiles, evidence hashes and maturity indicators produce reproducible assessments while clearly separating alignment from formal certification.
Owner-aware data lifecycle
Managed storage is pruned after five days by default. Owner-specific retention policies are ready to map to future service-level agreements.
Keys, data and authority are protected at the layer that owns them.
Seeds never become server credentials
DID challenges and IOTA transactions are signed in the browser. Recovery material is protected with PBKDF2-SHA-256 and AES-256-GCM.
Integration secrets stay behind the BFF
API tokens, device passwords and private coordinates are AES-256-GCM encrypted at rest per DID and are never returned to the browser.
Authenticated and constrained ingestion
Production MQTT uses TLS, broker authentication, explicit topic-to-Twin mappings, bounded retry and circuit-breaker behaviour. Unknown topics are ignored.
Every mutation is independently enforced
The authenticated signer must own the relevant capability, while the Move contract enforces authority again at the on-chain boundary.
Traceable implementation against Digital Twin standards.
ObjectID maintains versioned profiles, evidence and conformance tests that map implemented capabilities to the relevant reference models.
ISO/IEC Digital Twin series
- ISO/IEC 30173 — concepts and terminology
- ISO/IEC 30181 — Digital Twin identifier model
- ISO/IEC 30186 — maturity model and evidence
- ISO/IEC 30188 — general reference architecture
ISO 23247 manufacturing series
- Parts 1–2 — principles and reference architecture
- Part 3 — digital representation and profiles
- Part 4 — MQTT/REST information exchange
- Parts 5–6 — Digital Thread and composition
Use familiar protocols without coupling device firmware to blockchain logic.
Publishes a versioned JSON observation with asset ID, sequence and timestamp.
→
Authenticates the client and routes only authorized topics.
→
Validates schema, maps the Twin and exposes the realtime API.
→
Stores payload bytes and anchors URI, SHA-256, lifecycle and provenance.
→
Combines public trust evidence with authorized live operations.
Public and independently readable
- Twin identity and public metadata
- Public location, when explicitly published
- Lifecycle and Digital Thread evidence
- Hashes, roles and chain state
Private and deployment-controlled
- Integration API credentials
- Device decryption password
- Private Twin location
- Realtime telemetry and customer storage
Explore a working Twin or deploy the open Integration Server.
The public demo shows the full Webview experience. The Integration Server repository includes MQTT mappings, realtime APIs, S3-compatible storage, retention and signed command support.