Why Twala Anchors Documents on a Public Blockchain, Not a Private One

For an enterprise, the point of anchoring documents on a blockchain is proof that doesn’t depend on the vendor. That only works on a public chain, which is why HashOrigin™ anchors on Polygon. Here is the reasoning, what goes on the chain, and what an auditor should ask.

Say “blockchain” in a procurement meeting and three worries come up: cost, cryptocurrency, and data exposure. Twala’s use of it is narrower than any of them. Every document Twala seals gets a fingerprint, and those fingerprints are anchored on a public blockchain so the proof outlives anyone’s database, including Twala’s.

What the anchor is for

A signed PDF on Twala already carries proof inside the file: the Twala Platform Seal, a digital signature with a trusted timestamp. Change a byte and the seal breaks. So why add anything outside the file?

Because every proof inside a system rests on trusting whoever runs it. A seal is only as trusted as the certificate behind it. A record in a database that says “this document existed in this form on this date” is only as good as the people who can edit the database. For a contract that might be disputed in ten years, or a notarized deed a registry will rely on, an enterprise wants one more witness: one nobody controls, not even the vendor.

Why a private chain doesn’t solve it

A private or permissioned blockchain, run by a vendor or a small consortium, looks like the safe enterprise choice. For document proof, it brings back the problem it was meant to solve. Its operators decide who writes to it and can, together, rewrite it. If they shut it down, the record goes with it. And an outside auditor has to be given access to read it at all. In practice, it is a database with extra steps.

A public blockchain works the other way. It is maintained by many independent parties, anyone can read it with public tools, and once a transaction has been buried under later blocks, rewriting it is impractical. That is the property an enterprise needs from an anchor: a record that stays put and that any third party can check without asking permission.

What goes on the chain, and what doesn’t

Nothing about the documents themselves. When a document is completed on Twala, the sealed file’s SHA-256 hash is recorded. Every 15 minutes, up to 256 of those hashes are combined into a Merkle tree, and only its root, a single fingerprint of fingerprints, is written to Twala’s contract on Polygon, in its own transaction. If an anchoring job fails, it is retried automatically.

That design matters for privacy law as much as for security. No names, contents, or personal data are written on-chain, so a public, permanent ledger never holds anything the Data Privacy Act protects. A fingerprint can’t be turned back into the document it came from. Files stay in your Twala workspace, under your organization’s access controls.

What your team doesn’t have to do

Nobody in your organization handles a wallet, a token, or a transaction fee. Twala writes the roots to its own contract, and batching keeps one transaction covering up to 256 documents. To your users, anchoring is invisible: they sign, the document is sealed, and the proof is there when someone needs it.

Proof that outlives the vendor

This is where the public chain earns its place in an enterprise’s records policy. Anyone holding a Twala document can check it on Twala’s verify page, which shows the document’s fingerprint, the Merkle root, and the Polygon block where it was anchored, then returns Document verified or Document tampered.

The same check also works without Twala. With the document’s anchor proof, the short trail of values that links its fingerprint to the root, anyone can recompute the root with their own tools and compare it with what is recorded on Polygon. Anchor proofs, details of the contracts Twala anchors on, and a sample verifier are published at hashorigin.io. An auditor, a court, or a counterparty can confirm a document is unchanged without trusting Twala, and that stays true whatever happens to any single company.

Two details make that dependable. Twala’s anchoring contract has no upgrade mechanism, so the rules it uses to check a proof can’t be changed after the fact, by Twala or anyone else. And each document’s anchor proof can be downloaded as a small file, from the document’s record details or from the verify page under Verify independently. For an enterprise, that suggests a simple records rule: file the anchor proof next to the PDF, and the document can prove itself for as long as you keep both.

Questions for an auditor or a security review

What it doesn’t do

Blockchain anchoring doesn’t make a document legally valid. That comes from the law: the Electronic Commerce Act (R.A. 8792), the Rules on Electronic Evidence, and, for notarized documents, the Rules on Electronic Notarization. It doesn’t store your documents or stop anyone from copying a PDF. What it does is answer one question for good: is this exactly the file that was sealed, down to the last byte?

The step-by-step mechanics are in HashOrigin explained, and the full set of controls around it is on the security page and in the trust center.

Twala is a Supreme Court-accredited Electronic Notarization Facility (ENF). HashOrigin™ is a trademark of Ohelio Inc.