Govern assets
on your own subnet.
Issue deposit tokens. Whitelist holders, approve movements, export the audit trail.
Private subnet
Your ledger, customers and keys stay on your node.
Quantum-reliable
Post-quantum signatures protect every record, on top of Bitcoin's proof of work.
Tamper-evident record
Every control action is written once for audit.
Built for compliance
Whitelist, limits, approvals and audit, ready for review.
Issue deposit tokens under compliance controls. Whitelist holders. Pause transfers. Cap supply. Quorum signs every change.
Mint and burn
Issue on receipt. Burn on redemption. Cap supply.
Whitelist holders
Only approved addresses may hold the token.
Pause transfers
Stop all transfers when compliance requires it.
You hold the keys. SQRL never does. Signatures stay on your hardware or in your browser.
Trezor hardware wallets
Each signature is made on the device.
Software signing profile
Phrase and password stay in your browser.
What SQRL stores
Public keys and fingerprints only. Nothing that can sign.
Policy before a signature. Limits, allowlists and roles are checked before anyone signs.
Spending limits
Cap each vault and role. Over-cap transfers stop.
Closed until opened
No limit set means no send.
Approved destinations
Transfers only to addresses on your allowlist.
Signers fixed at creation
Signers and threshold cannot change later.
One console for vaults, policy and approvals. Holdings, quorums, limits and pending movements in one place.
Every movement waits
for its quorum.
Limits and allowlists first. Then quorum. Then broadcast. Final.
A record your auditors can export. Policy changes, signatures and broadcasts. Export as CSV.
Audit logs
Write-once log. Filter and export. Export is logged.
Roles and permissions
Eleven permissions, scoped per workspace.
Set up your institution your way. One organisation. Workspaces with their own vaults, people and policy.
Organisation
Your institution. Workspaces and invited people.
Workspaces
A desk or book on mainnet or sandbox.
Vaults
Multi-signature accounts with a fixed signer set.
Your subnet. Your tokens.
Your controls.
Issue on your node. Apply whitelist, limits and quorum before anything leaves.
Same vaults. Same keys. Now across borders. Markets reuses Enterprise policy when you pay other institutions.
Enterprise governs
- Vault
- Whitelist
- Limit
- Quorum
Markets moves
Controls stay on. The same whitelist, limit and quorum apply to the payment.
Enterprise governs. Markets moves. Controls stay on.
Questions from banking teams. Compliance, keys, audit and pilots.
You do. SQRL stores public keys only.
Yes. Only whitelisted addresses can hold it.
Yes. Pause the token at any time, with your quorum's approval.
Limits and allowlists first, then your signers' quorum.
A write-once log of every action, as CSV.
Yes. Start in the sandbox before any client funds move.
Explore the other products. They all run on the same settlement network, under the keys and policies you set.
Start with SQRL Enterprise.
Issue under your keys. Open whitelist, limits and audit to compliance.
