Fireblocks — MPC custody, accounting that respects the vault tree
Fireblocks's vault hierarchy and transaction policy define how a finance team operates. We preserve them in the audit trail rather than flattening to a wallet list.
Fireblocks is the leading MPC custody platform for institutional crypto. Vaults, sub-accounts, transaction policy rules, and the segregation-of-duties model are foundational to how Fireblocks customers operate. A naive accounting integration treats every Fireblocks-managed wallet as an isolated EOA — losing the vault hierarchy and the policy attribution. Wag3s preserves both. The vault tree is mirrored in the workspace; transaction policy approvals are part of the audit trail; per-asset and per-vault reporting works out of the box.
What the Fireblocks integration does
Vault tree mirroring
Fireblocks vault hierarchy preserved in the Wag3s workspace.
Transaction policy attribution
Approver list captured in the audit trail per transaction.
On-chain reconciliation
Fireblocks-reported balances reconciled against independently computed on-chain balances.
Multi-chain support
Every chain Fireblocks supports — ETH, BTC, SOL, AVAX, MATIC, plus the long tail.
The connection in 5 steps
Create a read-only Fireblocks API key with JWT authentication
In the Fireblocks console, generate an API key and a corresponding RSA key pair. Wag3s uses JWT-signed requests — paste your API key and upload the private key file. Add the Wag3s IP range to the allowed-IP list in your Fireblocks workspace settings.
Wag3s mirrors the vault tree
We enumerate every vault account and sub-account in your Fireblocks workspace. The hierarchy is preserved exactly in Wag3s — each vault maps to a Wag3s wallet entity with its parent relationship intact.
Transaction policy attribution ingested
For every executed transaction, Wag3s captures the approver list from the Fireblocks transaction policy log. Signers and policy rules are attached to the audit-trail record, not just the transaction hash.
On-chain reconciliation and ERP export
Fireblocks-reported balances are reconciled against independently computed on-chain truth. Reconciled, policy-attributed activity posts to your ERP on the daily schedule.
Staking and DeFi activity decoded
Fireblocks staking rewards and DeFi interactions (via Fireblocks DeFi tab) are classified with the correct accounting treatment and posted as a separate JE category.
Common configurations
Asset manager uses Fireblocks with 40 vaults organized by fund and asset class. Month-end requires per-vault P&L attribution and a reconciled balance sheet. Wag3s mirrors the vault tree, attributes P&L per vault, and produces the consolidated reconciliation without flattening the hierarchy.
Protocol treasury uses Fireblocks for MPC-secured key management across ETH, SOL, and AVAX vaults. The finance team needs policy-attributed spending reports for the DAO governance forum. Wag3s produces a spend report showing which transactions were approved, by which policy rule, for each reporting period.
Fireblocks integration questions
Does Wag3s have signing rights on my vaults?
No. Read-only API key with the minimum scopes — vault list, transaction history, balance read.
How is the vault hierarchy preserved?
Each Fireblocks vault becomes a Wag3s wallet entity, with the parent / child relationship preserved. Transfers between vaults are tagged as intra-organization.
How are Fireblocks staking rewards (via Fireblocks Staking) classified in accounting?
Staking rewards distributed through Fireblocks Staking (ETH, SOL, AVAX, etc.) are classified as ordinary income on the date the reward is credited to the vault, valued at the asset's spot price at that time. Wag3s identifies Fireblocks staking reward events by their originating vault type and books them as a distinct income category separate from trading gains, so per-asset staking income appears on its own line in your P&L.
Other connectors that pair with this one.
Connect Fireblocks in minutes
Free during Alpha. No credit card. Native sync, audit trail, no spreadsheets.