Fordefi

• Name: Fordefi
• URL: https://fordefi.com/
• Category: institutional wallet-and-policy company / DeFi transaction-review operator / MPC signer workflow platform
• Summary: Fordefi belongs as an entity note, not a protocol note. The useful question is who operates the transaction-review, simulation, approval-policy, and browser-to-DApp access shell that institutions actually depend on when they use Fordefi for DeFi. The practical leverage is not the generic MPC wallet claim; it is that a named company can shape how smart-contract interactions get rendered, which warnings and simulations appear before approval, how admin quorum and policy rules are enforced, and how much signing workflow remains inside Fordefi-managed interfaces and gateways.
• What it does:
  • Provides an institutional MPC wallet stack in which key shares are split between Fordefi and the customer, with customer-side shares stored on mobile devices or customer-controlled servers
  • Operates a browser extension and Web3 gateway for connecting to thousands of DApps across supported chains while surfacing contract metadata, transaction simulation, and warnings before approval
  • Exposes a policy engine for transaction approvals, address-book controls, admin quorum, and related operational guardrails tailored to DeFi workflows
  • Packages digital-asset operations through a web console, mobile approvals, API access, vault management, exchange connectivity, swaps, staking, allowances management, and audit / compliance settings
  • Offers developer-facing tooling including REST APIs, webhooks, API signer flows, and a WaaS SDK for embedded non-custodial MPC wallet use cases
• Key claims:
  • Fordefi describes itself as an institutional MPC wallet and security platform purpose-built for DeFi rather than a generic custody dashboard
  • Product docs claim the platform eliminates single points of failure by combining secret sharing, MPC signing, and hardware enclaves across Fordefi and customer environments
  • Security docs emphasize transaction enrichment, contract verification, simulation, and risk alerts so approvers can meaningfully review complex smart-contract interactions
  • The policy and admin model claims to reduce both rogue-user and rogue-admin risk through granular rules plus quorum requirements for sensitive changes
  • Fordefi publicly claims SOC 2 Type II certification and multiple security assessments, though those assurances should still be treated as vendor claims unless independently verified
  • The official product surfaces make clear that the sticky dependency is not only key custody but also Fordefi’s review UI, gateway path, policy engine, and transaction-meaning layer for DeFi operations
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were Fordefi’s official docs around products and services, security, interfaces, and core concepts; see ../whitepapers/fordefi-primary-sources-2026-04-22.md.
• Sources:
  • https://fordefi.com/
  • https://docs.fordefi.com/
  • https://docs.fordefi.com/user-guide/welcome/products-and-services
  • https://docs.fordefi.com/user-guide/welcome/product-security
  • https://docs.fordefi.com/user-guide/welcome/product-interfaces
  • https://docs.fordefi.com/user-guide/welcome/main-concepts

Internal linkages

• Project-layer alias: fordefi.
• Best adjacent operator-stack reads: fireblocks, bitgo, and dfns.
• Reusable lens: when a wallet stack sells institutional DeFi access, the real leverage can sit in simulation, policy, transaction rendering, and gateway placement rather than in the MPC primitive alone.

Protocol / company boundary

• There is not a very useful standalone Fordefi protocol boundary doing the analytical work.
• The important surface is the company-run signing and review shell around institutional DeFi activity: browser extension, transaction interpretation, simulation and warning pipeline, policy engine, admin quorum model, API signer path, and embedded-wallet packaging.
• That is why Fordefi belongs in companies/: the practical questions are who defines the approval ceremony, who mediates DApp access, who renders contract meaning to approvers, and how much workflow remains inside a named vendor relationship.

Control surface

• Practical leverage sits in transaction simulation defaults, warning and enrichment policy, address-book and whitelist administration, approval and admin-quorum design, browser-extension and gateway behavior, API-signer workflow, and how much operational truth institutions let Fordefi provide before signatures are gathered.

• Fordefi matters because it packages meaning and ceremony around DeFi transactions, not because it introduces a new neutral account substrate.

• Treat Fordefi as a company-run DeFi signing and policy control plane, not as a standalone protocol primitive.

• Last reviewed: 2026-08-06 UTC