Timelock on sensitive actions
Spiko's assessment for RD-F-033 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No timelock on any action category (mint/pause/rescue/setOracle/upgrade). All privileged actions route through Permission Manager roles gated by the 2-of-5 Safe with no on-chain delay. Pause function callable immediately by exceptional-operator.
Sources #
- DocsSpiko smart contracts architecture blogtech.spiko.io describes seven Permission Manager groups with no timelock on any; exceptional-operator can pause immediately; super-admin can upgrade immediatelyretrieved 2026-05-16
- Token implementation ABI on EtherscanToken ABI at 0x15EA0EC4: pause(), unpause(), mint(), upgradeToAndCall() all callable without timelock guard; Permission Manager ABI at 0x344278af confirms no timelock roleretrieved 2026-05-16
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 spiko factor RD-F-033 score red collected_at 2026-05-15 22:52:13