Zero-knowledge proof mode
UltraHonk
Use a supported Noir circuit to prove that its constraints were satisfied. Proof generation runs in your application environment using Barretenberg.
UltraHonk configurationAffixIO SDK 2.0.4
One SDK. Choose the proof your check needs.
Install affixio for Node.js 20 or later. The package supports local UltraHonk zero-knowledge proofs and HMAC proof envelopes, with different verification assumptions.
Authenticated evidence mode
HMAC
Bind a decision to an authenticated local envelope. This mode is useful where the integration accepts the producer and shared-secret trust model.
Local proof and verificationCompare the verification boundary
| Question | UltraHonk | HMAC |
|---|---|---|
| What is checked? | The configured circuit relation | The authenticity and integrity of a keyed envelope |
| Is it zero knowledge? | Yes, for the supported ZK circuit and proof path | No |
| Where is it produced? | Your application host | Your application host |
| Does it establish source truth? | Only the relation proved over the supplied inputs | Only the recorded decision and its authenticated envelope |
| Does it replace payment authorisation? | No | No |
Keep the layers distinct
A proof, a signature and an audit entry answer different questions. A proof checks a relation. A signature binds evidence to a signing key. Merkle inclusion shows that a digest belongs to a particular audit root. None makes an inaccurate source record correct.
Trust model (SDK 2.0.4): verification fails closed against pinned keys (trustedSigningKeys; fetchAffixioKeys with expectedKeys via /v1/keys). POST /api/attest returns server_verified:false and is not proof of validity; use POST /v1/attest/proof or verify with requestAttestation: true. The server Merkle root is unsigned and holds a rolling 50,000 leaves. 1.x is deprecated for a security flaw; upgrade to 2.0.x. Details: /docs/#trust-model.
ML-DSA-65 is the post-quantum signature layer. That does not make every component of the proof system post-quantum secure. Review the security documentation and published NIST alignment against your requirements.
Connect the source you already use
The SDK can check configured database records, HTTP JSON services and file exports. Keep source access in your service, handle an unavailable source separately from a failed check, and retain the policy and evidence references needed to explain the decision.
See SQL, API and file examples. For an agent workflow, continue to Agentic Pay Kit or BoundProof Agent.
SDK questions
Which npm package should I install?
Install affixio. The current release is 2.0.4 and requires Node.js 20 or later. UltraHonk and HMAC are modes in this package, not two separate SDK products.
Can I run the SDK in a public browser?
The published package targets Node.js. A browser interface can call your trusted backend. Keep SDK API keys, payment secrets and shared verification secrets on that backend.
Does offline verification need a fresh API request?
The SDK includes local verification and offline evidence utilities. Whether an operation also needs a licence, quota check or later synchronisation depends on the selected workflow. Follow the documentation for that operation.
Evidence matters more than the model label
AI, SI and ASI terminology does not change the trust assumptions of an evidence mode. A shared-secret record, zero-knowledge proof and signed attestation establish different facts. Select the mode and trusted keys for the defined check, not because an assistant is marketed as personal superintelligence.
AI, superintelligence (SI), ASI and personal superintelligence: terms and boundaries