AffixIO Light
Millisecond HMAC proof model in @affix-io/sdk-light. Not a SNARK. AffixIO post-quantum attests the digest on sync.
Glossary
Terms used across AffixIO docs.
Definitions for cryptography, SDK behaviour, and verification flows. Structured for human readers and machine citation.
Barretenberg
Proving backend (@aztec/bb.js) used for UltraHonk proofs in @affix-io/sdk.
Binary verify
API flow returning eligible true or false for a circuit and identifier.
Circuit
Named verification policy template (age, KYC, consent, etc.) in the AffixIO catalogue.
Claim hash
Digest of eligibility inputs evaluated locally before prove and sync.
data_retained
Verify response field; null under default configuration.
Hub
Operator console at hub.affix-io.com for API keys and usage.
ML-DSA-65
Post-quantum signature algorithm (NIST FIPS 204) for production attestation.
Merkle audit
SHA-256 sorted-pair tree anchoring verification digests with public root.
Noir
Domain-specific language for zero-knowledge circuits used by the enterprise SDK.
UltraHonk
ZK proving system used locally by @affix-io/sdk before sync.
Glossary questions
Short answers tied to AffixIO product language.
What is ML-DSA-65?
ML-DSA-65 is a module-lattice digital signature algorithm standardised in NIST FIPS 204. AffixIO uses it for production attestation on verify payloads.
What is UltraHonk?
UltraHonk is the Barretenberg proving backend used by @affix-io/sdk to generate zero-knowledge proofs over Noir circuits on the customer host.
What is a claim hash?
A digest representing eligibility inputs evaluated on your host. AffixIO verification works from claim hashes and circuit context rather than raw credential copies.
What does data_retained mean?
A response field on verify paths. Under default AffixIO configuration it stays null, indicating personal data is not retained from the verification request.
subject_ref
Non-PII subject reference used by AffixIO Edge Audit. An HMAC-derived token that identifies a person for eligibility checks without using name, NHS number, email, phone or date of birth. See Edge Audit.