Your browser asks the enclave for a signed fingerprint and verifies it.
It needs JavaScript. With it on, this page asks Maple's enclave at enclave.trymaple.ai for a fresh attestation document and verifies it. Without it, you can read the fingerprint Maple currently publishes in pcrProd.json on GitHub.
Not run yet
Step 1 of 4
Your browser makes a random number, and it must come back inside the signed document. That shows the answer is new, not replayed.
Your nonce
A one-time random value. Because the enclave had to include yours inside the signed document, an old document could not be replayed as a new answer.
Not run yet
Step 2 of 4
The document's certificate chain must end at Amazon's published Nitro root certificate. That shows Amazon's attestation infrastructure signed it, not someone else.
Root certificate SHA-256, matches Amazon's published value
Maple's enclave runs on AWS Nitro. Amazon's hypervisor writes the attestation document and Amazon's Nitro certificates sign it. You can compare this fingerprint on Amazon's page.
Not run yet
Step 3 of 4
The signature over the document must verify with the key in the last certificate of that chain. That shows nothing inside it was changed on the way.
Timestamp in the signed document
An ECDSA P-384 signature, verified with the leaf certificate's key, and each certificate's validity window against your device's clock. That is why a wrong clock fails this step.
Not run yet
Step 4 of 4
PCR0 is a hash of the software image inside the enclave. It must match an entry in Maple's signed history, the public record of every release Maple has approved.
PCR0, the enclave image fingerprint
Maple's signed history. Maple signs the fingerprint of every release it approves and publishes the list on GitHub. The check loads that list and verifies the signature on this fingerprint's entry in your browser. What does a match mean? That someone holding Maple's signing key approved this image. It does not by itself prove the image was built from the public source; rebuilding the image does that.
You still rely on the hardware behind each enclave, the published code and Maple's signing key.
Covers
Doesn't cover
Nothing to show yet. Document fields appear here only after a document passes verification.
Maple's signed history, pcrProdHistory.json. The check loads Maple's signed history from GitHub and verifies the matching entry's signature in your browser. A fingerprint already in the list built into this page skips that step. The Maple SDK (vendored at a pinned commit) does both, the way the Maple app does, and an entry counts only if its signature verifies in your browser against Maple's public key pinned in the SDK. The signed history keeps every release Maple has approved, so an enclave running an earlier approved release also passes. The list built into this page is the SDK's short list of recent releases; the current value is in pcrProd.json. Only PCR0 is compared.
ECDSA P-384 / SHA-384
Shown, not compared
Each run uses a new nonce. Verified in your browser with the same open-source functions the Maple app uses (@mapleai/sdk, vendored at a pinned commit). This request is separate from any chat session; the app runs the same check at the start of every session. The code is served by Maple from this page; if that matters for your work, use the desktop app or build Maple Proxy from source. Source, fingerprints and the Nix rebuild: services/opensecret on GitHub.
