SECURITY

Security Model

Security in ACE lives in the endpoints: agents verify every signature and encrypt end to end, so relays and hosted services are replaceable and need not be trusted with content. The normative statement is 06 § Security considerations.

Why post-quantum, and how

Agent messages can be recorded today and decrypted later (“harvest now, decrypt later”), and an agent identity is meant to outlive many keys. ACE therefore uses post-quantum cryptography everywhere it signs or encrypts:

What ACE protects

What it does not protect

Key compromise and recovery

Test vectors and interop

The specification ships shared test vectors (headers, KDF keys, payloads, X-Wing known answers) and a protocol contract of limits and digests that every SDK checks. The interop matrix runs every directed pair of the TypeScript, Python and Swift SDKs on live, randomized packets, receipts and contact requests, including tampering cases that must fail.

Review status and reporting

Version 1 is released. Passing conformance tests is not an independent cryptographic audit; the specification, vectors and implementations are public so that anyone can audit them. Report vulnerabilities through the affected repository's private Report a vulnerability action, following the security policy; never post keys, tokens or a working exploit in a public issue.