Admin keys
Upgrade authority, multisig posture, and ownership paths.
DeFi audits — config risk
Config-risk audits with evidence, not adjectives.
The risk is in the configuration. GridFleet reviews operational risk surfaces that matter to DAO treasuries, protocols, and institutional DeFi holders — and every finding comes back sourced.
Findings sourced · References on-chain · Lane defi-audit
Scroll
01 — Risk surfaces
Where protocolsactually break.
Code audits check the contract. Config-risk audits check who can change it, what it depends on, and how control moves — the operational surfaces where most real losses start.
Oracle dependency
Market data surfaces and failure concentration.
Governance drift
Timelocks, bypass paths, proposal history, and control movement.
Receipts
Contract addresses, transaction references, and sourced findings.
02 — The deliverable
A risk memoyou can verify.
Every audit runs in the defi-audit policy lane and returns like any other fleet job: the memo, the flags, and the receipt over the evidence bundle. You check the sources — you don't take our word.
- Every finding cites the contract address or transaction it came from
- Public configuration inputs only — no privileged access required
- Flags ranked by control impact, not adjectives
- Checksummed evidence bundle with the memo
03 — Start
Name the protocol.Get the memo.
Tell us the protocol and what you hold. We scope the review, run it through the lane, and return the memo with its receipts.