Secure institutional-grade crypto wallet and transfer infrastructure.
Vault accounts mirrored as wallets
Bitwave reads your Fireblocks vault accounts and represents them as wallets grouped under a Fireblocks parent in Bitwave, with a filter available to skip vaults you do not want created.
Transactions with their operation types
Fireblocks transaction history comes into Bitwave with its operation types, including transfers, contract calls, and staking operations, so your team can categorize custody activity with that context.
Balances and deposit addresses for reconciliation
Bitwave reads vault balances and deposit addresses from Fireblocks, supporting balance validation against the subledger and identification of transfers between your own vaults and wallets.
How it works
Bitwave connects to Fireblocks with a read-only access credential generated in the Fireblocks console. Fireblocks lets you scope it to read-only access, and Bitwave recommends that plus restricting it to Bitwave's addresses. Bitwave stores credentials encrypted and cannot sign or initiate Fireblocks transactions.
After the credential is added, Bitwave validates it, sets up a wallet record for each of your vault accounts, and brings transactions and balances into the subledger.
The workflow:
- Create a read-only access credential in Fireblocks, restrict it to Bitwave's addresses, and add it in Bitwave.
- Bitwave validates the credential and sets up a wallet record for each vault account.
- Bitwave brings in vault transactions and balances for categorization, one by one or with rules.
- Reconcile the period and push the results to your general ledger connection or journal entry reports.
.avif)
Fireblocks vaults are where many institutions hold and move digital assets, so the accounting record has to follow the vault structure closely. Bitwave mirrors vault accounts as wallets and imports their transactions with operation types, keeping custody activity organized the way your operations team thinks about it.
For the finance team, the result is custody transactions categorized in the same subledger as exchange and on-chain activity, balances and deposit addresses available to validate and identify internal transfers, and a read-only connection that satisfies security review without giving up control of signing.
Complete. Transparent. Secure.
ERPs
Sync data in real-time and eliminate manual errors. Bitwave seamlessly integrates with your existing back-office software for easier reporting.
.avif)
.webp)
.webp)
.webp)
Blockchains
Bitwave supports tokens on the Bitcoin, Ethereum (All ERC-20 tokens + Layer 2), Solana, NEAR, and more. We are constantly adding support for new Blockchains.
.webp)
Custodial Wallets
Bitwave currently supports Fireblocks, NYDIG, BitGo, and Anchorage custodial wallets. We are constantly adding support for new Custodial Wallets.
.webp)
.webp){kind=logo}
.webp)
DeFi Protocols
This is just a sample of the DeFi protocols we support. Click below for the full offering of DeFi integrations currently in place, with more being added each day.
.webp)
Exchanges
This is just a sample of the key Exchanges we support. Click below for the larger offering of Exchanges supported, with more being constantly added.
_logo%201.webp)
Multi-Signature Wallets
Bitwave supports a variety of multi-signature wallets, such as Gnosis Safe, Zebec, and Electrum. We are constantly adding support for new Multi-Signature Wallets.
