What Aqua builds on.
The standards the Aqua protocol specification relies on, and what each one does for your evidence.
RFC 9162
Certificate Transparency 2.0
Merkle trees and inclusion proofs for batches of evidence
RFC 6962
Certificate Transparency
The Merkle tree hashing that RFC 9162 builds on
RFC 3161
Time-Stamp Protocol
Trusted timestamps from a timestamp authority
RFC 5869
HKDF
Salts that keep withheld fields private
RFC 8032
Ed25519
Digital signatures
RFC 8785
JSON Canonicalization Scheme
The rules for writing text inside Aqua’s own exact byte form for signed data
FIPS 202
SHA-3
Hashing
FIPS 204
ML-DSA
Post-quantum signatures
EIP-191
Ethereum signed messages
Wallet signatures
What we are assessing.
New and revised standards that touch the protocol. Each one gets a written assessment; its status appears here once that assessment is closed.
- RFC 9964, ML-DSA for JOSE and COSE
- RFC 9942 and RFC 9943, COSE Receipts and the SCITT architecture
- RFC 9921, RFC 3161 timestamps in COSE
- RFC 9995, COSE Hash Envelope
- RFC 9864, fully specified algorithm identifiers
- NIST post-quantum transition guidance (IR 8547, SP 800-230)
- W3C Decentralized Identifiers 1.1
- W3C WebAuthn Level 3
- EIP-7951, the P-256 precompile on Ethereum
A standard describes technology, not who is responsible for using it: what we report, and what we don’t.
Need a standard we don’t list?
Tell us which one your organisation works with, and we look at how Aqua relates to it.