Fenwick Lending research programme.
Programme overview
- Protocol category
- Lending
- Ecosystems in scope
- Arbitrum
- In-scope components
- 4 (4 contracts)
- Languages
- Solidity
Focus areas
Where research is most wanted.
- 01
Liquidation edge cases
- 02
Interest accrual and rounding
- 03
Oracle staleness and sequencer downtime
- 04
Assumptions outside the verified model
Scope
In scope.
| Component | Type | Identifier | Notes |
|---|---|---|---|
| MarketCoreArbitrum | Smart contracts | 0x18d58527f6b1714e100c71946ea1b2f651b27139 | Supply, borrow, repay and withdraw accounting per market |
| InterestRateModelArbitrum | Smart contracts | 0x28746491ee2e6a6cf0912653e9de27b5ecd18bcb | Kinked utilisation-based borrow and supply rates |
| LiquidationEngineArbitrum | Smart contracts | 0x36669c05f0a29f1e6b08dd87aaebe1839572fa90 | Health checks and partial liquidations with close factor |
| OracleRouterArbitrum | Smart contracts | 0x1301967f595a8d0b4a15ad41023dea65354dfec9 | Price feeds with sequencer-uptime and staleness checks |
Out of scope
- Price feed providers themselves
- Governance proposals not yet executed
- Issues already reported in the research assessment
- Findings that require compromised keys or privileged access the attacker could not obtain
Severity
How findings in this programme are rated.
- Critical
- Borrowing without sufficient collateral
- Stealing supplied assets
- High
- Liquidating healthy positions
- Using stale prices during sequencer downtime
- Medium
- Interest accrual drift beyond documented bounds
- Low
- Gas inefficiencies that do not affect correctness are informational
Rules of engagement
Research within these rules.
- 01Test only against a local fork or the programme’s test deployment. Never interact with production systems or other users’ funds.
- 02Do not run denial-of-service, spam or social-engineering tests, and do not access data that is not yours.
- 03Report privately through the submission form. Keep details confidential until a disclosure date is agreed.
- 04One finding per submission, with a reproducible proof of concept where code is involved.
- 05Issues already listed in the protocol’s research assessment as acknowledged or open are not eligible for recognition.
These rules, together with the disclosure policy, define what the programme authorises. Testing outside them is not authorised.
Recognition
Validated findings receive recognition. This programme offers no monetary reward.
Acknowledgement in the report
Validated findings are credited in the protocol’s research assessment or advisory, by name or handle, with your consent.
Recognition ledger
Each validated finding becomes a ledger entry recording programme, vulnerability class, severity and validation date. Entries are published only with the researcher’s consent.
Researcher standing
Standing reflects validated findings over time: Contributor after the first, Recognised after three, Distinguished after a validated critical or high finding with a published write-up.
Research collaboration
Researchers with standing are invited to closed challenge rounds and to co-author research on the vulnerability classes they reported.
Report a finding in this programme.
One finding per submission, with steps to reproduce. Keep details private until a disclosure date is agreed.