Blockchain Verification

How Verification Works

Vilulia anchors finalized settlements, arbitration awards, completion certificates, and final executed documents to the Polygon blockchain. The process creates a tamper-evident record: a cryptographic hash of the document is computed and written to the blockchain, proving that the document existed in its exact form at a specific point in time. Blockchain verification is available on Professional (10 anchors per month) and Enterprise (100 per month) plans. Starter does not include it, and overage beyond the monthly allowance is billed as a metered add-on.

What you'll learn

How Vilulia computes and stores a document's hash
What the Polygon blockchain provides in this context
Where the transaction hash is stored
What verification proves and what it does not prove

Step 1: Hashing the document

When a record is anchored, Vilulia computes a SHA-256 hash of its content. For files this is the file bytes; for settlements and awards it is the record data. SHA-256 is a one-way cryptographic function: the same document always produces the same hash, and any change — even a single character — produces a completely different hash. The hash acts as a unique fingerprint of the document at the moment of anchoring.

Step 2: Writing to the blockchain

The hash is submitted as a transaction to the Polygon blockchain. Polygon is a proof-of-stake blockchain network that provides fast, low-cost transaction confirmation. Once the transaction is confirmed, it becomes part of the permanent, immutable blockchain record — it cannot be altered or deleted.

Step 3: Storing the transaction hash

Vilulia stores the blockchain transaction hash (tx_hash) against the case record in the platform. This is the reference used to verify the document. Anyone can look up the transaction on the blockchain, and Vilulia provides a public verification page (no account required) to confirm that the document's SHA-256 fingerprint matches what was recorded at the time of signing.

What verification proves

Blockchain verification proves that a specific document existed in its exact form at the time the transaction was confirmed on the blockchain. It does not authenticate the identities of the parties who signed the document — that is the role of the DocuSign e-signature process. Together, DocuSign e-signature and blockchain verification provide both identity verification and tamper-evidence.

Can't find what you're looking for? Contact Support