Entropy and key-transport infrastructure for wallets, dApps, and on-chain protocols. Non-custodial. Audit-proven per draw.
Wallet keys and VRF outputs are often seeded from predictable or low-entropy sources. A single weak draw compromises every derived key.
ECDSA and EdDSA signatures on-chain are public and permanent. A cryptographically relevant quantum computer can recover private keys from exposed public addresses.
Most entropy providers return raw bytes with no provenance. You cannot prove to auditors, regulators, or users where the randomness came from.
The same entropy and audit infrastructure used by regulated enterprises, exposed as APIs that wallets and dApps can call today.
Every draw returns entropy with a signed provenance record: source class, backend identifier, entropy score, health-test results, and audit batch linkage.
POST /v1/entropy/encrypted delivers entropy under ML-KEM-1024 so the API hop itself is quantum-safe. The client decapsulates locally.
QSG issues entropy and proofs. The client derives keys locally. Nothing ever leaves the user's device. That is the only honest non-custodial story.
Every draw is written to KV for fast lookup and R2 JSONL for compliance. Replay verification is available on Verified and Enterprise tiers.
Three API calls cover the typical Web3 flow.
Private beta — contact us to join. Request body:
{
"format": "base64",
"length": 32,
"suite": "QSG-HYBRID-1",
"client_public_keys": {
"x25519": "<base64url 32 bytes>",
"ml_kem_1024": "<base64url 1568 bytes>"
},
"client_nonce": "<base64url >= 16 bytes>",
"key_id": "my-key-001"
}
The wallet decapsulates locally and HKDF-expands into a seed.
{
"success": true,
"request_id": "550e8400-e29b-41d4-a716-446655440000",
"timestamp": "2026-09-02T14:22:08.117Z",
"suite": "QSG-HYBRID-1",
"kem_ciphertext": "base64url — 1600 bytes: X25519-eph-pub(32) || ML-KEM-1024-CT(1568)",
"ciphertext": "base64url — AES-256-GCM ciphertext",
"nonce": "base64url — 12-byte nonce",
"tag": "base64url — 16-byte GCM tag",
"aad_hash": "base64url — SHA-256 of canonical AAD (see protocol doc)",
"expires_at": "2026-09-02T14:27:08.117Z",
"format": "base64",
"length": 32,
"provenance": {
"source_class": "hardware-derived",
"source_id": "batch-2026-06-10-001",
"entropy_score": 0.9946,
"conditioning": "HKDF-SHA-256"
},
"rate_limit": {
"remaining": 499,
"reset_at": 1756902000000
}
}
The wallet or dApp then:
request_id for audit lookup via GET /v1/audit/:id.The chain still sees a normal ECDSA transaction. Quantum risk on the seed and the API hop is already reduced.
QSG competes on auditability, not on consumer wallets or patented SDKs.
| Product | Gateway Job | Web3 Surface | How It Lands |
|---|---|---|---|
| QSG This | Entropy + hybrid KEM + key lifecycle | APIs, wallet seed material, audit trail | Hardware-derived draws, SP 800-90B gating, FIPS 203 at the edge |
| QuantZen | Dual-signature overlay | Wallets, dApps, live transactions | ML-DSA beside ECDSA; no hard fork |
| KuCoin PQC Gateway | PQC HTTPS gateway | Exchange + Web2/Web3 TLS | Browser hybrid KEM; fallback for old clients |
| Qubit | Entropy layer + QaaS | Wallets, oracles, AI | Hardware entropy → keys, with on-chain optional commit |
| Chainlink / CCIP | Crypto-agile interoperability | Oracles, RWA, cross-chain | FIPS 203/204 roadmap; hybrid migration |
QSG does not compete with consumer wallets or dual-sign SDKs. We compete on auditability: SP 800-90B gating, per-draw signatures, crypto-agile KEM, and a documented non-custodial boundary.
Every POST /v1/entropy call returns a signed provenance record. Wallet consumers get the same audit trail as enterprise HTTPS clients.
/v1/entropy/encrypted becomes the default Web3 hop. ML-KEM-1024 ciphertext eliminates quantum record-and-decrypt risk on the API transport.
ML-DSA-65 + ECDSA for EVM transactions, without touching L1. Available as a signed wrapper for wallets that want forward-compatible signatures.
Sandbox keys provisioned automatically. Full response shape, full audit chain.