Known-exploit-template selector deployed by any address
Rocket Pool's assessment for RD-F-162 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No documented deployment of exploit-template-matching contracts targeting Rocket Pool contract class. Rocket Pool uses unique custom contracts (RocketStorage registry pattern, oDAO committee) not derived from common Compound/Aave fork templates, reducing exploit-template-replay surface. No hack-database entry for RP-specific exploit templates. Selector-pattern index not maintained at T-10.
Sources #
- EtherscanRocketStorage EtherscanRocketStorage registry at 0x1d8f8f00cfa6758d7bE78336684788Fb0ee0Fa46 — custom storage registry pattern, not a common fork templateretrieved 2026-05-04
Methodology #
Determine whether any contract has been deployed containing a function-selector pattern matching a known exploit template targeting protocols of this class.
See the full factor methodology and distribution across all protocols →