Skip to main content
Compliance Gate for Substrate 2 (v2) — the commercial, packaged version of the compliance gate that runs in the AlgoVoi production gateway. The open A2A Compliance Gate Extension protocol specification is published separately as v1.

​
What it is

Compliance Gate turns a screening decision into a signed, no-PII compliance receipt. You screen a payer through your own sanctions / PEP / AML provider; the Gate maps the result to a categorical ALLOW / REFER / DENY verdict and emits a Falcon-1024-signed receipt whose payer reference is a content hash — never the cleartext. It is the same compliance gate that runs in the AlgoVoi production gateway, packaged for Substrate 2 as a standalone OEM SDK you can embed in your own product. It is the origination side of Proofs: the receipt the Gate produces is exactly the one Proofs binds and proves. Use the Gate to make and sign the compliance decision; use Proofs to prove it privately downstream. It does not perform the sanctions lookup itself — that’s your provider’s data. The Gate is the certification, privacy, and provability layer on top: it takes a verdict and turns it into auditable, shareable, post-quantum-signed evidence.

No PII in the receipt

The address goes in (you have to screen it); only sha256(network:address) comes out. The signed receipt is shareable with a regulator or partner with nothing personal in it.

Categorical, audit-grade verdict

ALLOW / REFER / DENY is a closed enumeration — a REFER (e.g. a Suspicious Activity Report obligation) is byte-distinct from a DENY, and the verdict is post-quantum signed.

Bring your own screening

Inject any provider — Chainalysis, TRM, Elliptic, an internal list — behind a small interface. The Gate orchestrates and certifies; it never holds sanctions data.

Produces what Proofs proves

The receipt format and content hash match Proofs exactly, so a Gate verdict drops straight into a privacy-preserving proof.

​
What you get

  • A verdict you can share. A signed compliance receipt you can hand a regulator or counterparty with no customer PII in it — not the raw, data-laden output of a screening provider.
  • Provider-agnostic. Keep your existing screening vendor; bolt the Gate on top to certify its verdicts. No switching cost, and we never compete with the data providers.
  • A complete compliance pipeline. Gate (make + sign the decision) → Proofs (prove it privately) is an end-to-end story: produce the verdict, then prove it without exposing the data.
  • Quantum-resistant, offline-verifiable. Every receipt is Falcon-1024 signed and verifies from the public key alone — no callback, no shared infrastructure.
  • Optionally Substrate 2-bound. Fold each compliance verdict into the broader Substrate 2 evidence chain.

​
How it works

StepWhat happens
ScreenYour injected provider checks the payer (sanctions / PEP / AML).
MapThe result becomes a categorical ALLOW / REFER / DENY.
CertifyBind a content-addressed payer reference and sign the receipt (Falcon-1024).
Verify / proveVerify the receipt offline, or feed it to Proofs to prove the verdict privately.

​
Cryptography

  • Post-quantum signing. The ALLOW/REFER/DENY verdict is a Falcon-1024-signed (NIST Level 5), no-PII, offline-verifiable receipt. The gate performs no zero-knowledge proof itself — it produces the categorical verdict that Proofs can later prove privately.

​
Why commercial

The certification and verifier layer was never published as open source — there is no free tier to fall back on. It is offered as a commercial product because the value is in a maintained, privacy-preserving compliance-evidence capability:
  • Embed without attribution overhead. A commercial OEM licence lets you ship it inside your own product with no open-source notice obligations.
  • Enterprise terms. Support, warranty, and a defined relationship — for a compliance-critical dependency.
  • Maintained crypto suite. Post-quantum primitives and the receipt format are ongoing work, bundled into the licence.

​
Who it’s for

  • Regulated PSPs, VASPs, and exchanges that must evidence screening to a regulator or partner without exposing customer PII.
  • Crypto platforms already paying a screening vendor that want a signed, shareable, provable verdict on top of raw provider output.
  • Compliance / MLRO teams that need an audit trail of ALLOW / REFER / DENY decisions.
  • Anyone who needs to certify a compliance decision without disclosing the data behind it.

​
Get Compliance Gate

Compliance Gate is an additional, separately-licensed package — an add-on that binds to Substrate 2, not part of Substrate 2 itself. It pairs with Proofs as a “produce → prove” compliance pipeline. It is available self-serve as a Starter licence (see below) and as a commercial OEM SDK and is included in the AlgoVoi Enterprise and On-premise plans. It is not distributed on public package registries.

Buy Starter — $6,000

Starter licence — perpetual, self-hosted, paid in USDC on mainnet. The store issues your licence key + install command on settlement; install from the private index and set ALGOVOI_LICENSE_KEY to run. Enterprise / OEM (warranty, indemnity, SLA, multi-deployment, Substrate 2 binding): email us.