L2BEAT separates a protocol’s age from the age of its critical contracts
The Ossification view combines unchanged contract history, value exposure and upgrade conditions to sharpen infrastructure due diligence.
L2BEAT’s Ossification page asks a more precise question than how long a protocol has existed: how long have the critical contracts securing it remained unchanged? A critical change resets the clock. The view also brings together value exposure, critical changes and exit windows.
Its percentage compares contract age with a dataset of recorded code-bug exploits. It is a historical comparison, not the probability that a project is safe. Value secured over time adds context, while upgrade conditions show whether users have time to leave before a change.
For teams selecting infrastructure, the useful next step is to review the latest critical change and who can authorize the next one. Upgrades can repair vulnerabilities as well as add features. Long unchanged operation is evidence to assess alongside governance and security work, rather than a reason to ignore them.