Twala Sign

The problem

E-signature platforms are trusted third parties. Their audit logs are their own claims — dependent on their solvency, retention policy, and integrity. For contracts that matter (large transactions, cross-border deals, regulatory filings), that dependency is a single point of failure. If the platform goes down, gets acquired, changes retention policy, or has its own compliance failure, the audit trail you rely on can evaporate. Anchoring signature records on-chain solves the dependency by moving the integrity guarantee from the platform to the blockchain. But building that anchoring in a way that satisfies enterprise workflow requirements and holds up in court is nontrivial.

Key challenges

Blockchain-anchored e-signatures have to work as a normal e-signature product first and as a blockchain product second. Enterprises don't sign contracts on blockchains; they sign contracts through UIs that happen to anchor to blockchains in the background. The anchoring needs to be reliable, cost-manageable, and legally defensible without adding friction the user perceives.

What we built

AR Data delivered engineering on Twala Sign — blockchain-anchored e-signatures where the signature record hashes are committed on-chain. Signature integrity survives platform failure because the hash exists on a chain the platform doesn't control. The workflow feels like a normal e-signature product: draft, send, sign, complete. The anchoring happens in the background — signature record hashes get committed to the chain as part of the completion flow, with an on-chain reference stored alongside the signed document. Verification is available to anyone with the document and the on-chain anchor.

Our approach

1. 1

   Enterprise UX first, blockchain second

   Users don't want to think about blockchains; they want e-signatures that work. The UX matches DocuSign-family expectations; anchoring is transparent.

2. 2

   Hash-only on-chain anchoring

   Storing documents on-chain is impractical. Hash anchoring gives integrity guarantees without the cost and privacy issues of on-chain storage.

3. 3

   Multi-chain anchoring for redundancy

   Single-chain anchoring is a dependency. Multi-chain anchoring gives redundancy against any single chain's operational issues.

4. 4

   Verification available to any party with the document

   The verification tool doesn't require the platform to be around. Any holder of the document and the anchor can verify integrity, which is the whole point.

Key architectural decisions

Results

• Blockchain-anchored signatures with tamper-evident integrity
• Enterprise workflow integration matching DocuSign-family UX
• Multi-chain anchoring for redundancy
• Verification available to any party with the document
• Cost-manageable on-chain anchoring via hash-only storage
• Audit logs that survive platform failure

Impact

Twala Sign is a working demonstration that blockchain integration can meaningfully improve e-signatures without changing what users experience. The engineering pattern — hash-only anchoring, multi-chain redundancy, platform-independent verification — is the right shape for any product where blockchain integrity guarantees need to strengthen a Web2 workflow.

Tech stack