Deploy privacy. Stay compliant.
Our enclaves hold the audit keys for privacy-enabled stablecoins, rollups and networks — so issuers can meet their compliance obligations without running key custody themselves. Nobody gets the actual keys. Not even us.
StarkWare · Starknet
Live on mainnet — holding the master audit key on the STRK20 privacy pool. Screening on deposit; scoped disclosure under lawful request.
Canton Network
On testnet — running a validator on the Canton Network. Accepting inquiries from asset issuers for our soon-to-be-launched app.
Cited by RUSI
Named by the Royal United Services Institute as a practical model for privacy-enhancing technology in regulated finance.
Read: StarkWare on the STRK20 compliance design → · Starknet privacy whitepaper →
Four reasons to reveal. One custodian for all of them.
Law enforcement
An investigation arrives with a warrant and a scope. We verify the legal basis and disclose only what it covers.
Exchange risk
A token arrives at an exchange. Where did it spend time? Is it clean? They run analytics before accepting it.
Preemptive hygiene
Issuer-initiated, continuous screening for bad funds — finding problems before they become incidents.
Solvency check
If the cryptography ever fails, the audit-key holder can verify the supply is sound — no tokens minted in secret.
One custodian for the keys, the warrants, and the disclosure.
Hold the keys
We take custody of the audit key on behalf of the issuer or ecosystem, with a managed backup so the keys can always be moved out.
Disclose under lawful request
Our counsel verifies the legal basis and sets the scope. We reveal only what it covers — never the whole key.
Open to analytics
Approved compliance firms run their tools on the disclosed data — they get the result, never the keys or the raw data.
When the ledger goes private, the obligations don’t change. Meeting them gets harder.
Hold and run the audit key yourself, and a leak exposes every user who was promised privacy. Don’t hold it — or lose it — and there’s no answer when bad funds enter the pool and an investigator comes asking.
It’s the same question on every privacy chain: who holds the keys, and under what conditions can they be used? Everyone wants the privacy; nobody wants to run the key custody.
Keys stay safely stored — we decrypt only what’s in scope, and hand back the result re-encrypted.
Everything runs inside sealed, attested enclaves — even our own engineers can’t reach in. One enclave safeguards the keys; a second runs the analysis. Results go re-encrypted straight to the legally authorized recipient.
Two recent incidents an audit key would have changed.
An issuer froze an entire shielded pool
After bad funds entered, the only available move was to freeze every holder — not just the bad actor.
With an audit key, you trace where the bad funds landed and freeze those specific addresses — leaving everyone else untouched.
A cryptographic bug let tokens be minted in secret
A privacy chain found a flaw that, in principle, allowed tokens to be created with no one able to see it.
With an audit key, the holder runs a solvency check — catching a silent failure before it becomes a loss.
We represent the issuer. We work for the ecosystem.
Our enclaves hold the key so issuers don’t have to.
A dedicated operator for the hardest part — keeping a key safe, usable, and never leaked.
Analytics firms run on the data — not the keys.
They get the result, without ever holding the keys or the raw data, inside an environment we control.
A first point of contact when the chain goes dark.
When an investigation hits a private chain, there’s a place to bring the warrant — with a playbook for lawful, scoped disclosure.
The ledger is going private, and the compliance architecture for it doesn’t exist yet.
Regulators see confidential tokens as necessary for payments at scale — and full transaction visibility as a liability of its own. The GENIUS Act puts the obligations on the issuer.
Selective disclosure already exists in every other regulated sector — crypto is the outlier without it.
When the underlying asset is centralized, you keep the ledger at the issuer and don’t reveal it. That’s the bet behind Canton — exactly where FPI operates.
The same model the regulated financial system has used for decades — independent custodians, with no commercial interest in the underlying assets — applied to the keys behind private digital money.
Built by the team behind QEDIT and Bits of Gold — with board and counsel oversight. About the team →
Deploy privacy. Stay compliant.
Live with StarkWare on Starknet. Running a validator on Canton testnet.
Contact us ››