Dfns Integration for Firms That Run Their Own Ledger
Protofire builds the parts of a Dfns integration that Dfns leaves to banks, payment firms, crypto firms and issuers. Those parts are deposits booked once, approval policies from the firm's authority matrix and a solvency check. We deployed Safe on 120+ EVM networks, where it secures $2B+.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
Dfns tracks balances, and your ledger tracks owners
In a Dfns integration, client entitlements are recorded in your ledger. This is because a Dfns vault tracks balances and not who owns what inside a pooled wallet.
Where a firm runs its own ledger in front of Dfns wallets, a solvency check compares the ledger with the wallets. Dfns' CISO wrote on 26 October 2026 that this check is, for now, "the client's to build" (Dfns). If the check is left unbuilt, a break between the ledger and the wallets appears at reconciliation.
For example, the client ledger can show a deposit twice while the Dfns wallet holds it once. Dfns resends a failed webhook delivery as a new event with its own ID (Dfns). So a consumer that keys on the event ID credits the same money twice.
Who owns each step between a Dfns event and your books
Dfns detects the deposit and confirms it after the network's confirmation delay. Your connector books the deposit once. Your staff and signers keep approvals and signing.
Firm's ledger
Dfns organization
Signers
Connector
Solvency check
Dfns behaviors that cause wrong positions or approvals
Four problems start with documented Dfns behavior, and each one ends in a wrong position or a wrong approval.
Webhook retries arrive as new events
Dfns sends each retry as a new event with a retryOf field, so the event ID cannot be the booking key. The connector that Protofire builds keys a blockchain event on wallet ID, transaction hash and index. The connector keys a vault entry on its entry ID. A vault deposit also emits the underlying wallet events (Dfns). So for a vault's wallets, the vault entry is posted and the wallet events feed reconciliation.
Included events arrive before the confirmation delay
Dfns can first send an Included event for a block that is "not yet finalized". A Confirmed event follows after the network's confirmation delay. On Bitcoin, that delay is 2 blocks (Dfns), but Dfns' monitoring guide lists "6 blocks for high confidence". Dfns sends Confirmed once and documents no event that reverses a deposit after a reorg (Dfns). The connector books a deposit on Confirmed. The connector holds large deposits until its own chain read shows the depth that your risk team set.
Vault quarantine and unscreened deposits
A vault holds incoming transfers in quarantine until a user or service account calls Release Quarantine (Dfns). In a plain wallet, incoming funds can be spent at once (Dfns). The connector books an unscreened or flagged deposit to a held position. Protofire's Chainalysis integration page covers screening itself.
Dfns policy gaps that approve more than you meant
With no policy configured, "all transactions are allowed", and delegated wallets bypass the policy engine entirely (Dfns). Amount and allowlist rules cannot read a mint or burn, so they fail closed and trigger. A user who belongs to two approver groups satisfies both with a single decision. A member added mid-request can cast the deciding vote. Protofire tests these policy gaps before go-live.
Dfns facts we build against
- Regulatory status
- Dfns calls itself "Deliberately unlicensed" and says custody is kept inside the client's perimeter (Dfns).
- Deployment and keys
- Dfns offers MPC in its own cloud, a hybrid with firm-hosted signers, fully self-hosted signers, or keys wrapped by the firm's HSM (Dfns).
- Networks
- Dfns lists 57 active mainnets. Of these, 53 are Tier-1, with indexing and deposit webhooks. The Tier-2 networks report the native balance (Dfns).
- Support
- Dfns support covers weekdays, unless the 24/7/365 add-on is bought (Dfns).
Checked November 2026 against Dfns' documentation.
Dfns key placement decides what your firm can stop
Where the keys are held decides what your firm can stop.Dfns offers four places for them. They are its cloud, a hybrid split, signers that your firm hosts, or your HSM.
Dfns' hybrid page lets you choose the split and recommends a 3-of-5 scheme (Dfns). The page gives an example with two signers at your firm and three at Dfns. The page also says that up to n minus t signers can be offline. So your signers are a veto only if Dfns' signers alone cannot reach the threshold t. Before you sign the contract, ask Dfns to confirm in writing which signers each signing ceremony needs.
Dfns hybrid ceremonies also run through the delivery server that Dfns operates. Your signers are part of the withdrawal path, so an outage at your site stops withdrawals.
The CSA will assess the maturity of CASPs’ digital operational resilience frameworks in relation to custody activities. It will focus on risks inherent to distributed ledger technology (DLT), including governance arrangements, key and storage management, transaction controls, incident detection and response, [...] and dependencies on third-party providers.
Leaving Dfns and the exit plan DORA asks for
A firm leaves Dfns by moving assets onchain to new wallets.The exit plan should exist before the contract is signed. Under DORA, your firm lists Dfns in its register of information. Where Dfns serves a critical or important function, DORA asks for exit plans that are "comprehensive, documented" and "sufficiently tested" (DORA, Article 28).
Under Dfns' standard terms, user data and histories are available "free of charge" for 30 days after termination (Dfns). After those 30 days, Dfns deletes them. An Enterprise contract can differ. The histories and the audit log must be exported before the 30 days end.
Dfns key export "is not enabled by default". Export rebuilds the full private key on one machine, which Dfns calls "a single point of failure". After export, the wallet keeps signing in Dfns (Dfns). So an exit moves funds onchain to wallets generated at the next provider, and an exported key is kept as a sealed backup.
Protofire belongs in your register as an ICT provider. Your risk and legal teams decide what is filed. Protofire's DORA third-party risk guide covers the provider classes.
What a Dfns integration changes on your side
Deposits booked once in the ledger you already run
Protofire builds the connector and the posting rules. A retry under a new event ID posts nothing, whether the ledger is Temenos, Mambu, an in-house core or a client ledger. A withdrawal blocks the client position when the withdrawal is accepted. The final debit posts at the depth that your risk team set.
Dfns approval policies from your authority matrix
Protofire maps your authority matrix to Dfns policies that an auditor can read. User groups are fed from your identity provider. Approval steps cover changes to group membership and policy edits, which Dfns has offered since October 2026 (Dfns changelog). Protofire ships tests for a user in two approver groups and for a member added mid-request.
A solvency check per asset and chain
Per asset and chain, Protofire matches client entitlements against Dfns wallet history and vault entries, and against a chain read independent of Dfns' indexer. You get an alert when entitlements exceed holdings. You also get a daily break list with an owner for each line.
Signers placed where your risk team wants them
For hybrid, self-hosted or HSM deployments, Protofire deploys the signers with your infrastructure team. We also write the recovery runbook. Your key custodians run a drill on an offline machine, and we file each run as audit evidence.
Alerts and Dfns release checks
Failed webhook deliveries, pending approvals and stuck transfers reach a named person. So do a service-account token near expiry and a low fee sponsor. Dfns' weekly releases included breaking API changes in four separate weeks between 24 August and 2 November 2026 (Dfns changelog). So Protofire checks each release against the connector. Protofire's managed onchain operations service can watch these alerts once you are live.
Our record: Safe multisig and a blueprint that lists Dfns
Dfns policies ask who must agree before funds move.Protofire's multisig work deals with the same question.
Safe deployments on 120+ EVM networks
Protofire deployed Safe on 120+ EVM networks, where it secures $2B+. The Safe Ecosystem Foundation wrote in May 2026 that Protofire "has been contributing to Safe since 2018". Read more on our Safe multisig work page.
Our Euro Stablecoin Issuance blueprint lists Dfns
Protofire's Euro Stablecoin Issuance blueprint names the vendors an issuer rents, and it lists Dfns in its Proven stack. Our integrations hub lists each custody platform that we connect, including Fireblocks.
Steps of a Dfns project with Protofire
- Step 1
An engineer reads your Dfns setup before the call
Before the call, a Protofire engineer reads your Dfns organization and deployment model. The engineer also reads your authority matrix and target ledger. A written proposal follows. - Step 2
Booking and the solvency check come first
The connector and the daily match are built before the policies change. They come first because a Dfns retry can post the same money twice. - Step 3
Policies, signers and alerts for each product launch
Each product comes with its own policy set, signer placement and alerts. They are tested before the product goes live. - Step 4
What your firm owns after launch
The code, configuration and runbooks are yours. Your staff hold the approver seats and the connector's service-account key. Your team runs the integration, or Protofire operates it under a written scope.
How work with Protofire starts
Send a description of your Dfns setup, from the deployment model and wallet types to the target ledger.Protofire's written proposal maps the connector keys, the policy gaps and the exit. The terms for each phase are set out on how we work.
- Proposal
- In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
- Price
- Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
- Ownership
- Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
- After launch
- Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
- Access
- Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
- Licenses
- Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.
How we work shows a worked proposal.
When a Dfns setup needs little outside engineering
Four Dfns setups need little outside engineering.
- Your firm approves in the Dfns dashboard and books from CSV exports at low volume.
- A core banking vendor or Dfns already offers the link. Ask Temenos, Mambu and Dfns first.
- You need the signers or the HSM Driver installed and nothing more. Your infrastructure team can follow Dfns' deployment guides.
- End users hold sole signing authority, and counsel agrees that their assets are kept off your books. The remaining work is the app, recovery and fee booking.
Protofire holds no license, and Dfns describes itself as unlicensed. So your firm holds the license and safeguards client assets. Protofire gives no legal opinion on whether your wallet model counts as custody. Dfns is responsible for fixing a Dfns outage, and your runbook names who acts.
FAQ
What is a Dfns integration?
Who can build a Dfns integration for a bank or a payment firm?
Will Protofire hold keys or approve Dfns transactions?
Should a regulated firm use Dfns wallets, vaults or delegated wallets?
Does a Dfns integration differ for a bank, an e-money firm, a crypto firm or an issuer?
Can a firm move from Dfns cloud MPC to hybrid or an HSM later?
Get a proposal
Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.
