Guided Demo
Walk through the full VFD + Ocean lifecycle: upload sensor data, build a deterministic dataset, publish to Ocean Protocol, verify integrity, extract contracted subsets, replicate, and observe metrics.
Waiting to start...
Data Manager
Drag & drop a CSV or JSON file here
or click to select
Objects in Store 0
| Key | Object ID | Size |
|---|
What this proves
Each object is content-addressed via SHA-256 of its canonical binary representation. The object ID is deterministic: identical data always produces the same ID, regardless of insertion order, timestamps, or environment. This is the foundation of VFD's integrity guarantees.
Dataset Builder
What this proves
The DatasetID is a SHA-256 hash of the dataset's Merkle root, name, version, namespace, and all object IDs. It is deterministic and tamper-evident: changing any single byte in any object changes the ID.
Ocean Publisher
What this proves
Publishing creates an on-chain NFT record linking the DID to the dataset descriptor. The transaction hash is immutable proof that the dataset existed at a specific point in time.
Verify & Proof
What this proves
Verification re-computes every hash from raw data and compares against the published descriptor. If any object was modified, the Merkle tree will produce a different root, and verification will fail. The Truth Hash from ARIA provides an independent cross-check.
Contract & Derive
What this proves
Contraction extracts a minimal provable subset from the full dataset. The contracted bundle includes Merkle proofs that each selected object was indeed part of the original dataset, without revealing any other objects. This enables selective data sharing with full integrity.
Replication
Store A (Source)
0
objects
Store B (Replica)
0
objects
What this proves
Replication uses a hash-chained append-only log (RLOG). Each entry's hash includes the previous entry's hash, creating a tamper-evident chain. If any entry is modified or reordered, the chain verification fails.
Storage Explorer
Live view into the actual VFD MemoryVfdStore. Every number here comes directly from the store internals — nothing is simulated.
Namespaces
| Namespace | Keys | Bytes | Browse |
|---|
Object Browser — ocean-demo 0
| Key | Object ID | Bytes | Lane | Epoch | Inspect |
|---|
Object Detail
Integrity Check
Observability
Step Timings
Bundle Sizes
Replication Log
Similarity Scores
What this proves
All operations are deterministic — identical inputs produce identical outputs and identical timings (within measurement noise). The charts visualize the operational characteristics of each step.