Private betaVerified 2026-08-17
Smart-Contract Security
Review DeFlow's deployed contract architecture, upgrade boundary, governance powers, and assurance status.
The current release uses contracts deployed on Ethereum Sepolia. An external contract audit has not yet been engaged, so this page describes the implementation rather than making an assurance claim.
Deployment model
| Contract | Current model |
|---|---|
| Escrow | Complete per-deal CREATE2 deployment; non-upgradeable |
| EscrowFactory | Plain deployment; creates escrows, maintains token allowlist, can pause new deployments |
| FeeRouter | UUPS/ERC1967 proxy; governance-authorised upgrades |
| ReferralVault | Plain non-upgradeable deployment |
Governance
The current Sepolia deployment is controlled by a single externally owned account. It is not protected by a Safe multisig or timelock.
Depending on contract state, governance can:
- pause or resume new escrow deployments;
- update the token allowlist and FeeRouter used by the factory;
- settle a funded escrow after its deadline;
- resolve a dispute by allocating funds between counterparties;
- trigger refunds; and
- seize and reroute escrowed assets to a quarantine wallet through the emergency path.
Do not describe the current system as removing all counterparty or governance risk. The current release must be used only with Sepolia assets that have no monetary value.
Verify independently
Use the addresses on Fees and supported assets and the deal screen to inspect Sepolia transactions. Contract source, deployment manifests, automated tests, and a future independent audit serve different assurance purposes; none should be substituted for another.