Timelock on sensitive actions

PancakeSwap's assessment for RD-F-033 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Timelock (6h) covers governance-directed changes. However: (1) 6h is thin at $1.73B TVL; (2) current timelock admin is a dormant EOA (last active Aug 2021); (3) Infinity/V4 contracts may have separate admin paths not going through this legacy timelock; (4) not all sensitive functions (mint, rescue) confirmed to route through timelock.

Sources #

Etherscan
PancakeSwap Timelock — BscScanBscScan Timelock 0xA1f482Dc — 21700s delay; last executed April 2021retrieved 2026-04-28
Docs
PancakeSwap FAQPancakeSwap FAQ — timelock mentioned as security measureretrieved 2026-04-28

Methodology #

For each sensitive action category (mint / pause / rescue / setOracle / upgrade), determine whether execution requires going through the declared timelock.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol pancakeswap factor RD-F-033 score yellow collected_at 2026-04-28 19:10:57