Fordefi Integration for Policy Rules on Contract Calls
Protofire builds the firm's side of a Fordefi integration. That side covers the API Signer in your cloud and rules for contract calls. It also includes an approver service and booking each balance effect once. We maintain Solhint, the Solidity linter, with Ethereum Foundation funding in three allocations.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
Fordefi rules check simulated amounts on contract calls
A contract call has no amount of its own, so Fordefi derives one from simulation. Your authority matrix has to be written for that figure. For example, Fordefi's own documentation warns that a rule like "net amount ≤ $1,000" matches a $1,000,000 Aave borrow (Fordefi).
A Fordefi integration is the firm's side of Fordefi's MPC wallets. It covers the API Signer in your cloud and the rules drawn from your authority matrix. It also covers an approver service and booking. Fordefi splits each key between its own secure enclave and the customer (Fordefi). Fordefi also simulates each transaction it creates by default (Fordefi). Protofire builds the four parts, which run in your own cloud accounts and Fordefi organization.
Fordefi's factory settings require no approvals
Fordefi's factory settings "require no approvals at all" (Fordefi).Fordefi recommends a default rule set to block or require approval. Rules are ordered, and the first match decides.
Contract calls test Fordefi's rule order hardest. The recipient of a contract call is the contract being called. Its amount comes from simulation as two figures, an outgoing amount and a net amount. Periodic limits count the net figure too, so deposits and borrows barely move a daily cap. So an authority matrix copied over from transfers lets large positions through.
Three more parts are left to your firm: the API Signer host, the key backup and the ledger. If the policy is left as it is, a desk learns what its rules do from its first live borrow.
Transfers and contract calls in a Fordefi rule
A Fordefi rule reads a contract call through its simulation.So the recipient, amount and asset conditions work differently from those on a transfer.
Recipient
Transfer: The address that receives the funds
Contract call: "The contract or program being called". All recipients must be covered (Fordefi).
Amount
Transfer: The amount sent
Contract call: Derived from simulation. Outgoing counts assets sent and liabilities received. Net is out minus in.
Fordefi's $500 USDC example
Transfer: Sent to an address: $500 on the amount conditions
Contract call: Deposited into Aave: outgoing $500, net about $0, since the receipt token offsets the deposit
Asset condition
Transfer: The token sent
Contract call: Tokens the vault sends. A borrow sends none and matches no rule that names assets.
Periodic limit
Transfer: Net amount, on fixed UTC periods: hourly, daily, weekly from Monday
Contract call: Net amount too, so deposits and borrows add almost nothing. "Monthly" means 30 days.
ABI condition
Transfer: Not available on transfers
Contract call: A 4-byte selector, or parameter values by position, including tuples, arrays and inner bytes4 selectors
The custody policy referred to in the first subparagraph shall minimise the risk of a loss of clients’ crypto-assets or the rights related to those crypto-assets or the means of access to the crypto-assets due to fraud, cyber threats or negligence.
What happens to a contract call when simulation fails
When Fordefi cannot work out a contract call's amount, a "≤" amount rule does not match.The call then moves down the list toward the default rule. Fordefi cannot work out the amount when the chain has no simulation on Fordefi's list (Fordefi). The same happens when the simulation fails, or when the vault sends a token with no price (Fordefi).
Two flags in Fordefi's API change how a contract call is matched. With skip_prediction=True, Fordefi matches the policy only partly and "skips every external provider screening". As a result, no rule on a screening result can match. With fail_on_prediction_failure=false, a call whose simulation errors "reverts to the default policy rule" (Fordefi). For that reason, the default rule is written first. It either blocks the call or requires approval from the approvers that your authority matrix names.
Fordefi platform facts
- Owner
- Paxos, which announced on 25 November 2025 that it "has acquired Fordefi" (Paxos).
- Key model
- MPC. Each key is split between Fordefi's share on AWS and the customer's mobile app or server (docs).
- Policy engine
- Rules are ordered, and the first match wins. The actions are Allow, Block or Require approval (docs).
- API Signer
- Runs on Docker or Helm in the customer's environment. Its only egress is to api.fordefi.com. Each organization has one Signer (docs).
- Networks
- 80+ mainnets, with footnotes for chains without simulation (docs).
- Custody vaults
- Paxos custody accounts at Paxos Trust Company, N.A., connected with Admin Quorum approval. Paxos custody is the sole custody connection supported (docs).
Checked November 2026 against Fordefi's developer and user documentation and Paxos's newsroom. Protofire integrates Fordefi for firms that have chosen it.
What Protofire builds in a Fordefi integration
The API Signer on a host your team owns
Your infrastructure team owns the machine that holds your share of each key, and Protofire writes the runbooks for that machine. We build the API Signer deployment as a Docker container or a Helm chart. An organization gets one Signer, so we map which API users share it.
Ordered rules from your authority matrix
Your limits by desk, protocol and contract method become ordered rules that an auditor can follow line by line. The rules name contract recipients, ABI selectors and parameter values. They also set outgoing caps on deposits and borrows. Protofire delivers a test pack of deposits, borrows, swaps and unlimited allowances, with the rule that each one matched.
An approver service for checks the rules cannot express
A webhook service in your infrastructure approves or aborts calls that need a check the rules cannot express. That is the case where the authority matrix needs a bridge destination, an EIP-712 field or an internal limit system. The service runs under its own Trader API user, which your Admin Quorum approves. That API user creates no transactions, so no service approves a call it started. Fordefi documents this pattern as one that "does not cryptographically sign" (Fordefi).
Each balance effect posted once in your ledger
Protofire builds the event consumer and the posting rules, so each balance effect posts once in your ledger. For example, one call that moved two tokens and paid gas posts three lines, once. A reverted call posts its fee only.
A daily reconciliation at your cut-off
Finance sees each Fordefi effect matched to a posting at your cut-off, without rebuilding balances by hand. For Paxos custody vaults, Paxos records are the second source, because deposits made outside Fordefi do not appear in the vault's history (Fordefi).
Our record: Solhint, the Solidity linter we maintain
Protofire works with Solidity code, which defines the functions and parameters that an ABI condition names.
Solhint, our open-source Solidity linter
Protofire maintains Solhint, its open-source Solidity linter, downloaded 25M+ times from npm. Our Solhint page describes the linter.
Ethereum Foundation funding in three allocations
The Ethereum Foundation's Ecosystem Support Program funded Protofire's work on Solhint in Q4 2022, Q4 2023 and Q1 2025. The last allocation was for ongoing maintenance and support (Ethereum Foundation).
How work with Protofire starts
You send your authority matrix, your current Fordefi policy and a sample transaction log.Protofire's first proposal then sets out the Signer, the rule set and the booking service. The services that create, approve, abort or release transactions run in your infrastructure. Each of those services runs as an API user that your Admin Quorum approves. Your staff hold the services' access tokens and P-256 request-signing keys, and the services act on rules that your staff sign. The services that read Fordefi data are the event consumer, the postings and the daily reconciliation. Those three can run under a written scope through Protofire's managed onchain operations.
- 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.
Where Fordefi's own tools or Integral are enough
Protofire fits when your contract calls reach lending markets, DEXs or bridges.In three other cases, Fordefi's console, Integral or Fordefi's API Approver example is enough.
- Your desk creates and approves calls in the web console and the browser extension, and nothing posts to a ledger. Fordefi calls its policy engine "completely self-serve" (Fordefi).
- You need only reporting. Integral reads a Fordefi wallet by its public address and "will automatically begin aggregating your transaction data" (Fordefi blog).
- One approver check is all you need. Your engineers can adapt the modified server in Fordefi's api-examples repository. Fordefi's API Approver page uses that server for custom validation rules (Fordefi).
Protofire holds no license. Your counsel judges whether your Fordefi rules and custody policy meet MiCA's custody policy rule (Article 75).
FAQ
What is a Fordefi integration?
Who can build a Fordefi integration for a fund, a bank or a payment firm?
Can a Fordefi rule cap how much a desk deposits into a lending protocol?
What happens if our service times out while creating a Fordefi transaction?
Do deposits into a Paxos custody vault show up in Fordefi?
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.
