Anchored to Bitcoin & Polygon · Open verification spec

Sign once. Verify forever.

The first e-signature platform anchored to Bitcoin AND Polygon — two independent public networks. Open verification spec. Open-source CLI. Tamper-proof for decades.

By clicking Start for free, you agree to our Terms & Conditions and Privacy Policy.

Free plan available · No credit card required

Integrates with 24+ tools you already use

Zapier
Zapier
Slack
Slack
Google Drive
Google Drive
Salesforce
HubSpot
Stripe
QuickBooks
QuickBooks
Microsoft 365
Pipedrive
PayPal
Dropbox
Dropbox
Notion
Notion
Teams
Teams
Zoho
Square
Greenhouse
Make
Box
BambooHR
Xero
Xero
Monday
Monday
Zendesk
Zendesk
Google Workspace
Google Workspace
OneDrive
OneDrive
Zapier
Zapier
Slack
Slack
Google Drive
Google Drive
Salesforce
HubSpot
Stripe
QuickBooks
QuickBooks
Microsoft 365
Pipedrive
PayPal
Dropbox
Dropbox
Notion
Notion
Teams
Teams
Zoho
Square
Greenhouse
Make
Box
BambooHR
Xero
Xero
Monday
Monday
Zendesk
Zendesk
Google Workspace
Google Workspace
OneDrive
OneDrive

Trusted by teams in high-compliance industries

Legal FirmsReal EstateFinancial ServicesHealthcareGovernment

How it works

Six steps to legally binding, multi-anchor-verified signatures.

Zdottedline 6-step e-signature workflow: upload document, AES-256 encryption and secure cloud storage, invite signers, document signing with identity verification, dual-anchor audit trail on Bitcoin (OpenTimestamps) and Polygon, and completed legally binding document under ESIGN Act and eIDAS compliance
1

Upload Your Document

Drag and drop any PDF, DOCX, or image. Our AI auto-detects signature zones and form fields.

2

Encrypt & Store

AES-256 encryption at rest, TLS 1.2+ in transit. Stored in AWS S3 with server-side encryption and key management.

3

Invite Signers

Add recipients by email. Set signing order, access codes, and 2FA requirements for each signer.

4

Sign with Verification

Signers authenticate and apply their signature. IP address, timestamp, and user agent captured for legal validity.

5

Multi-Anchor Audit Trail

Every action extends a SHA-256 hash chain. The Merkle root anchors to Bitcoin (via OpenTimestamps, every plan) and Polygon (Pro+) — two independent public networks, two independent proofs.

6

Legally Binding · Independently Verifiable

Completed documents are ESIGN, UETA, and eIDAS compliant. The verification spec is open. The CLI is open source. Anyone can confirm using only public Bitcoin and Polygon nodes.

Everything you need for secure document signing

Enterprise-grade features designed for teams that handle sensitive documents.

GDPR Compliant
HIPAA Ready
AES-256 Encryption
AWS Infrastructure
eIDAS AES
ESIGN Act
SHA-256 Hash Chain
Bitcoin Anchored
Polygon Anchored
Open Verification Spec
GDPR Compliant
HIPAA Ready
AES-256 Encryption
AWS Infrastructure
eIDAS AES
ESIGN Act
SHA-256 Hash Chain
Bitcoin Anchored
Polygon Anchored
Open Verification Spec

Immutable Hash Chain

Every action from upload to final signature creates a SHA-256 hash chain. Tampering with any step invalidates the entire record.

AI-Powered Field Detection

Upload a PDF and our AI identifies signature zones, date fields, and form areas automatically. Set up signing in seconds, not minutes.

Open-Source Verification

Anyone can verify a signed document against public Bitcoin and Polygon data — using our open-source CLI (npm install -g @zdottedline/verify). No account needed. Verification runs directly against public networks.

Legally Binding Signatures

Compliant with ESIGN Act and UETA. eIDAS Advanced Electronic Signature support. Every signature captures IP, timestamp, and user agent for legal validity.

Multi-Party Signing

Sequential or parallel signing workflows. Set the order, add access codes, require 2FA. Handle complex signing ceremonies with ease.

Complete Audit Trail

Every view, click, and signature is logged with immutable timestamps. 7-year retention meets eIDAS Advanced Electronic Signature requirements.

Encrypted Cloud Storage

Documents encrypted at rest with AES-256. Access only through time-limited signed URLs. Your files never leave your control.

Document Templates

Create reusable templates with pre-placed fields. Send contracts, NDAs, and agreements in seconds with consistent formatting.

Real-Time Status Updates

Know the instant a document is viewed, signed, or declined. Live WebSocket updates keep your team in the loop.

The shift

Incumbent e-signature

Trust, conditional.

Your proof is a PDF certificate generated by their backend and vouched for by their logs. If their logs are wrong, or gone, or subpoenaed, your proof is whatever they say it is.

Audit trail hosted on vendor infrastructure
Verification requires vendor to still exist
Certificate is a rendered PDF, not a proof
Your documents sit in their S3 bucket

zdottedline

Proof, unconditional.

Every envelope extends a SHA-256 hash chain. The Merkle root anchors to Bitcoin (via OpenTimestamps) and Polygon — two independent public networks. Decades from now, anyone with the signed PDF and the .ots proof can hash, walk, and confirm authenticity against public Bitcoin and Polygon nodes — with or without us.

Audit trail reproducible from public Bitcoin + Polygon data
Works even if zdottedline ceases to exist
Open verification spec at github.com/zdottedline/zdl-verify
Zero-knowledge option: we never see content

Verify

Don't take our word. Take the chain's.

Every signed document carries two independent proofs (Bitcoin .ots file + Polygon tx hash). Run our open-source CLI — npm i -g @zdottedline/verify — and it walks the hash chain locally, reads the Polygon anchor from any public RPC, and confirms the OpenTimestamps proof against any public Bitcoin node. No account. No login. No zdottedline required.

Open spec · MIT-licensed CLI · github.com/zdottedline/zdl-verify

zdl-verify · github.com/zdottedline/zdl-verify
$ zdl verify efca4f81-1ac4-4b40-a595-0dc51d0752c0
→ fetching verify json + .ots proof…
hash_chain PASS · 6 events linked correctly
polygon PASS · block 54,221,098 · root matches
bitcoin PASS · block 850,123 · via OpenTimestamps
→ verified against public networks · ZDottedLine not in the loop
◆ VERIFIED. Independent of ZDottedLine. Independent of any single chain.

Sign something that lasts.

Start with three free signed documents per month. Bitcoin-anchored on every plan. Send the verification link to anyone who needs to check — or hand them the open-source CLI.