How to download the signed copy and its certificate

The four files you can download

File	Where to click	What it holds	Who can download it
Signed copy (the title, then -signed.pdf)	View the signed copy, then Download signed copy	The whole agreement: the signed pages, with every entry, a "Signed with Attest" stamp on each signature and a seal line at the foot of every page, a certificate of completion, the audit trail up to completion and a "Verify it yourself, without us" page, with the full evidence, the original document and a standalone verifier attached inside	The parties
Signed pages only (-signed-pages.pdf)	Signed pages only, in the same window	Just the document's own pages, with their stamps and the evidence attachments, for a filing that must keep the page count. It is anchored too	The parties
Certificate of completion PDF (attest-certificate-, then the agreement ID)	Download certificate (PDF), on the certificate page	The certificate of completion: the title, the completion time (UTC), the number of parties, the verification code, the fingerprints of the document and the signed state, the Horizen anchor transaction, and each signer's name and signing time, with no document, entries or audit trail; the evidence and the verifier are attached	Anyone who can view the certificate
Signature evidence (attest-signatures-, then the agreement ID, .json)	Download the evidence (JSON), on the certificate page	Each signer's signed statement, passkey public key and WebAuthn signature data, for anyone who wants to re-check the signatures with their own tools	Anyone who can view the certificate

The parties are the sender and each signer. Attest stores the signed copy only encrypted with the document's key, so on Attest only they can open it. The copy you download is the decrypted file: an ordinary PDF that anyone you give it to can open, so keep and share it as you would the contract itself.

Download the signed copy, step by step

The video above shows these steps on the real app.

1. Sign in at attest.datahubz.com, open Documents in the menu (it reads Agreements on accounts that use every Attest tool) and choose the Completed tab.
2. On the document, click View the signed copy. Your passkey unlocks your key, and the document is decrypted in your browser. If Attest asks for your recovery phrase instead, type it and click Decrypt.
3. Read the header of the window. "Signed copy · every party signed, sealed and anchored" means this is the final sealed copy. "anchoring now (preliminary copy)" means the blockchain anchor isn't written yet: close the window and open it again a little later. When the sender is on the Free plan, the anchor is written within about 10 minutes; on the Signing plan or Pro, the moment the document is complete.
4. Click Download signed copy. The file is named after the document's title, for example services-agreement-northwind-and-acme-signed.pdf. A copy downloaded before the anchor is written ends in -preliminary, so keep the sealed one.
5. If you need only the document's own pages, for example for a filing that must keep the original page count, click Signed pages only (Pages only on a narrow screen). It appears once the copy is sealed.

Signed without an account? Your signing link shows View and download the signed copy for 30 days after the document is completed. After that, go to attest.datahubz.com/signin, click Email me a sign-in link with the address the document was sent to, and follow the steps above.

One sealed copy, checked every time it opens

Each agreement has one sealed copy. The first party's browser to open the document after it is complete and anchored makes it, and Attest stores it, encrypted, for everyone, so every party downloads exactly the same file. Its pages are anchored on Horizen, a public blockchain, from the sender's wallet.

Every time you open it, your browser decrypts it, checks it against its recorded fingerprint and re-makes its pages from what was signed. A copy whose pages differ is refused, so what you download is exactly what every party signed.

What's inside the signed copy

• The signed pages, with every signer's entries where they were placed, a "Signed with Attest" stamp around each signature (initials get a smaller "Attest" stamp) and a seal line at the foot of every page with the verification code and the link to verify it.
• A certificate of completion, with the title, the completion time, the number of parties, the verification code, the document and signed-state fingerprints, the anchor transaction and each signer's signature with their name and signing time.
• The audit trail up to completion, each step in order, with times in UTC.
• A "Verify it yourself, without us" page, the last page, which explains how to check every step without Attest.
• Three attached files: attest-evidence.json (the full evidence), original-document.pdf (the document exactly as signed) and attest-verifier.html (the standalone verifier). A PDF reader with an attachments panel, such as Adobe Acrobat Reader, lists them; the verifier is also published at attest.datahubz.com/attest-verifier.html.

Download the certificate, step by step

1. On the completed document, click Certificate. Or open the email Attest sent every party when the document was completed (the subject starts with "Completed:") and click View verification certificate.
2. Watch the certificate check itself. As it loads, your browser re-checks each signer's passkey signature, recomputes the signed state and reads the anchor from Horizen, then shows "Signed and sealed".
3. Click Download certificate (PDF), below the Fingerprints section. Your browser opens the PDF; save it from there.
4. To keep the raw signature evidence too, click Download the evidence (JSON) under Passkey signatures.

A public certificate can be opened, and its PDF and evidence downloaded, by anyone with its link, the verification code or the document's fingerprint. It shows signers by name, and their email addresses only to the parties. If the sender made the certificate private, only the parties can open it: the sender, and each signer through their link or signed in. Anyone else is told the agreement exists and is private.

Which file to keep, and which to share

You want to	Use
Keep the agreement with your records	The signed copy
File it where the page count must match the original	Signed pages only
Show an auditor who signed and when, without the terms	The certificate PDF, or the certificate's link
Let a technical reviewer re-check every passkey signature	The signature evidence (JSON)
Prove you signed, and the date it was completed, without the title or the terms	A zero-knowledge proof: see how to share proof that you signed

The two PDFs each check themselves. Drop either one on the verifier attached inside it, and it re-makes its pages from what was signed and anchored and compares them with the file byte for byte. How to verify a signed document, step by step shows what each check means.

Why keep your own copy

Once downloaded, the signed copy depends on neither your Attest account nor Attest. The verifier attached inside it runs in any browser and reads only a public blockchain node. A real agreement signed on attest.datahubz.com was verified this way with Attest blocked, in the film "We blocked Attest. The agreement still verified." on the signing page.

Keeping a copy can matter legally, too. In the United States, the ESIGN Act says that where a law requires a contract to be in writing, an electronic record of it may be denied legal effect if it isn't in a form "capable of being retained and accurately reproduced for later reference" by everyone entitled to keep it (15 U.S.C. 7001(e)). Where a law requires a contract or other record of a transaction in interstate or foreign commerce to be retained, keeping an electronic record that accurately reflects it, and that stays accessible to everyone entitled to it for the required period in a form that can be accurately reproduced, meets the requirement (15 U.S.C. 7001(d)(1)). This is general information, not legal advice.