Hardware E-Seal. Non-repudiable, jurisdiction-portable.

Where Legal & Digital Notary breaks today

Signature repudiation in litigation

Defendants increasingly claim 'I never signed that' or 'my account was compromised' — and conventional e-signatures lack the cryptographic non-repudiation to defeat the claim.

80% — of B2B contracts now electronic · ESIGN Act surveys

Timestamp manipulation

The party controlling the e-signature platform also controls the timestamp; counter-parties have no independent verification.

eIDAS QES — requires a Qualified Trust Service Provider for timestamps

Document tampering post-signature

PDF signature wrappers can be stripped or altered; downstream parties may receive a tampered version with no detection.

ESIGN Act §7001 — requires signature integrity over the entire record

Three patents, deployed against this industry's threat model

Each of Axowl's three filed patents maps to a specific structural failure mode in Legal & Digital Notary. Together they form a single, end-to-end defense.

Hierarchical Distributed Trust Fabric — E-Seal device (L1) · Notary server (L2) · Jurisdictional registry (L3)

The signing party's hardware E-Seal carries a PUF identity (L1). A notary or in-house signing server acts as L2. The jurisdictional registry (or the EU Trusted List for QES) forms L3. The E-Seal must be physically present — credentials alone never suffice.

Transition-Sealed Integrity System — Every counter-signature, every amendment, sealed

Each signature, counter-signature, and amendment is appended to the contract's hash chain. Tampered documents are detectable on opening; the legal record consists of the document plus the chain, not the document alone.

Pre-grant LLM Conflict Verification — Conflict-of-interest patterns refused at grant

A grant such as "counsel + sign for opposing party" or "notary + same-firm party" is detected as a structural conflict and refused. Bar-rule violations are caught before they happen, protecting the firm and the client.

Deployment that fits the threat model

Legal deployments require the Defense tier — hardware E-Seal token, TPM-anchored signing workstation, and the IRON sealed chain. Cross-border deployments to EU jurisdictions integrate with eIDAS Qualified Trust Service Providers.

Recommended tier: T2 · Defense

Deployment path: AWS Nitro Enclave · Hardware E-Seal token · QTSP federation

Operational detail: Day-1 deployment on AWS Nitro Enclaves. Hardware E-Seal tokens (YubiKey-class, custom-branded for major firms) ship to signing parties. EU QES alignment via federation with EU Trusted List QTSPs.

Three concrete deployments

M&A document execution

Multi-party closings — buyer, seller, lenders, escrow agent — co-sign with their respective E-Seals. The complete closing binder carries a single sealed chain spanning all signatures.

Real estate closings

Title transfer, mortgage execution, and escrow release are sealed in chain. Title companies can verify the entire transaction history without re-parsing PDFs.

Board resolutions & corporate governance

Board votes are sealed by each director's E-Seal. The resulting resolution survives any later dispute about who voted, when, and from where.

Versus what's deployed today

Today — Cloud e-signature platform

Platform controls keys, timestamps, and audit log. The same vendor that hosts the contract attests to its authenticity; counter-parties must trust the vendor.

With DPSM — Axowl DPSM

Hardware E-Seal must be physically present at signing. Counter-parties verify against an independent L3 registry. Vendor compromise cannot forge a signature.

Standards & regulatory frameworks aligned

• eIDAS Article 26 (QES)
• ESIGN Act §7001
• UETA §7
• ETSI EN 319 401
• ETSI EN 319 411 (QTSP)
• 21 CFR Part 11 (life-sciences contracts)