All guides / Proof and permanence
Certificates, Verified and Archive
What the Certificate page, Version History, the Verified and Archive lists and the PDF certificate show, and how to read them.
Every sealed article has a public Certificate page. Two lists in Explore, Verified and Archive, gather sealed articles. The author can also download a PDF of the certificate. A seal does not prove who wrote the text or that it is original.
The Certificate page#
Anyone can open it, signed in or not. Press the gold View Certificate label on a sealed article, Certificate in the Verified list, or Sealed next to an article in Studio.
From top to bottom:
- The heading. This Article is Verified or Verification in Progress. What a seal proves says what it means.
- Title, author and the Sealed on date, with the buttons Return to Article, Share Certificate and Issue Certificate.
- What This Means. Three rows. Signed Text is green when today's text gives the fingerprint the article has on record now. When the author edits a sealed article, that record is renewed, so this row stays green. Signature says that the author's wallet signed, and when. After an edit it turns off and the heading reads Verification in Progress. Permanent Record appears when there is a record on the blockchain. Version History shows what was sealed.
- Technical Details, collapsed and marked "For advanced users". It holds the Digital Fingerprint (Content Hash (SHA-256), with a copy button), the Author Signature, the Arweave Transaction ID (a button opens the copy) and the Blockchain Record. The record shows a Verified badge once Scryve has confirmed the CKB seal, the transaction ID, and Verify, which opens the CKB explorer (a public website that lists every CKB transaction).
- Independent Verification, collapsed, shown only when the article has a CKB transaction. Scryve's server fetches the seal from the chain, and your browser recalculates the fingerprint from the article text. The boxes Hashes Match and On-chain hash matches stored hash turn green when the fingerprints agree. For a subscriber-only article, a reader who cannot read it gets no text, so the panel cannot recalculate the fingerprint for them. It says "This article is paid, so its text goes only to readers who have it." The panel gets its data from Scryve. To look at the chain directly, press View on Explorer or Verify. The Manual Verification Guide in the panel says to look in the output data. For current seals, look in the extra witness instead (see below).
- View Article and Copy Certificate URL at the bottom.
In the transaction, the fingerprint is in an extra witness (a part of a transaction that can carry data). The witness is hex. It starts with 0x5343525956454851, which is the letters SCRYVEHQ, and Raw Hex Data in Independent Verification shows it. The fingerprint is not in the output data.
If nobody has started a seal on the article, you see Certificate Not Found ("This article does not have a seal yet.") and a Back button. The same screen shows if the page could not load. If an author started a seal and did not finish it, the page opens with Verification in Progress and Signature is off.
Version History#
At the bottom of a sealed article, any reader who can read the article can open Version History. Each version shows its number, a date, View and two small icons: one for the Arweave copy and one for the CKB transaction in the explorer. View opens the full text of that version. In that window, Compare with current shows removed words in red and added words in green. The comparison leaves out formatting and images.
After an author edits a sealed article, a row marked Pending Seal or Awaiting seal stands for the edited text that is not sealed yet.
The Verified list#
In Explore, open the tab Verified. Each row is one sealed version of an article, so an article sealed twice can appear twice. A row shows the title, the author's address in short form, the date, the badge On-Chain, the buttons Certificate, CKB TX and Arweave, and the full Content Hash. The list holds the 50 newest seals, shown 10 per page with Previous and Next. A count line reads "N verified article(s)" and counts all seals.
A row is listed only while its article is published. If an article is unpublished or deleted, its row goes. The CKB transaction stays.
To check a row yourself, open its CKB TX link and compare the fingerprint in the transaction with the Content Hash on the row. Certificate opens the article's current certificate, which matches the row only if the article has not been edited since.
The Archive list#
In Explore, open the tab Archive. Signed-in users also see an Archive link in the footer. Type an address, or part of one, in Search by wallet address... and press Search or Enter. The list then shows only authors whose address contains what you typed. The list shows 20 articles per page.
The Archive lists published articles that have a copy on Arweave. A row shows the title, the author, the time since signing, a short fingerprint and the buttons Permanent Copy and CKB. The badge Modified means the article was edited after it was sealed. The badge Sealed is on every row. The line "N article(s) sealed" above the list counts the rows. Both only mean that the article has a copy on Arweave. The green check Verified on-chain means the CKB seal was confirmed.
If the list does not load, you see "Failed to load archive. Please try again later."
The PDF certificate#
On the Certificate page, Issue Certificate downloads a one-page PDF titled "Seal Certificate". It shows the title, the author, the fingerprint, the transaction hash, the Arweave ID and the web address of the certificate. A message says "Certificate Downloaded".
- Only the author, signed in, sees Issue Certificate. It downloads the PDF with an active subscription (Reader or Pro) or a founder or associate status. Without one, the button looks faded and opens the Subscriptions page, and an info icon beside it shows "Subscribe to download and export your certificate". See Subscriptions.
- The PDF is not signed. It repeats what the Certificate page shows. To check a seal, use the Certificate page and the transaction.
- If it fails, you see "Failed to generate certificate. Please try again."
Checked: 2026-11-16