Skip to content

Blockaid Integration for Firms That Add Cosigner to Safe or MPC Signing

Blockaid returns scan verdicts, co-signs through Cosigner and runs monitors. Your firm decides what each verdict does, who holds the override signer and which permission a response uses. Protofire builds that side of your Blockaid integration. Protofire engineers helped build the Gnosis Safe web app from 2019 to 2021.

Luis Medeiros

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026

On this page
  1. Overview
  2. What you get
  3. Cosigner
  4. Verdict handling
  5. Response routes
  6. Platform facts
  7. Why Protofire
  8. How the work goes
  9. How work starts
  10. Not the right fit
  11. Related guides and services
  12. FAQ

Work shipped for 60+ networks and 95+ protocols, including

  • Chainlink
  • Ethereum
  • Solana
  • Safe
  • Ripple
  • Aave

A Blockaid verdict needs a rule in your own system

A Blockaid integration decides what your systems do with each Blockaid answer. In Blockaid's public Node client, a scan of an EVM transaction or address returns a verdict of Benign, Warning, Malicious or Error. Its Cosigner joins your Safe or MPC signing as an extra signer and withholds its signature when a check fails. In its Co-Signer exhibit, Blockaid's SaaS agreement template says the customer "retains full control and sole responsibility for final authorization and execution of all transactions". Protofire builds the services and Safe changes that turn each answer into an action in your flows.

For example, Cosigner withholds its signature on a transfer from your treasury Safe. Blockaid writes that "Approval can only continue if an authorized override signer manually intervenes" (Blockaid). If Cosigner is mandatory in your signing policy and the person who holds the override signer is on leave, the transfer waits. If nobody agreed in advance when the override may be used, your team decides under pressure.

A transfer can go out on an unverified result. If your code checks for Malicious and nothing else, a transfer that Blockaid could not validate goes ahead as if it were clean. A Warning and a scan that times out need rules too, and your risk lead approves them before the first live transfer.

Who owns each part of a Blockaid setup

Your team decides what each Blockaid answer does, and Protofire builds the services and Safe changes that apply those decisions.

Your team

Safe owners or MPC policy

Your owners and threshold, or your Fireblocks, Fordefi or Utila policy, approve each transaction.

Override signer and policy approval

A named person holds the override signer, and your risk lead approves the policies and the verdict table.

On-call and case tools

Your staff own each alert and each held transaction.
Blockaid

Scan API

Blockaid scans transactions, addresses and tokens and returns a verdict.

Cosigner

Blockaid's signer simulates each transaction and withholds its signature when a policy or the malicious rule fails.

Onchain Monitoring

Monitors fire on onchain conditions and send an alert, call a contract or propose a transaction.
Protofire builds

Verdict handling service

Scan calls in your withdrawal, deposit or signing path act on each verdict, Error and timeout.

Cosigner rollout and policy tests

Protofire prepares the owner or policy change for your team to sign and tests the policies.

Response routes and alert receiver

Role grants or proposal payloads back each monitor response, and a webhook receiver opens a case.

What your firm gets from a Blockaid integration

An action for each verdict, Error and timeout included

Your withdrawal, deposit or signing path proceeds, holds or blocks according to a verdict table that your risk lead approved. Protofire builds the service that calls Blockaid's scan API and applies that table.

Cosigner in your signing flow, with a named override signer

Cosigner signs after Blockaid's checks pass. A person you named in advance decides whether a held transaction continues. Protofire prepares the Safe owner change, or the MPC policy change, for your team to sign.

A Cosigner policy set tested before it enforces

Your risk lead sees each policy checked against real transactions before your team saves the set. Protofire writes the test cases and runs them in Blockaid's Test Policies.

Monitor responses through permissions your firm granted

A Blockaid monitor that pauses a contract acts through a role that your admin granted. A proposal to your custody platform goes through your Fireblocks or Fordefi approval policy. Protofire prepares the role grants and the proposal payloads.

Alerts with an owner, and a record of each decision

Each Blockaid alert reaches a named person in your on-call or case tool. Protofire builds the webhook receiver and a decision log that stores each request ID, verdict and action.

Cosigner joins your multisig as a signer with its own wallet

Blockaid writes that Cosigner is "implemented as its own Safe-compatible wallet with a 1-of-2 threshold configuration" (Blockaid).Blockaid manages one signer of that wallet. Your organization manages the other one, the override signer.

Your firm chooses whether the Cosigner signature is "optional or mandatory in your signing policy". When Cosigner signs, approval "still requires quorum from the rest of the designated signers". On a Safe, your owners sign the transaction that adds Cosigner's wallet as an owner and sets the threshold.

Cosigner evaluates its policies in order. Each cosigner "ships with a built-in, non-overridable Reject policy" that blocks what Blockaid's detection engine flags as malicious (Blockaid). Blockaid pins that policy "to the top of the policy list". Your own policies follow and are "evaluated in order until one matches", so their order changes the result. Test Policies checks a real transaction hash or simulated parameters against the set "without sending anything onchain". Recommended Policies, a beta, drafts rules that "can only make a cosigner more restrictive". Blockaid adds that "Nothing enforces until you save".

Multi-sigs managing high value wallets and contracts should have at least 1 additional required signer that is external to the organization (such as a security partner or trusted advisor)
Security Alliance (SEAL), Security Frameworks, Multisig for Protocols, Publisher of open security frameworks for onchain teams · Multisig for Protocols, use-case specific requirements, Security Frameworks v0.0.3, read November 2026

What your service does with Warning, Error and a timeout

Blockaid's scan API returns a verdict, and your service turns that verdict into an action.For an EVM transaction scan, Blockaid's Node client defines the result as Benign, Warning or Malicious when validation succeeds, and Error when it fails (GitHub). Portal's Blockaid connector docs say, for a Tron scan, that an Error result "is unverified and shouldn't be treated as safe" (Portal). Your risk lead decides what Warning does in each flow.

A scan can also time out. By default, requests from Blockaid's Node client "time out after 1 minute" (GitHub). Connection errors and 408, 409, 429 and 5xx responses are "retried 2 times by default". While no verdict exists, your rule decides whether the withdrawal holds, is blocked or goes ahead with a flag. The service that Protofire builds applies that rule and logs the case.

Each scan response includes an x-request-id header. Blockaid accepts a report of a misclassification "using a request ID from a previous scan", marked as a false positive or a false negative (GitHub). A second call reports "whether the end-user accepted the Blockaid classification".

Blockaid's API can also change your organization's risk settings. Its Node client documents the call: "Pass a category name or verdict level with a new value to override the platform default" (GitHub). Your firm decides who may make that call, because the change applies across your organization.

A monitor response acts through your contract role or your custody policy

Blockaid's Call Contract action calls a function on your contract or, since May 2026, proposes a pre-defined transaction to Fireblocks or Fordefi (Blockaid).Each route needs a permission that your firm sets up first.

What happens when a monitor fires

Call Contract to your contract: Blockaid calls the function you defined, such as a pause, from a response wallet configured in Blockaid.

Proposal to Fireblocks or Fordefi: Blockaid proposes a transaction that you uploaded in advance as a JSON-RPC payload.

What must exist first

Call Contract to your contract: A role on your contract that your admin grants to the response wallet.

Proposal to Fireblocks or Fordefi: A Cosigner configured for your Fireblocks or Fordefi workspace.

What approves the action

Call Contract to your contract: Your contract accepts the call from the granted role, and your admin revokes that role.

Proposal to Fireblocks or Fordefi: Fireblocks' standard TAP approval flow, or the Fordefi Transaction Policy that a proposal from the Blockaid-integrated API user follows.

Who holds the sending wallet's key

Call Contract to your contract: Your firm confirms this with Blockaid and writes it into its own runbook.

Proposal to Fireblocks or Fordefi: Your Fireblocks or Fordefi workspace signs under the policy your admins set.

Blockaid facts that shape the integration work

Contracting party
Blockaid Inc., of Wilmington, Delaware, under New York law, in Blockaid's published SaaS agreement template of May 2025.
API access
REST calls go to api.blockaid.io with an X-API-Key header, or to client.blockaid.io with a client ID header. Blockaid publishes Node and Go clients on GitHub.
Chain coverage
Blockaid's platform overview says its data pipelines process signal across 50+ chains. The Node client also has scan endpoints for Solana, Bitcoin, Stellar, Starknet, Sui and Hedera.
Monitor responses
An alert by email, Slack or Telegram, a webhook notification, an API call to an external service, or Call Contract, per Blockaid's blog.
Token scan webhooks
Subscriptions per chain, with an optional 32-character shared secret "used to calculate the HMAC signature", per Blockaid's Node client.

Checked November 2026 against Blockaid's public SDK repositories, blog posts, product pages and published SaaS agreement template.

What Protofire brings to Safe signing flows

From late 2019 to mid-2021, Protofire engineers worked with the Gnosis Safe team on the Safe web app.In that period they wrote about 950 commits and about half of its merged pull requests, including the Safe Apps tab and the desktop app.

Cosigner joins a Safe as one more owner, so its rollout is work on a Safe's owners, threshold and signing flow.

How Protofire builds the Blockaid side of your flows

  1. Step 1

    A verdict table for each flow

    Protofire reads the flows that will call Blockaid, such as withdrawals, deposits, signing requests or token listings. We draft a verdict table with an action for each verdict, Error and timeout in each flow. Your risk lead approves the table before code calls the API.
  2. Step 2

    Cosigner change and policy tests

    Protofire prepares the Safe transaction that adds Cosigner's wallet as an owner, or the change to your MPC policy. Your owners sign that change after your risk lead has read the policy test results.
  3. Step 3

    Response routes and alert receiver tests

    Protofire prepares the role grant for each Call Contract response, or the JSON-RPC payload for a proposal to Fireblocks or Fordefi. Your Safe or admin signs each grant. We test the webhook receiver with your on-call and case tools before your team enables the monitors.
  4. Step 4

    Code, policies and runbook handed over

    Your team receives the service code, the verdict table and the tested policy set. The runbook names the override signer and each response permission. After launch, Protofire holds no signer, override signer, pauser or admin role, and no admin seat in your Blockaid account.

How work on your Blockaid setup starts

Blockaid API calls use your firm's Blockaid API key, which your staff keep in your vault.A written scope under which Protofire operates a service lists each write call that the service makes to Blockaid. Such calls include a risk-threshold change, a webhook subscription and a misclassification report.

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.

Requests that Blockaid, Safe or another service covers

Four kinds of request need a different answer.

  • You want monitors set up inside Blockaid. Blockaid offers onboarding "with our team mapping your environment and configuring monitors with you" (Blockaid).
  • You want Blockaid's warnings in Safe{Wallet} and nothing else. Safe's help center says Safe Shield shows "Security signals from trusted providers (e.g., Blockaid, Tenderly, Hypernative)" (Safe).
  • An exploit is under way. Protofire offers incident engineering as Protocol Rescue.
  • You want engineers who answer Blockaid alerts after launch. Protofire's managed onchain operations service handles alert duty of that kind.

FAQ

What is a Blockaid integration?
A Blockaid integration puts Blockaid's scan verdicts, Cosigner and monitors to work inside a firm's own flows. Each verdict gets an action in the withdrawal, deposit or signing path. Cosigner joins the firm's Safe or MPC signing, and alerts reach a named owner. Protofire builds these parts, and the firm's own signers decide what is signed.
Who can build a Blockaid integration for an exchange, wallet or fintech?
Protofire builds the firm's side of a Blockaid integration. Protofire writes the scan calls and verdict rules in withdrawal, deposit or signing paths, and prepares the Cosigner change to a Safe or MPC policy. Protofire also prepares the role grants or proposal payloads behind monitor responses, and builds the alert receiver.
Does Cosigner work with Fireblocks, Fordefi or Utila as well as Safe?
Yes. Blockaid's Cosigner page lists Safe, Fireblocks, Squads and Utila. For Fordefi, Blockaid writes that Cosigner "only acts to reject Fordefi MPC transactions deemed malicious" (Blockaid). Fordefi remains "the system of record for keys, policies, and approvals".
Who is responsible if Blockaid misses a threat?
Blockaid's published SaaS agreement template does not warrant that the service will detect any and all threats. Its Co-Signer exhibit calls a validation or signature "Decision Support Output", "intended solely as an informational tool". The exhibit leaves final authorization of each transaction to the customer. Your counsel reads the agreement that your firm actually signs.
How does Blockaid's Cosigner differ from Hypernative's guard on a Safe?
On a Safe, Blockaid's Cosigner is an extra owner: a separate 1-of-2 wallet that withholds its signature when a check fails. Hypernative's Transaction Guard is a guard contract. It needs a keeper approval and reverts a transaction without one. The Safe's owners remove it after a timelock.

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.

Luis MedeirosField CTO, reads every request · LinkedIn

A demo or repository link also works.