# Majax Messenger cryptographic verification

Canonical human-readable page:
- https://majax.fr/verification-cryptographique/

Machine-readable resources:
- https://majax.fr/verification-cryptographique/data/manifest.json
- https://majax.fr/verification-cryptographique/data/latest-attestation.json
- https://majax.fr/verification-cryptographique/data/latest-attestation.statement.json
- https://majax.fr/verification-cryptographique/data/latest-attestation.sig
- https://majax.fr/verification-cryptographique/data/public-attestation-ed25519.pem

Canonical origin resources:
- https://majax.app:8443/.well-known/majax-security.json
- https://majax.app:8443/security/latest-attestation.json

Declared architecture:
- Algorithm: ML-KEM-1024
- Separated cryptographic domains: messages, voice, media, rtc, identity
- Domain count: 5
- Rotation policy: daily with a bounded overlap

Verification scope:
- Ephemeral test keys only
- No production key or shared secret
- No user account, message or media
- No production log or environment file
- No administrative interface

Executed ML-KEM-1024 checks for each of the five domains:
- Exact algorithm identifier
- Standard ML-KEM-1024 object dimensions: 1568-byte public key, 3168-byte private key, 1568-byte ciphertext, 32-byte shared secret
- Encapsulation and decapsulation reciprocity
- Distinct ephemeral key pairs on successive generations
- Implicit rejection of a bit-altered ciphertext: the original shared secret is not recovered
- Cross-domain private-key isolation: a private key from another domain does not recover the original shared secret

Executed Maurice HMAC v2 checks:
- Canonical form METHOD|PATH|TS|NONCE|DEVICE_ID|SHA256(BODY)
- Binding to the deployed middleware source by SHA-256 and source invariants
- Acceptance of a valid canonical request in the independent reference model
- Rejection of an exact replay
- Rejection after body or path mutation
- Fresh random nonce uniqueness

Explicitly not evaluated by the current public suite:
- Execution of the Android Signal engine and the nested Signal/KEM composition
- Signal forward secrecy
- Signal post-compromise recovery
- Application-wide nonce handling outside Maurice requests

NOT_EVALUATED does not mean FAIL. It means that the property requires a production-compatible Android or stateful two-party harness that is not part of this server-side public suite.

The signed result is an automated technical self-attestation. It is not presented as an independent audit or certification.