Browser extension

The Fidemark extension scans every web page for attestation markers, looks them up via the public JSON API, and shows a small floating pill summarizing what’s verified. The popup also lets you attest the current page yourself with one click.

Status: not yet available. The extension will appear on the Chrome Web Store once it has been published and cleared the store’s review process. A Firefox build is on the roadmap.

What it detects

The content script scans the page at document_idle for any of:

Marker	Example
<meta name="fidemark-uid" content="0x...">	A page declaring its own attestation.
<fidemark-badge uid="0x...">	A rendered Fidemark badge.
[data-fidemark-uid="0x..."]	A generic data attribute.

For each unique UID, the extension’s background worker fetches https://verify.fidemark.dev/api/attestation/<uid> (cached 30 s per UID) and renders a floating pill bottom-right of the page summarizing the result:

• ✓ N verified: all attestations valid.
• N revoked, M valid: at least one revocation present.
• N unreachable: lookup error (offline, server down).

Click the toolbar action for the per-UID list with status pills and links to the full verify page.

”Attest current page”

The popup has a single button: Attest current page. It:

1. Reads document.body.innerText from the active tab via chrome.scripting.executeScript.
2. SHA-256 hashes the text in the browser using Web Crypto.
3. Opens the dashboard at https://verify.fidemark.dev/app?contentHash=0x…&source=<page-url>.

The dashboard reads the contentHash query parameter and prefills the attestation form in precomputed-hash mode: the textarea is replaced with a banner showing the hash and the source URL, the original page text stays on the originating page, and only the 32-byte digest goes on chain. The form keeps a Switch to manual entry escape hatch in case you would rather paste the text yourself.

You finish the attestation with your own wallet: the extension never holds keys.

Installing

Install from the Chrome Web Store.