Product updates

What shipped

Every update to the platform, newest first. Each one goes through the same policy, approvals and co-signer checks as the rest of Chainvara.

October 9, 2026

  • Developers

    The co-signer on npm

    Install it with npm install -g @chainvara/cosigner@1.2.3, then chainvara-cosigner setup and serve. Every version is published only by our GitHub workflow, after an approval, with a provenance attestation tying it to its commit; no npm token exists, so nobody can publish it any other way (npm trusted publishing); it has no dependencies and runs nothing at install. It starts correctly when run through a symlink (Linux and macOS package managers) and shows its version. Since 1.2.3 a second co-signer can no longer start on the same data folder, a port already in use gives a plain message, and errors never print a stack trace.

    Learn more
  • Developers

    Automations by API, and steadier sweeps

    Create, pause and delete sweeps, top-ups and balance alerts with /api/v1/automations: destinations are always your own wallets, and every transfer a rule creates still follows your policy, approvals and co-signer. A wallet that has just sent is now left alone until its balance is read again, so a sweep never fires twice on the same funds. Solana deposits now name their sender in deposit.received.

    Learn more
  • Payments

    Promo codes that last several months

    A promo code can now discount your first month, your first few months or every month. When you renew within that span, checkout applies the code on its own and shows which month of the discount you are on; after it, the plan renews at its normal price. You can remove the code from checkout at any time.

    Learn more

October 8, 2026

  • Security

    Our security programme, in writing

    Chainvara's security policies are adopted and signed: every change to production needs a second person's approval, dependencies are scanned for vulnerabilities on every change and every week, production access is least-privilege and reviewed quarterly, logs are centralized, and incidents follow a written plan. The security page now lists the programme and what each customer controls on its side. A SOC 2 Type I examination is targeted for early 2027.

    Learn more
  • Security

    Co-signer update: threshold-signature module

    A new co-signer build ships the threshold-ECDSA module rebuilt with two upstream Rust security updates (cmov 0.5.4, rand 0.10.1). Neither issue could be reached in the co-signer, which runs the module as WebAssembly, but we recommend updating: download it from Developers → API co-signer and check that its SHA-256 matches the one shown there and on GitHub.

    Learn more
  • Payments

    Promo codes at checkout

    Have a promo code? Enter it when you pay for a plan: the discount shows before you get your payment address, and the invoice lists the plan price, the discount and the code. The discount applies to that payment; renewals are at the plan price.

    Learn more
  • Developers

    A readable API reference

    Every endpoint on one page: method, path, the scope its key needs, parameters, request body and responses, generated from the same OpenAPI file your tools read, so it is never out of date.

    Learn more
  • Platform

    Terms, privacy and data processing

    The Terms of Service, Privacy Policy, Acceptable Use Policy, Data Processing Addendum (GDPR article 28), subprocessors and legal notice are published under Legal. No advertising or analytics trackers are used anywhere on Chainvara.

    Learn more
  • Platform

    Live chat with the Chainvara team

    A chat button on the website, the sign-in pages and every console page: write to us and a person from the team answers in the same window within seconds of replying, and by email if you have left. Each conversation is a numbered ticket; signed-in customers are recognised by their account, visitors only leave an email. Never share a password, key or recovery phrase in it: we will never ask.

  • Developers

    Every endpoint in every SDK and in the OpenAPI file

    The TypeScript, Python, Go, Java and .NET SDKs now cover the whole API — deposit addresses, network fee estimates, MPC key refresh, inbound screening, network Travel Rule messages and proof-of-reserves snapshots, plus, in Java and .NET, the payment network, embedded wallets, swaps, screening, security posture, payees, prices, tokens and address proofs — each tested against a real local server. The OpenAPI specification documents every route, payouts, previews, tags and reports included.

    Learn more
  • Security

    Report a vulnerability

    A responsible-disclosure policy on the security page and a standard /.well-known/security.txt: write to us without an account, an answer within two business days, and no action against good-faith research.

    Learn more
  • Security

    Download your data, delete your account

    Settings → Your data: download everything Chainvara holds about you as JSON (organizations and roles, passkeys and devices, your approvals, your activity), or delete your account — you leave every organization and are signed out everywhere, and the account can never be used again. An organization is never left without an owner, nor with production wallets nobody can reach; the audit trail and approvals are kept as anti-money-laundering rules require.

    Learn more

October 7, 2026

  • Developers

    Java and .NET SDKs

    Two more single-file, dependency-free SDKs — Java 11+ (java.net.http) and .NET 6+ (HttpClient, System.Text.Json) — with the same resources as the others, retries, idempotency keys, typed errors, pagination, webhook verification (secret rotation included) and co-signer signatures. Download them with their SHA-256 in Docs.

    Learn more
  • Compliance

    Travel Rule with any VASP (TRP v3)

    Add the beneficiary's Travel Address (ta…) to a transfer: their VASP receives the IVMS101 data and must approve exactly the destination before anything is signed, then gets the transaction id once broadcast. In Compliance, publish Travel Addresses for your wallets: inquiries to them are answered with that wallet's address and their originator data is stored sealed (travel_rule.received). Optional client certificate (mTLS) and LEI.

    Learn more
  • Wallets

    Coin control for Bitcoin, Litecoin and Dogecoin

    Each Bitcoin-family wallet page lists its coins: freeze one (with a reason) and no payment, payout batch or consolidation spends it until it is released. Freezing is open to treasury, compliance and security; releasing to owners, admins, CFOs and compliance; both are audited.

    Learn more
  • Developers

    Use vault wallets from viem, ethers and Hardhat

    The TypeScript SDK's cv.eip1193(walletId, { rpcUrl }) is a standard EIP-1193 provider: reads go to your node, transactions become contract calls and personal_sign / signTypedData become signature requests — simulated, approved under your policy and co-signed — resolving with the hash or signature. The API accepts contract_call and sign_message operations for keys with the new contracts:write scope, off by default.

    Learn more
  • Security

    MPC 2-of-3 with a backup share

    Create MPC wallets with a third share: your co-signer computes it and seals it at once to your offline recovery key (set in its policy.json, never sent by Chainvara). Signing is unchanged — vault and co-signer — and any two shares rebuild the key: the recovery tool now restores these wallets from a kit alone, or from your co-signer backup alone. ECDSA (EVM, Tron, Bitcoin-family, Cosmos), Ed25519 and Taproot.

    Learn more
  • Wallets

    Cross-chain USDC with Circle CCTP

    Send native USDC from one chain to another — Ethereum, Base, Arbitrum, Polygon, Optimism, Avalanche, Linea, Sonic, Unichain, World Chain and their testnets: burned here with an exact-amount approval, minted there automatically once Circle attests it. Standard transfers are free; fast ones arrive in minutes for a small Circle fee. Your co-signer checks the burn and the mint itself. Also POST /operations with type cctp_burn.

    Learn more
  • Security

    Custom roles

    Build roles for each team in Team: a built-in role narrowed to requesting or approving, some vaults and networks, and USD caps. Every request and approval checks it; giving or removing one follows your admin quorum. Growth plan and above.

    Learn more
  • Security

    Address poisoning protection

    A transfer to a new address that shares the first and last characters of one you know — address book, your wallets, destinations already paid — is refused (or needs an approval, your choice in Policies). It is how attackers get addresses copied from a transaction history. Their bait — an incoming movement from the lookalike — is marked in the wallet's history and carries poisoning on transaction.detected.

    Learn more
  • Security

    Approval watch

    A new automation reads the token approvals of your EVM wallets every few hours and reports each new one (wallet.approval_detected, to webhooks and Slack or Teams). Optionally, a new unlimited approval to an unknown contract gets a revocation request at once, under your policies.

    Learn more
  • Security

    Token approvals: find and revoke

    Every EVM wallet page lists the approvals that can still move its tokens — ERC-20 allowances, NFT operators, Permit2 — read live, with what is at risk now. Revoke one, or every unlimited one at once: each revocation is a contract call under your policy and co-signer. Also GET and POST /v1/wallets/{id}/allowances.

    Learn more
  • Developers

    Test a webhook endpoint

    Send test in Developers delivers a signed webhook.test event to that endpoint only, so you check signature verification and the 2xx answer before a real transfer depends on it.

    Learn more
  • Developers

    Webhook secret rotation without downtime

    Rotate an endpoint's signing secret in Developers: for 24 hours every delivery is signed with both the new and the previous secret, so you switch your server whenever you are ready. The SDKs accept either signature.

    Learn more
  • Developers

    Event feed you can poll without gaps

    Every event now carries a seq: GET /events?after=<seq> returns the ones that came next, oldest first, with next_after for the following call — no event is ever skipped. The type filter now applies before the limit.

    Learn more
  • Developers

    Cursor pagination for transfers

    GET /transfers now returns next_cursor: pass it as starting_after to read every transfer, page after page, with a stable order while new ones arrive. The TypeScript SDK walks them all with for await (const t of cv.transfers.all()).

    Learn more
  • Payments

    Transfer tags

    Tag transfers for your books — payroll, vendor:acme, project names — when you send them (console or API tags) or afterwards on the transfer page. Filter the transfers list or GET /transfers?tag= by tag; tags are in the ledger export. They never change what was approved or signed.

    Learn more
  • Payments

    Exports for Xero and QuickBooks

    Reports export straight to the bank-statement formats Xero and QuickBooks Online import: every movement in USD at the price of its time, inflows positive, outflows negative, with the transaction hash as reference.

    Learn more
  • Payments

    Solana transfers that expire are sent again

    When Solana is congested, a transaction can expire before it is included — and then it can never land. Chainvara now signs the same approved transfer again with a fresh blockhash (three times at most, within a day), without new approvals; your co-signer accepts it only once the previous transaction is certainly dead.

    Learn more
  • Wallets

    Lend Tron energy to your hot wallets

    Stake TRX once in a treasury wallet and lend its energy to your deposit and payout wallets: they send USDT without burning TRX, and you take the energy back any time. The receiver is screened and approved like any destination, and locked delegations are refused.

    Learn more
  • Wallets

    Tron energy: USDT transfers without burning TRX

    Stake TRX for energy (or bandwidth) from any Tron vault wallet and your TRC-20 transfers stop burning TRX for fees. The staking page shows energy available and how many USDT transfers it covers a day; unstake and withdraw after 14 days. Every step is an operation under your policy, and MPC co-signers decode it.

    Learn more
  • Wallets

    Automatic coin consolidation

    A new automation merges a Bitcoin, Litecoin or Dogecoin wallet's small coins at the cheapest moment: once it holds enough coins worth spending and the network's low fee is under your ceiling, one consolidation is requested — at most one a day, under your policies and approvals.

    Learn more
  • Security

    Admin requests in Slack, Teams and webhooks

    Every sensitive change waiting for a second admin — a new API key, pausing the co-signer, unfreezing a vault, opening console access — now also emits governance.requested to your webhooks and team chat, so nobody misses a change they did not expect.

    Learn more
  • Wallets

    Smart-contract console

    Load any EVM contract — the ABI comes from Sourcify, implementation included behind EIP-1967 proxies, or paste your own — query its read functions, and call its write functions from a vault wallet. Each call is a contract_call operation: simulated, valued, approved and co-signed under your policy.

    Learn more
  • Security

    Loosening security takes two people

    Opening the console to more networks, unfreezing a vault after an incident and no longer requiring single sign-on now wait for another owner or admin in Approvals. Tightening — restricting networks, freezing, requiring SSO — still applies at once.

    Learn more
  • Security

    The co-signer can't be switched off alone

    Pausing, removing or replacing an active API co-signer now needs another owner, admin or CFO to approve it in Approvals; until then the current co-signer keeps the last word. Turning it back on is never delayed.

    Learn more
  • Security

    API keys need a second admin

    A new API key now works only once another owner or admin approves it in Approvals, like policy and team changes — a single compromised admin account can no longer mint a working key. Rejecting or canceling the request revokes the key. Teams with a single admin are not blocked.

    Learn more
  • Compliance

    Travel Rule beneficiaries on file

    Record the beneficiary of a trusted destination once — name, person or company, service provider (or self-hosted), reference — in the address book or with POST /addresses. It is sealed with your organization's key, and every transfer to that address carries it automatically once the address is trusted.

    Learn more
  • Developers

    Vaults API and freeze from your SIEM

    List and create vaults, move wallets between them, and freeze a vault with an API key — so your SIEM or SOC can stop every outflow of a vault the second it detects an incident. Unfreezing stays in the console, for owners, admins and CFOs only.

    Learn more
  • Developers

    Policy as code

    GET /policy returns the policy in force with its version; POST /policy/impact replays a candidate policy file on your last 200 requests and lists what it would decide differently. Keep the policy in git, check every change in CI, publish it in the console. In the three SDKs.

    Learn more
  • Developers

    Address book API

    GET /addresses, POST /addresses and POST /addresses/{id}/revoke — in the TypeScript, Python and Go SDKs too. Adding needs the new addresses:write scope, granted on purpose; every addition is screened and waits for your security cooldown like one made in the console.

    Learn more
  • Security

    Address book import

    Bring hundreds of trusted destinations at once from a CSV (network, address, name, note): every line is validated and sanctions-screened before anything is added, with the same security cooldown as a single address.

    Learn more
  • Security

    Approve several transfers at once

    Tick the pending transfers you can decide and approve or reject them together — up to 50. Each is still checked one by one (role, separation of duties, one voice per person, intent, policy version). With a passkey, a single signature covers exactly the selected set: if any of them changes before you confirm, the signature is refused.

    Learn more
  • Developers

    Webhook recovery

    After an outage on your side, retry every failed delivery of an endpoint in one click, or send again every subscribed event since a time (up to 30 days back), delivered or not — each still signed, in order. Queued and failed counts show per endpoint.

    Learn more
  • Security

    Preview a policy before publishing it

    Edit limits, tiers, the address book or Travel Rule settings and press Preview impact: the new policy is replayed on your last 200 requests — 24-hour totals and velocity windows recomputed from the same history — and every request it would have decided differently is listed, stricter or looser, with the reason. Nothing changes until you publish.

    Learn more
  • Wallets

    Coin consolidation for Bitcoin, Litecoin and Dogecoin

    A deposit wallet that collected hundreds of small coins pays for each of them in every later payment. The wallet page now shows how many coins it holds and which ones cost more than they are worth, and merges the smallest into one at the network's low fee — refused if fees would exceed 2% of the merged value. Same policy, approvals and co-signer as any operation; also POST /operations with type utxo_consolidate.

    Learn more
  • Payments

    Realized and unrealized gains

    Reports now compute your gains per asset, by FIFO or weighted average cost (prix moyen pondéré): proceeds, cost basis, realized gain, network fees at cost, holdings with their cost and market value. Moves between your own wallets are excluded, unknown costs stay unknown, and the disposals export to CSV or GET /reports/gains for your accountant.

    Learn more
  • Compliance

    Self-hosted wallet ownership proofs

    Send the owner of a self-hosted wallet a link: they sign a one-time message with their wallet (MetaMask, Phantom, a Safe, Electrum, Sparrow…) and Chainvara verifies it. The policy can then require a proof above a threshold for self-hosted beneficiaries — the EU Transfer of Funds Regulation asks for it above €1,000 — or ask for an approval instead.

    Learn more
  • Security

    Rules by destination type

    Transaction rules now match the kind of destination: the organization's own wallets, connected network organizations, address book entries or one-time addresses — for example, internal moves without approval and two approvals for any one-time address. Only wallets whose key was generated in your vault count as your own: never a watch-only address or an imported key.

    Learn more
  • Payments

    One transaction per Bitcoin payout batch

    Payout batches on Bitcoin, Litecoin and Dogecoin now leave in a single transaction: one fee instead of one per line, and no waiting for change to confirm between lines. Every line keeps its own policy decision, screening and approvals, the fee is shared between lines, and your co-signer checks that each approved line is paid exactly once. Bitcoin-family wallets also sign one transaction at a time, so two transfers never pick the same coins.

    Learn more
  • Payments

    Bitcoin and Litecoin replace-by-fee

    A Bitcoin or Litecoin transfer stuck under a low fee can now be sped up — the same coins spent again, the higher fee taken from the change — or canceled, everything back to the wallet. New transfers signal replace-by-fee, the policy's automatic speed-up covers them, and your co-signer accepts a cancellation only when it spends exactly the coins it already signed.

    Learn more
  • Security

    Approval delegations

    Going on holiday? Hand your approval rights to a colleague until a date. They approve with your voice — never a second one of their own — and cannot approve what either of you requested. Two-factor, audited, revocable.

    Learn more
  • Developers

    external_id and fee estimates

    Tag a transfer with your own reference (external_id, unique and searchable), and read the current network fee for each fee level with GET /networks/{id}/fees.

    Learn more
  • Payments

    Scheduled payments

    Pay the same amount every day, week or month — payroll, rent, suppliers — from any vault wallet. Never twice for the same period, each payment under your policies, approvals and co-signer, with an optional end after N payments.

    Learn more
  • Wallets

    Staking on Cosmos chains

    Delegate ATOM, OSMO, TIA, AKT and DYDX to validators, unstake and claim rewards from the console or POST /operations — under your policies and approvals, with your co-signer decoding every staking message before it signs.

    Learn more
  • Payments

    Hot wallet top-up

    Keep a working wallet stocked automatically: below a threshold, your treasury wallet sends what brings it back to the target — one transfer at a time, under your policies, approvals and co-signer, with an alert when the treasury runs short.

    Learn more
  • Platform

    Slack and Microsoft Teams notifications

    Approvals needed, policy blocks, failures, risky deposits, unexplained movements and alerts posted to your team's channels with a link to act, retried until delivered. Webhook URLs are stored encrypted and only sent to Slack's or Microsoft's hosts.

    Learn more
  • Payments

    Network fee priority

    Choose slow, normal or fast for each transfer (fee_level low, medium or high in the API): EVM tips and fee caps, Bitcoin, Litecoin and Dogecoin fee rates, and Solana priority fees follow your choice.

    Learn more
  • Security

    Console access by network

    Limit the console to your office or VPN addresses: members elsewhere are refused even with a valid password and session. Owners keep a break-glass path; you cannot save a list that would lock yourself out.

    Learn more
  • Compliance

    Proof of reserves

    Commit what you owe each customer in a Merkle sum tree, read your reserves from your wallets at the same moment, and publish the coverage per asset. Customers verify their own inclusion in the browser; their ids are never revealed.

    Learn more
  • Security

    Rules by contract method

    Policy rules can match the EVM method a request calls — approve, setApprovalForAll, permit, transferFrom or any selector — for dApp calls, token transfers and NFT moves.

    Learn more
  • Security

    Approval window

    A request still waiting for approvals after 7 days (or the window you choose) expires, so a late approval never sends money on an old request. Webhook transfer.expired.

    Learn more
  • Security

    Velocity rules

    A rule can apply only once too much has been sent over a window: across the organization, from one wallet, to one address or by one person or API key, by total amount or number of transfers. Unmeasured or unpriced amounts make blocks and approvals apply, never allowances.

    Learn more
  • Developers

    Co-signer callback to your own server

    The co-signer can ask your server before approving: your code sees every transfer and answers approve or reject, both directions HMAC-signed and bound to the request. A down, slow or forged answer approves nothing. Helpers in the TypeScript, Python and Go SDKs.

    Learn more
  • Security

    Recovery kit: your exit plan

    Rebuild every private key yourself, offline, without Chainvara: a kit holding Chainvara's share of each wallet sealed to your own recovery key, your co-signer backup, and an open, dependency-free recovery tool that checks each key against the wallet's public key. MPC (ECDSA, Ed25519, Taproot), split and vault keys.

    Learn more
  • Payments

    Speed up or cancel stuck transactions

    An EVM transaction waiting in the mempool can be re-signed with a higher fee, or canceled by spending its nonce on a 0-value transaction to the wallet. Approvals still apply, your co-signer accepts a cancellation only for a nonce it already signed, and whichever transaction lands decides the outcome.

    Learn more
  • Security

    SAML single sign-on

    Okta, Microsoft Entra ID, Google Workspace or any SAML 2.0 provider, on a domain you prove with a DNS record. Require it for everyone but owners, and let newcomers join with a read-only role.

    Learn more
  • Platform

    Cosmos: Hub, Osmosis, Celestia, Noble, Akash and dYdX

    93 blockchains. Six Cosmos SDK chains with vault, MPC and split-key wallets, exchange memos, and USDC on Noble, Circle's native issuance. Your co-signer decodes each Cosmos transaction itself — recipient, amount, memo, fee and chain — before adding its share.

    Learn more
  • Wallets

    Send NFTs from the vault

    Any ERC-721 or ERC-1155 item a vault wallet holds can be sent from the console or POST /operations. The standard and ownership are read from the chain, checked again before signing, and the co-signer decodes the transfer itself.

    Learn more
  • Security

    Tamper-evident audit trail, streamed to your SIEM

    Every audit entry is numbered without gaps and linked to the hash of the one before. GET /audit feeds Splunk, Datadog, Sentinel or Elastic in order, /audit/verify recomputes the whole chain, and the console shows the chain status and exports it as CSV.

    Learn more
  • Security

    Proactive refresh of MPC key shares

    Renew both shares of any MPC wallet — FROST or threshold ECDSA — with your co-signer, from the console or the API. The address stays the same and a share copied before the refresh becomes useless; the switch happens only once both sides confirmed the same key.

    Learn more
  • Platform

    87 blockchains

    27 more EVM networks — Kaia, Chiliz, Filecoin, Flow, IoTeX, ZetaChain, Ethereum Classic, Astar, Conflux, Etherlink, Oasis Sapphire, Plume, Telos, Viction, Bitlayer, Merlin, B², Hemi, Morph, Zircuit, Lens and more — each chain id, RPC and explorer checked live, with MPC from day one.

    Learn more
  • Wallets

    MPC on every mainnet

    Litecoin and Dogecoin join Bitcoin, Ethereum, Solana, Tron, the XRP Ledger, Stellar, Aptos, Sui, TON and every EVM chain: every production wallet can be a 2-of-2 threshold key shared with your co-signer.

    Learn more
  • Security

    Your co-signer checks every chain's own format

    Before adding its share, the co-signer decodes Bitcoin, Litecoin, Dogecoin, EVM, Solana, Tron, XRP Ledger, Stellar, Aptos, Sui and TON transactions itself and recomputes the hash it signs. On Dogecoin it reads the spent amounts from the previous transactions, so a hidden fee is impossible.

    Learn more
  • Payments

    Payment requests and net settlement

    Ask a connected organization for a payment, record what you owe each other trade by trade, and settle only the net with one transfer once both sides confirmed.

    Learn more
  • Compliance

    Every deposit's sender screened

    Incoming funds are checked against sanctions and your Chainalysis, Elliptic or TRM Labs account; flagged deposits wait for a compliance decision, and your platform is told before it credits anything.

    Learn more
  • Compliance

    Travel Rule exchanged between organizations

    Paying another organization by @handle sends your originator information before signing; the beneficiary acknowledges it and both sides keep the record down to the transaction hash.

    Learn more
  • Compliance

    Blockchain analytics with your own account

    Connect Chainalysis, Elliptic or TRM Labs: destinations are risk-scored before every production transfer, and your policy blocks or requires approval by risk level.

    Learn more
  • Payments

    Fifteen exchanges, and moves between them

    MEXC, HTX, Bitfinex, Gate, Bitget, Gemini, Bitstamp and Crypto.com join Binance, Coinbase, OKX, Bybit, Kraken, Deribit and KuCoin. Funds can move from one of your exchange accounts to another, only to the deposit address that exchange gives you.

    Learn more
  • Wallets

    Embedded wallets: recovery and mobile apps

    A user who loses their phone recovers their wallet with a recovery code only they hold; Chainvara keeps the encrypted backup and cannot open it. React Native, iOS and Android apps run the same SDK through a self-contained bridge.

    Learn more
  • Wallets

    Embedded wallets on every EVM network

    Your users' wallets on Ethereum, Base, Arbitrum and every other EVM chain are shared between their device and the vault with threshold ECDSA.

    Learn more
  • Security

    dApp simulation sees hidden approvals

    The dry run of every dApp transaction now reports each approval or operator right it grants — even inside a router or multicall — ERC-1155 movements, and calls to addresses with no contract.

    Learn more
  • Security

    Time windows and approval groups

    Transaction rules can apply only during or outside chosen hours, and require one approval from each group — Finance and Compliance, for example.

    Learn more
  • Developers

    Go and Python SDKs

    One-file SDKs with no dependencies for Go and Python, next to TypeScript: retries with stable idempotency keys, typed errors, webhook and co-signer signatures.

    Learn more
  • Platform

    Monitoring and public status page

    Every component is probed each minute; incidents open and close automatically and are published with 90 days of uptime.

    Learn more
  • Security

    Platform master key in AWS KMS

    The key that seals every organization's vault material is held by AWS KMS and decrypted only in memory.

  • Wallets

    Outbound co-signer

    The co-signer connects to Chainvara itself: no public address, tunnel or open port on your network.

    Learn more
  • Wallets

    Non-custodial by default

    Every new production wallet keeps a key share with you; a full compromise of Chainvara alone cannot move your funds.

    Learn more
  • Payments

    Deposit addresses for every user in one call

    POST /deposit-addresses returns a user's addresses on every network you need, and deposit.received tells you whom to credit.

    Learn more

October 6, 2026

  • Security

    Passkey approvals and admin quorum

    Approvals can be bound to Face ID, Touch ID or a security key, and sensitive changes need a second admin.

    Learn more
  • Security

    Transaction rules

    Ordered rules by initiator, vault, network, asset, operation, destination and amount, with named approver roles.

    Learn more
  • Wallets

    MPC wallets on Solana and Bitcoin

    The first 2-of-2 threshold wallets: FROST for Solana and Bitcoin Taproot, generated jointly with your co-signer.

    Learn more
  • Payments

    Swaps, staking and tokens

    Best-price swaps with an approved guaranteed minimum, Solana staking and Lido, and your own tokens with mint, burn, freeze and fixed supply.

    Learn more
  • Security

    dApps through WalletConnect

    Connect vault wallets to dApps; every request is decoded and simulated, and message signatures always need an approval.

    Learn more
  • Platform

    58 blockchains

    XRP Ledger, TON, Sui, Aptos, Litecoin, Stellar, Dogecoin and 46 more EVM mainnets, with their stablecoins verified on chain.

    Learn more
  • Compliance

    Travel Rule

    Beneficiary information required above your threshold, sealed with your organization key, with monthly exports.

    Learn more