Chrome / Edge Extension

The TrustDID Chrome/Edge extension signs outgoing email in Gmail and verifies TrustDID signatures on any website. The toolbar shield turns green when a page's document authenticity is Verified, amber when something doesn't match, red when verification fails. The popup also shows the trusted-signer answer — Yes / No / Unknown — based on the trust registries your verifier is configured with (trustdid-setup --add-trusted-registry).

Before you start

The extension talks to the local TrustDID Service over https://localhost:8080. You need:

TrustDID installed — the signed installer on Windows, or the install script on Linux
An activated identity — paid tiers run trustdid-setup --managed YOUR_TOKEN YOUR_ID once (token + UUID from your enrolment email), which pulls the license from the API automatically; Free tier just runs trustdid-setup interactively
The TrustDID Service running (trustdid-service status reports running)

If any of those is missing, see Software Bundle on Windows or Software Bundle on Linux first.

Step 1: Accept the local certificate

Open https://localhost:8080/health and accept the self-signed certificate when the browser asks. Chrome and Edge will refuse to talk to the service otherwise. The certificate is generated on your machine and never leaves it.

Step 2: Load the extension

The extension ships unpacked during early access — there's no Web Store listing yet.

Extract TrustDID-Chrome-Edge-v1.4.3.zip to a permanent folder, for example C:\TrustDID\chrome-edge\ or ~/.trustdid/chrome-edge/. Don't move it later — Chrome remembers the path.
Open chrome://extensions/ (or edge://extensions/ for Edge).
Toggle Developer mode on (top-right corner).
Click Load unpacked and pick the folder you extracted.
The TrustDID shield icon appears in your toolbar. Pin it for easy access: click the puzzle-piece icon, then the pin next to TrustDID.

Step 3: Configure the extension

Right-click the TrustDID icon in the toolbar and choose Options. In most cases the defaults work — the extension auto-detects the local service. You may want to adjust:

API URL — defaults to https://localhost:8080. Change if you ran the service on a different port.
Auto-sign Gmail — on by default. Turn off if you'd rather click to sign.
Auto-verify — on by default. Turn off to verify only on demand.
Footer signature — appends a one-line "Verified by TrustDID" footer to signed messages. On by default.
Language — EN/FR. Defaults to your browser language.

Step 4: Try it

Verify: visit any website with a .well-known/did.json file (the TrustDID homepage works). The shield icon turns green and the badge shows the signature count for the page.

Sign Gmail: open Gmail in the same browser, click Compose, type a short message, and click Send. With auto-sign on, the message is signed in the background and a .vrfy sidecar attaches automatically. With auto-sign off, click the small TrustDID button in the Gmail toolbar before sending.

Troubleshooting

Shield icon stays grey. Service isn't reachable. Click the icon — the popup tells you exactly which endpoint failed. Most often: the service stopped, or you didn't accept the self-signed cert in this browser.

"Auto-sign skipped: identity not configured" in Gmail. The service is running but ~/.trustdid/config.json doesn't have a valid identity. Run trustdid status and follow what it prints.

Extension disappears after Chrome restart. You moved the unpacked folder. Re-load it from chrome://extensions/. Once the Web Store listing is live this won't happen — the store version is loaded from a stable location.

Edge: shield works in chrome:// pages but not on the actual web. Toggle Allow extensions from other stores in Edge settings. Microsoft's default policy blocks unpacked extensions from running on most domains.

Need help?

Open View → Developer → JavaScript Console in Chrome, reproduce the issue, and email support@trustdid.ca with the console output and your browser version.