Open protocol · verifiable forever

Sign documents that anyone can verify. Forever.

Cryptographic proof you signed a specific document at a specific time — self-contained, independent of any platform, anchored on public chains.

Anchored onBitcoinPolygon
the proof is in the math.
The problem

You don't own your signature. They do.

Every time you sign with DocuSign, Adobe Sign, or HelloSign, you're trusting a company to keep your signature valid. If they shut down, raise prices, get breached, or lose your data, your proof disappears.

How it works

Three steps. Thirty seconds.

01

Sign

Open a document, tap Sign, confirm with Face ID or fingerprint. Done.

02

Share

Send a verification link or code to anyone who needs proof.

03

Verify

They open the link, see the . No account, no app — the math proves it.

The proof, not a promise

Everything a verifier needs, in one file.

A SignedBundle is a self-contained JSON file. It carries the document hash, the signer's key chain, a blockchain-anchored timestamp, and proof the signing key was valid. Anyone can verify it, forever.

SignedBundleValid
document_hash:sha256:e3b0c44298fc1c14…what was signed
signer:ed25519:7a3f…c91dwho signed it
timestamp:2025-06-01T14:32:00Zanchored on Bitcoin
subkey_cert:v2:ab12…ef56key was valid
What was signedWho signed itWhenKey was valid
Trust tiers

How sure can a verifier be?

Not all signatures carry the same weight. Mark lets you build trust progressively, each tier keeping the assurance below it.

Tier 1

Self-attested

Create an identity in two minutes. Cryptographic proof is strong, but identity is unverified. Good for everyday signing between known parties.

Tier 2

Endorsed

Get endorsed by a Tier 3 organization. An org vouches for the signer — verified through their process and signed with an org endorsement.

Tier 3

Notarized

Visit a notary who verifies your government ID. Equivalent to a notarized wet signature under US federal law.

Notary attestation is pending legal review of the attestation template.

Sovereignty

Two paths. One proof.

Identity

Published to Polygon via relay

On-chain

We relay the tx

Timestamp

Public calendars

Sharing

Verification code

SignedBundleValid
document_hash:sha256:e3b0c44298fc1c14…identical proof
signer:ed25519:7a3f…c91d
timestamp:2025-06-01T14:32:00Zanchored on Bitcoin
The case

Mark vs DocuSign.

MarkDocuSign
PriceFree tier, Pro $5/mo$15/mo
You own your signaturesSelf-contained proofPlatform owns verification
Survives vendor shutdownBlockchain-anchoredNo
Document uploaded to vendorOnly if you choose, for co-signYes, always
Independent verificationAnyone, anywhere, foreverNeed DocuSign
On-chain timestamp proofBitcoin + PolygonNo
Hardware key supportYubiKey 5C NFCNo
Open all the way down

Mark is one implementation, not the only one.

The Mark Signing Protocol (MSP) is published, versioned, and anyone can implement it. A SignedBundle is a JSON file. The verification algorithm is published. The proof chain resolves to public blockchains. If Mark the company disappeared tomorrow, every signature ever made would still verify.

{ "type": "SignedBundle", "version": "1.0", ... }
Read the spec
Legally binding

Valid where it counts.

Mark satisfies the US ESIGN Act and UETA (49 states + DC), the EU's eIDAS regulation (Advanced Electronic Signature), and equivalent laws in the UK, Australia, and Singapore. At Tier 3, a Mark signature is equivalent to a notarized wet signature under US federal law.

US ESIGNEU eIDAS (AES)UK / AU / SG

Exceptions: wills, codicils, testamentary trusts, and certain family-law documents are excluded in most jurisdictions.

Read the legal mapping

Your signature should be yours. Provable, permanent, and verifiable by anyone.

Verify a documentRead the docs