BenchmarksStack Ranking
APIsPricingDocsWhite PaperTokenBlogAboutSecurity Demo
Log InGet API Key
Available on AWS

The H33-74 on AWS

Every computation result your application produces — attested by a 74-byte post-quantum H33-74, signed under three independent NIST signature families, and anchored to the Bitcoin blockchain. Deploy on AWS in under 5 minutes. No rebuilds.

Flagship H33-74

74 bytes. Three post-quantum families. Anchored to Bitcoin.

The H33-74 is a fixed-width, computation-agnostic commitment object that binds any computation result to a post-quantum attestation under three independent NIST signature families. The full 21 KB ephemeral signature bundle is distilled to 74 persistent bytes — 32 on-chain, 42 off-chain — at a 284.5:1 compression ratio. Patent pending.

74 B
Total persistent footprint
32-byte on-chain anchor (SHA3-256 signing message) + 42-byte compact receipt with verification digest
42 µs
Per attestation
Full pipeline: FHE batch verify + three-family sign + ZK-STARK cached lookup. Graviton4 metal, 96 workers.
1.67M
Attestations per second
Sustained 30-second measurement on c8g.metal-48xl with CacheeEngine and CMS admission.
Three Independent Hardness Assumptions
ML-DSA-65
FIPS 204 · Lattice (MLWE)
1,952 B public key · 3,309 B signature · NIST Level 3
FALCON-512
Draft FIPS 206 · Lattice (NTRU)
897 B public key · 649–666 B signature · NIST Level 1
SLH-DSA-SHA2-128f
FIPS 205 · Hash-based
32 B public key · 17,088 B signature · NIST Level 1
Bitcoin-Anchored via Taproot
Every H33-74 is anchored to the Bitcoin blockchain via Taproot key-path tweak — adding zero marginal weight to the transaction. The 32-byte signing message m(S) = SHA3-256(S) serves as both the on-chain anchor and the canonical usage meter. No soft fork. No new opcodes. No consensus changes.

Four ways to deploy. Same H33-74.

Every integration path produces the same 74-byte H33-74, the same three-family PQ signatures, the same Bitcoin anchor. Pick the deployment that matches how you build.

~3 minutes
Option 1

CloudFormation (One-Click)

Deploy an API Gateway + Lambda proxy that produces a 74-byte H33-74 for every API call. Your existing application code doesn't change. The proxy runs the full pipeline — FHE encryption, three-family PQ attestation, ZK-STARK proof, and Bitcoin anchoring — on every request.

What you get
API Gateway endpoint Lambda function CloudWatch logging
Launch Stack
Instant
Option 2

AWS Marketplace

Subscribe to H33 through AWS Marketplace. Billing goes through your existing AWS account — no new vendor approval, no procurement process. Usage-based pricing: pay per H33-74 attestation through AWS metering.

What you get
AWS billing integration SaaS subscription Usage metering
View on Marketplace
~2 minutes
Option 3

Lambda Layer

Add the H33 Lambda Layer to any function. Import h33, call h33.attest(), h33.verify(), h33.encrypt(). Each call produces an H33-74 — 74 bytes of post-quantum attestation with Bitcoin anchoring. Works with Node.js 18/20 and Python 3.11/3.12.

const h33 = require('h33-pq');

// Attest any computation result — returns 74-byte H33-74
const primitive = await h33.attest(event.body);

// Verify an H33-74 — checks all three PQ families
const valid = await h33.verify(primitive);
LAYER ARN (us-east-1)
arn:aws:lambda:us-east-1:329646112703:layer:h33-pq:1
View Docs
~1 hour (with H33 support)
Option 4

PrivateLink

Enterprise-grade private connectivity. H33-74 attestation traffic stays on the AWS backbone — never traverses the public internet. Deploy an interface VPC endpoint in your VPC and all H33-74 operations route through AWS's private network.

What you get
VPC endpoint Private DNS No internet exposure
Contact for PrivateLink

Before and after H33-74

Your architecture stays the same. Every result gets a 74-byte post-quantum attestation anchored to Bitcoin.

Before
Your API call
AWS KMS (classical encryption)
Your database
H33 Proxy
After
Your API call
H33-74 Proxy
74-byte H33-74 (3 PQ families)
Bitcoin anchor (Taproot)
Your database (post-quantum attested)

Your first H33-74 attestation

After the CloudFormation stack deploys, your endpoint is ready. One curl command to produce a 74-byte H33-74.

terminal
# After CloudFormation deploy, your endpoint is ready:
curl -X POST https://YOUR-API-ID.execute-api.us-east-1.amazonaws.com/h33/attest \
  -H "Content-Type: application/json" \
  -d '{"data": "sensitive-payload", "sensitive_fields": [42, 100]}'
74 B
H33-74 width
42µs
Per attestation
1.67M
Attestations / second
3
PQ signature families

Start attesting your AWS workloads today

Get a free API key with 1,000 H33-74 attestations per month. Launch a CloudFormation stack in 3 minutes. No credit card required to start.

Verify It Yourself