Security
Your funds can only move with your share of the key and your own machine’s agreement. Here is exactly how — no badges, no claims we cannot show.
2-of-2
Every production wallet needs your share to sign
0
Full private keys in existence for MPC wallets
87
Mainnets in MPC, each transaction decoded by your co-signer
Every minute
Health checks, published on our status page
Keys and signing
Non-custodial in production
Every production wallet keeps a key share with you. A full compromise of Chainvara — servers, database and staff — cannot move your funds alone.
MPC, no full key
MPC wallets are generated jointly by our vault and your co-signer: FROST (RFC 9591) for Solana, Bitcoin Taproot, XRP Ledger, Stellar, Aptos, Sui and TON; DKLs23 threshold ECDSA for Ethereum and 76 more EVM networks, Tron, Litecoin and Dogecoin. The private key never exists, not even while signing.
Your co-signer checks every byte
Before adding its signature, your co-signer decodes each chain's own transaction format, recomputes the hash it signs and refuses any other recipient, amount, token, fee, network or extra instruction.
No double payment
One approval can be signed with one nonce, sequence number, seqno or set of coins only: a retry works, a second payment is refused by your own machine.
Shares you can renew
Both shares of an MPC key can be refreshed at any time, address unchanged: a share stolen before the refresh is worthless. Key rows in our database can change only through such a confirmed refresh — never edited or deleted.
Master key in AWS KMS
Vault material is sealed with AES-256-GCM under a key per organization, itself sealed under a platform master key held by AWS KMS.
Embedded wallets on the user's device
Your users' wallets are shared between their device and our vault; the device verifies the exact transaction before signing and never trusts the server's description.
Recovery without custody
A user's device share can be backed up encrypted under a 125-bit recovery code only they hold: we keep the backup for a new phone and can never open it, and every recovery attempt is reported to you.
No seed phrases, ever
We never ask for seed phrases or private keys. Anyone who does is not us.
Policies and approvals
Policy before every signature
Caps, a rolling 24-hour limit, transaction rules, approval tiers, address-book cooldowns and screening run before anything is signed; the approved intent is re-checked before execution.
Rules that fit how you work
Ordered rules by initiator, role, API key, vault, network, asset, operation, destination, amount and time of day — for example, block payments outside office hours.
Approval groups
Require each group to sign off (1 from Finance and 1 from Compliance), by role or named people; a person counts once.
Approvals bound to the transfer
Approvers confirm with a passkey whose signature covers that transfer's intent hash; any change afterwards invalidates the approval.
Governance
Policy, team and execution changes need a second owner or admin, and every policy version is kept forever.
2-of-3 MPC keys
Optionally, every MPC key gets a backup share sealed by your co-signer to your offline recovery key: any two of Chainvara, your co-signer and the backup rebuild the key, and Chainvara never holds two.
Custom roles
A built-in role narrowed per team — request or approve, vaults, networks, USD caps — checked on every request and approval; widening someone's access needs a second admin.
Address poisoning
A destination that imitates a known address (same first and last characters) is refused or held for approval; the incoming bait is marked in the wallet's history.
Token approvals
Every EVM wallet's open approvals — ERC-20, NFT operators, Permit2 — are listed live with what is at risk, can be revoked under the policy, and are watched for new ones.
Kill switch
Execution can be paused per environment instantly; a frozen vault stops its transfers even after approval.
Compliance
Sanctions screening
Every destination is checked against the OFAC sanctions list, refreshed daily; a match is always refused, whatever the approvals.
Blockchain analytics (KYT)
Connect your own Chainalysis, Elliptic or TRM Labs account: destinations are risk-scored before every production transfer, and your policy blocks or requires approval by risk level.
Travel Rule
Beneficiary information is required above your threshold and sealed with your organization key; between network organizations, originator and beneficiary data are exchanged before signing and acknowledged; with any other VASP over the Travel Rule Protocol (TRP v3), whose approval of the exact destination comes before signing.
Inbound screening
The sender of every deposit is screened against sanctions and your analytics providers; flagged funds wait for a compliance decision before your platform credits them.
Counterparty monitoring
Reconciliation flags funds received from or sent to sanctioned addresses.
dApp simulation
Every dApp transaction is simulated first: what leaves and enters the wallet, and every approval or operator right it grants — even hidden inside a router — is shown to approvers and checked against your policy.
Access
Roles
Owner, admin, CFO, treasury manager, compliance, security and developer: each role sees and does only what it needs.
Two-factor and passkeys
Organizations can require two-factor authentication; money movement, approvals, keys, policies and team changes ask for it again.
Guessing is throttled
Repeated wrong passwords or codes pause sign-in for the account and for the network they come from.
API keys
Scoped keys, stored only as hashes, with optional IP allowlists, rate limits, monthly quotas and idempotency keys; test keys can only reach the sandbox.
No account enumeration
Sign-in, sign-up and password reset respond identically whether or not an email is registered.
Exit plan: recovery kit
Register a recovery key created offline; the console exports Chainvara's share of every wallet sealed to it. With your co-signer backup, the open recovery tool rebuilds each private key on your own machine and checks it against the wallet's public key — even if Chainvara no longer existed.
Console access by network
Limit the console to your office or VPN addresses: a stolen password or session is refused from anywhere else, with an owner break-glass path.
Single sign-on
SAML 2.0 with Okta, Microsoft Entra ID or Google Workspace on a DNS-verified domain. When required, only sessions from your own identity provider get in, so removing someone there removes their access here; owners keep a break-glass path.
Data
Tenant isolation
Every record carries its organization and environment, and every query is scoped by them from your verified session or key — never from what a request says.
Append-only evidence
Ledger journals, balance observations and audit events cannot be updated or deleted; the database rejects it.
Your personal data, your call
Each person downloads everything we hold about them (JSON) and deletes their own account from Settings. An organization is never left without an owner able to act on its funds, and the records anti-money-laundering rules require us to keep stay; the rest goes, for good.
Exact amounts
Balances are integers in each asset's smallest unit with 78 digits of precision. No floating point is used for money.
Complete, hash-chained audit trail
Sign-ins, approvals, policy changes, key operations and every change to connected sources are recorded with actor, time, IP and device. Each entry carries the hash of the previous one, so a deletion or edit breaks the chain, and the trail streams to your SIEM.
Web platform
Strict browser policy
Signed-in pages get a per-request nonce Content Security Policy with strict-dynamic; framing, plugins and foreign form targets are forbidden everywhere.
Transport and isolation headers
HSTS with preload, no-sniff, strict referrer and permissions policies, cross-origin opener and resource policies on every response.
No server-side request forgery
Webhook and co-signer URLs are resolved and pinned to public addresses; blockchain and price sources are fixed by us.
Signed webhooks
Every event is HMAC-signed with a timestamp; our TypeScript, Python and Go SDKs verify it in one call.
Operations
Monitored every minute
The API, database, vault, sign-in, background processing, webhooks and blockchain access are checked every minute; incidents open and close automatically and alert our team.
Public status page
Current state, 90 days of uptime per component and every incident are on our status page.
Reviewable by your auditors
We provide a security review pack to penetration testers and cryptography reviewers: scope, claimed properties, key management, protocols, known limitations and how to reproduce our tests.
Encrypted backups
Co-signer shares are backed up encrypted on your side; you keep control of your half.
A co-signer you can verify
The co-signer is published on npm and GitHub with its SHA-256 and a provenance attestation tying each version to its public source commit. It has no dependencies and runs nothing at install; only our release workflow, after an approval with two-factor, can publish it — no npm token exists.
Security programme
Written and approved
Our security policies — roles, access control, change management, incident response, business continuity, vendor management, data retention — were adopted and signed by our founders, and are reviewed at least once a year.
Every change reviewed
No change reaches production without a pull request approved by someone other than its author, after the automated tests and a dependency vulnerability scan pass. GitHub enforces it; nobody can bypass it.
Vulnerabilities fixed on a clock
Every dependency is checked against public vulnerability databases on each change and every week; critical and high findings are fixed within 7 days.
Least privilege
Production access is approved in writing, needs two-factor sign-in, is reviewed every quarter and removed within 24 hours of a departure. Preview builds never get production data or keys.
Logged and watched
Application logs are collected centrally and every use of the vault's master key is logged by AWS; alerts reach the team at once.
Risk and incidents
A formal risk assessment, including fraud and insider misuse, is done every year; incidents follow a written plan with customer notice, a root-cause analysis and, for personal data, notice to the authority within 72 hours.
SOC 2 in preparation
We are preparing a SOC 2 Type I examination by an independent CPA firm, targeted for early 2027. We will say so here once the report is issued, and share it under NDA.
Your part
Your people and their access
Invite only people you trust, give each the narrowest role they need, require two-factor for your organization, and remove someone the day they leave. Review your members and roles regularly.
Your policies
Set limits, approval tiers and the address book to match your risk, and keep production execution off until they are in place. Chainvara applies the rules you set; it does not choose them for you.
Your API keys
Give each key only the scopes it needs, restrict it to your servers' IP addresses, keep it in a secret manager, rotate it, and revoke it at once if it may have leaked.
Your co-signer
Run it on a machine you control and keep up to date, keep its policy strict, back up its encrypted shares, and check the SHA-256 of each new version against the console and GitHub (with npm: pin the version and run npm audit signatures).
Your recovery key and kit
Create the recovery key offline, keep it and the recovery kit apart from each other and from the co-signer backup, and test a recovery from time to time.
Your integrations
Verify the signature of every webhook, use https endpoints you control, and keep exchange keys read-only unless you need withdrawals.
Watching and reporting
Read your alerts, review the audit trail and transfers, and tell us at once at support@chainvara.com if you suspect a compromise.
Not yet in place, and known limits
- No independent penetration test or SOC 2 report yet: both are planned for early 2027 and will be listed above only once done.
- Our FROST implementation comes from an audited library; the DKLs23 threshold-ECDSA library has no public audit we know of yet.
- The vault's share is still decrypted in server memory while signing; the hardware key enclave that ends this (attested confidential VM, master key in an HSM) is built and being switched on. Either way, it cannot sign without yours.
- The platform runs in one region (Europe) for now. Daily off-site exports to a second region (sealed with the vault master key, restore tested) are built and will be listed above once switched on.
Report a vulnerability
Write to support@chainvara.com with “Security” in the subject: what you found, how to reproduce it and what it lets an attacker do. No account is needed. We answer within two business days, keep you informed until it is fixed, and credit you if you wish once it is.
- Test only against your own account and the sandbox. Never access, change or keep data that is not yours; stop and tell us if you reach some.
- No denial of service, spam, social engineering or physical attacks, and no testing of our providers’ systems.
- Give us a reasonable time to fix before telling anyone else.
We will not take action against research done in good faith within these rules. Machine-readable contact: security.txt.