Forge a credential. You can’t.
Here is one genuinely valid ATX credential and a verifier that runs real cryptography in your browser. Tamper a field, mint your own key and re-sign it, paste a forged Ed25519 or post-quantum signature, outlast its lifetime, replay it after revocation. Every attack runs against a real check: Ed25519, a real ML-DSA-65 post-quantum signature, and the issuer-to-key binding OpenA2A actually ships. Nothing is scripted. Open your network tab: nothing leaves this page.
TAMPER A SIGNED FIELD
Edit what the credential claims. The bytes the signature covers change the instant you do.
RE-SIGN WITH YOUR OWN KEY
Mint a real Ed25519 keypair in your browser and sign the tampered credential with it. The math will be perfect. Watch what the verifier does anyway.
FORGE THE SIGNATURE DIRECTLY
Paste any Ed25519 signature hex you like in place of the real one.
Paste any hex in place of the ML-DSA-65 post-quantum signature. The Ed25519 signature stays untouched.
OUTLAST OR REPLAY IT
{"agentDid":"did:opena2a:agent:agent_conformance_test_001","agentId":"agent_conformance_test_001","atcVersion":"1.1","behavioralProfile":{"checksum":"sha256:ghi789","generatedAt":"2026-05-19T00:00:00Z","observationDays":14},"buildAttestation":"https://slsa.dev/provenance/v1#opena2a-conformance","capabilities":["read:public","write:owned"],"contentHash":"0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff","expiresAt":"2099-12-31T23:59:59Z","issuedAt":"2026-05-23T00:00:00Z","issuerChain":["did:opena2a:authority:opena2a.org-root","did:opena2a:authority:opena2a.org"],"issuerDid":"did:opena2a:authority:opena2a.org","publisher":"opena2a-conformance","publisherDid":"did:opena2a:publisher:opena2a-conformance","scanSummary":{"criticalFindings":0,"cryptoServe":"no-weak-crypto","highFindings":0,"hma":"passed","oasbLevel":"L1","secretless":"clean"},"trustLevel":4,"trustScore":"87.500000","version":"1.0.0"}verifying…
The credential is the ATX 1.1 hybrid fixture of the atx-conformance suite, byte for byte. Its Ed25519 and ML-DSA-65 (FIPS 204) signatures are verified for real in your browser via @noble/curves and @noble/post-quantum, over JCS(TBS), the bytes atx-spec core.md §1.3a.2 defines, against the keys the suite pins. Tamper any signed field and both fail. Those keys are the suite’s published test keys: the Ed25519 key is the RFC 8032 test key, and the suite publishes each key’s seed, so a signature made with those seeds verifies here; this page never carries the seeds. When you “re-sign with your own key”, a real Ed25519 keypair is generated in your tab and signs for real; the secret never leaves it. The verifier accepts a credential only when both signatures verify against the keys pinned for its issuer, inside its lifetime and off the revocation list. Revocation is a locally cached list plus a short lifetime (seven days for an issued ATX; this fixture’s runs to 2099 so it stays verifiable), not a live lookup. Production uses the same model.
