How vtimestamp Compares
An honest look at how vtimestamp stacks up against traditional methods and other blockchain platforms for document timestamping.
vs Traditional Methods
Timestamping has existed long before blockchain. Here's how vtimestamp compares to the methods people have used for decades.
| vtimestamp | Traditional Notary | Centralized Service | RFC 3161 TSA | Bitcoin (OpenTimestamps) | |
|---|---|---|---|---|---|
| Document privacy | Hash only, never uploaded | Document seen by notary | Document often uploaded | Hash only (sent to TSA) | Hash only (client-side) |
| Proof ownership | Your VerusID | Paper certificate | Service account | Signed time-stamp token file | A .ots file you keep |
| Verification | Anyone, anytime, free | Requires notary records | Requires service to exist | Requires TSA certificate chain | Anyone with the .ots file + a Bitcoin node |
| Metadata | Title, description, filename on-chain | Notary's records | Service database | None (hash + time only) | None (hash only) |
| Cost | Verus tx fees (~0.004–0.005 VRSC) | Notary fee ($5-50+) | Subscription / per-stamp fee | Free to per-stamp (commercial TSAs charge) | Free (aggregated via Merkle tree) |
| Identity | Self-sovereign VerusID | Government ID | Email / password | TSA-signed (no user identity) | None |
| Durability | Blockchain permanent | Paper degrades | Company may shut down | TSA cert expiration / TSA shutdown risk | Blockchain permanent; .ots file must be kept |
| Human readable | Yes (metadata + explorer) | Yes (paper document) | Depends on service | No (binary token) | No (hash and proof file) |
vs Other Blockchains
How does timestamping on Verus compare to doing it on other major chains?
| Verus (vtimestamp) | Ethereum | Solana | Cardano | Hedera (HCS) | Sui | |
|---|---|---|---|---|---|---|
| Mechanism | Native identity update (contentmultimap) | Smart contract or calldata | Memo Program or custom program | Native transaction metadata | HCS topic messages | Move objects (custom module) |
| Smart contract needed? | No | Yes | No (Memo Program) | No | No | Yes |
| Identity | VerusID (native, self-sovereign) | ENS (.eth) — separate system | SNS (.sol) — separate system | ADA Handle / Atala PRISM | DID via HCS | SuiNS (.sui) — separate system |
| Identity is native? | Yes — built into the protocol | No — ENS is a smart contract | No — SNS is a program | Partial — handles are native tokens | No — DID is an application layer | No — SuiNS is a Move module |
| Cost per timestamp | ~0.004–0.005 VRSC (stable) | 21,000-41,000 gas + variable gwei (volatile) | 0.000005 SOL | ~0.18 ADA | ~$0.0008 USD (fixed) | ~0.001-0.01 SUI |
| Cost predictability | Stable (fixed fee) | Volatile (gas market) | Stable (low base fee) | Stable (formula-based) | Fixed USD schedule | Stable (low fees) |
| Structured metadata | Yes — VDXF DataDescriptors with typed labels | No — you design your own contract storage | Limited — 566 bytes in memo | Yes — native JSON metadata | Yes — up to 1KB per message | Yes — Move struct fields |
| Data lives on | Your VerusID (you own it) | A smart contract (contract owner controls) | Transaction logs or program account | Transaction record | Mirror nodes (not consensus nodes) | Sui objects (can be owned/frozen) |
| Who owns the proof? | You — it's on your identity | Contract determines access | Your wallet signed it | Your wallet signed it | Topic creator controls submit access | Object owner |
| Verification | Anyone, any Verus node | Anyone, any Ethereum node | Anyone, any Solana node | Anyone, any Cardano node | Mirror nodes (not fully permissionless) | Anyone, any Sui node |
| Document privacy | Hash only — client-side, never leaves device | Depends on dApp — hash or full upload | Hash only | Hash only | Hash only — up to 1KB visible on mirror nodes | Hash only |
| Existing timestamping dApps | vtimestamp | OriginStamp, CryptoProof (timestamp.com), ScoreDetect | Research prototypes only | No dedicated service found | No verified service found | None found |
What Stands Out
Verus vs Ethereum
Ethereum requires deploying a smart contract to store timestamps, and ENS is a separate system you opt into. On Verus, identity and structured data storage are protocol-level features. You don't deploy anything — you update your identity. Ethereum's gas costs are also unpredictable, whereas Verus uses standard consistent transaction fees.
Verus vs Solana
Solana is extremely cheap and fast, but the Memo Program gives you 566 bytes of unstructured text. There's no native identity or structured metadata. You'd need to build a custom program for anything beyond a raw hash, and Solana's name service is a separate add-on. No production timestamping dApp exists on Solana.
Verus vs Cardano
This is the most interesting comparison. Cardano's native transaction metadata is genuinely good — structured JSON, no smart contract needed, cheap. The key difference: Cardano metadata lives on a transaction. Verus timestamps live on your identity. Your VerusID accumulates timestamps over time as part of your identity history — it's not just "a hash was in this transaction" but "this identity recorded this hash."
Verus vs Hedera
Hedera's HCS is purpose-built for this kind of thing and is very cheap. The tradeoff is decentralization: you can't run a consensus node (only governing council members can), and message data is stored on mirror nodes rather than consensus nodes. Verification depends on mirror node infrastructure being available. Verus is fully permissionless — anyone can run a node and verify directly.
Verus vs Bitcoin / OpenTimestamps
OpenTimestamps has been the standard for Bitcoin timestamping for nearly a decade. It's free — millions of timestamps aggregate into a single Bitcoin transaction via Merkle trees — and it runs on a clean, blockchain-agnostic open protocol. Its tradeoffs are scope: timestamps are hash-only with no identity or structured metadata, and each proof is a .ots file you have to keep alongside your document to verify. Verus trades free-per-timestamp for identity-attributed, structured, self-contained proofs that live on your VerusID — nothing extra to keep. OTS is excellent for "did this exist?" Verus is better for "who recorded this, with what context, and how can anyone find it again?"
The Identity Difference
The recurring theme across all comparisons: on other chains, identity is an add-on. On Verus, identity is the foundation.
Every other chain starts with addresses — long hex strings — and bolts on naming services as optional layers. Your timestamp is tied to a wallet address first, a human-readable name second (if at all).
On Verus, your timestamp is stored on your VerusID. The identity is the container. When someone verifies a timestamp, they look up alice@ — not 0x7a3b... with a reverse ENS lookup. The identity layer isn't cosmetic; it's structural. Your timestamps, your data — it all lives under one self-sovereign identity that you own and control.