The Usenami Signer signs your CEX/DEX orders inside an AWS Nitro Enclave — the venue API key never leaves attested code, and you don’t have to take our word for it. The PCR0 below is fetched live from the running enclave each time this page loads; it is never a pinned copy. Compare it against what your own tools report (below) and the on-chain registry — if they match, the code signing your orders is exactly the code we published.
The live attestation endpoint was not reachable from this server just now, so we’re deliberately not printing a PCR0 here — a stale value would be worse than none. The demo enclave rotates its measurement on every cutover, so the only trustworthy value is the live one. Fetch it yourself:
curl -s https://signer-demo.usenami.io:8443/attestation
Then confirm that PCR0 is active in the on-chain registry (below). If the endpoint stays unreachable, reach us at [email protected].
Every active PCR0 is registered in the UsenamiAttestationRegistry contract on Base, so the set of code measurements we’ve ever run is public and tamper-evident. Each cutover writes a new registerPCR0 entry — check the contract’s live event history rather than any one pinned transaction:
registerPCR0 history (most recent entry = current measurement): contract eventsisPCR0Active(<a PCR0>) answers whether that exact measurement is registered as active right now, and who owns it. Between rotations a box can be running a measurement the registry has already retired — so read the answer, don't assume it.When an AWS Nitro Enclave boots, AWS itself measures the exact image (code + config) into a register called PCR0 and signs that measurement. The signer’s KMS key is locked so it will only decrypt your venue secret for an enclave whose PCR0 matches the published build. So a matching PCR0 proves two things at once: the code is the published source, and that code is the only thing that can use your key — not our operators, not your laptop, not a compromised agent.
There's no live value to show right now — cross-check these independent sources against each other; they should all report the same PCR0:
1. From your AI agent (the MCP tool)
Ask your Claude Desktop / Cursor / ElizaOS agent to call get_attestation. The pcr0_sha384 field it returns must match the PCR0 you fetch below.
2. Straight from the gateway
curl -s https://signer-demo.usenami.io:8443/attestation
Returns { "pcr0_sha384": "…", "attestation_doc_b64": "…", "nonce": "…", "timestamp_ms": … }.
3. From the enclave host (if you run your own)
nitro-cli describe-enclaves | jq '.[].Measurements.PCR0'
4. On-chain
isPCR0Active on the Base registry says whether the measurement above is registered right now. This page used to tell you to expect true; it no longer does, because a promise printed in a file goes stale and this one did — for two days after a rotation it promised true for a measurement that same rotation had retired.
The check below runs in your browser, against the public Base RPC. It is your request, not ours — we only render what came back. The PCR0 above we do fetch for you, because that gateway is ours and there is no way around it; the registry is public, and there is.
No measurement came back from the endpoint, so there is nothing to ask the registry about.
Learn more about the Signer: @usenami/signer-mcp · source. One exception to the line above, stated plainly because we would rather you hear it from us: a registry false for the DEMO endpoint between rotations is our lag, not a broken service — the check above says so when it happens. Anything else that does not line up, including a falsefrom production, means something is wrong — please tell us at [email protected].