Verify an Object
Last updated
Last updated
The vBase Verify tool checks whether a file—or its content ID (SHA3 hash)—has previously been stamped on the blockchain using vBase. If a match is found, the app displays the full stamp details, including the timestamp, blockchain address, and other stamp details.
For a quick overview,
Visit
Select the file you want to verify
The app calculates the file’s content ID () in your browser
It queries the blockchain (currently ) for any stamp matching that content ID
If a match is found, full stamp details are displayed
When you verify a file:
The SHA3 hash (also called the content ID or digital fingerprint) is calculated locally in your browser
vBase uses this content ID to search for matching stamp transactions on the relevant blockchains (currently Polygon)
If a match is found, the app retrieves and displays the following on-chain stamp metadata:
📅 Timestamp
When the stamp was recorded on-chain
👤 Blockchain Address
The blockchain address associated with the vBase account that created the stamp
🧩 Content ID
A hash (unique fingerprint) of the file
🗂️ Collection ID
A hash of the name of the collection to which the file belongs (if applicable)
🔗 Transaction Hash
Blockchain transaction ID for the stamp
💡 This information is pulled directly from the blockchain and is independently verifiable.
In some cases, off-chain metadata from the vBase database (e.g., Username, Collection Name, Identity Verification Status) may also be shown if available.
User Notes
Your file’s hash is always calculated locally in your browser
The file itself is never uploaded or seen by vBase during verification
All stamps are currently recorded on the Polygon blockchain and are independently verifiable
Even a 1-character or 1-byte change to a file will produce a completely different content ID.
This means:
The file must match exactly—bit-for-bit—with the originally stamped version
If you've re-saved, edited, or reformatted the file in any way, the hash will not match
Yes! If you already know your file’s SHA3 hash, you can paste it into the "Verify by Content ID" field:
Click "Verify by Hash"
Paste the SHA3 hash (hex format, e.g., 0xabc123...)
The app will search for a match and display any corresponding stamp
If the file was originally stamped as part of a Collection, the Verify app will:
Display the Collection ID associated with the file
Show the Collection Name, if available
📌 This is especially useful when verifying which files belong to specific projects, datasets, or deliverables.
Yes. If a user stamps the same file twice or two users stamp an identical file, it will produce the same content ID. The blockchain will show multiple transactions for that content ID, each with its own timestamp and blockchain address. For real-world data with any reasonable amount of entropy, this is extremely unlikely.
Yes, see the Python SDK samples for verifying via the API.
Stamp records on the blockchain are permanent. If the original copy of the file is lost, then the associated Stamp will not be verifiable, however it will still be visible on-chain.
SHA3 Hash
A unique fingerprint for a file
Content ID
A vBase-specific name for an object's fingerprint
On-chain Data
Info permanently stored on the blockchain
Off-chain Data
Extra metadata, not on the blockchain
Advanced users can query stamps directly via tools like , , or publicly available Polygon nodes
You can calculate the SHA3 hash locally using tools like sha3sum, openssl, or browser-based hash calculators to compare with the content ID. A few public calculators are available and .
Go to
📖
🧩
