Device-bound approval
The non-exportable device share is bound to Secure Enclave / StrongBox. Mobile App provides biometric approval with what-you-see-is-what-you-sign.
Modules
Mobile App
WALLET INFRASTRUCTURE
Build your customer service on a controlled custody core.
Serve your own customers with institutional wallets, a platform API and an event model.
Talk to salesBuilt for
- Banks
- Fintechs
- Crypto platforms
Capabilities for your workflow
A bank-protected signing participant
The platform share uses HSM/KMS envelope encryption in the bank. Network accompanies the custody core across EVM, Bitcoin, Solana and Tron; signing uses DKLS23 or FROST for the applicable chain.
Modules
Network
A workflow interface for your systems
The platform API has 175 endpoints and 64 event types. Mobile App and Network sit within that platform’s approval and chain workflows.
Modules
- Mobile App
- Network
How it works
Set the custody policy
Define roles, limits and approved destinations for the customer workflow.
Route the instruction
Connect the bank’s systems to the platform API and event model; apply policy and maker-checker approvals.
Sign with both shares
After biometric approval, device and platform shares sign through an untrusted coordinator that cannot see either share.
Retain workflow evidence
Preserve the authorization trail in the WORM evidence log.
- Policy engine
- Maker-checker approvals
- Transaction limits
- Address whitelists
- Immutable WORM evidence log
