Re-deployed to new addresses in last year
A operational history factor in the v1.7.0 rubric. Measured per protocol on a e cadence.
Methodology how we score#
What this measures
This factor records whether the protocol redeployed to a new set of contract addresses in the trailing twelve months, retiring at least one previously-live contract that held user funds. Redeployments are detected via on-chain history and protocol announcements. This does not include proxy upgrades (which preserve the address), only full address migrations. It flags the risk that a migration introduced new, unaudited code or created a window during which user funds were briefly in a less-secure state.
Why it matters
Full redeployments are high-risk events for two related reasons. First, the new contracts are effectively new code that begins life with no battle-testing clock, resetting the age signal (RD-F-076). Second, redeployments often occur under operational pressure (post-exploit remediation, V2 launches) when the team's attention is divided and the temptation to skip re-audit is strongest. GMX V1 ($42M recovered, 2025) was exploited via a security patch added three years after the last audit -- a redeployment-style risk even without a full address migration. Several protocols in the dataset also exploited migration windows to front-run users moving funds to the new version.
Green / Yellow / Red
Green: no redeployment to new addresses in the trailing twelve months. Yellow: one redeployment with a full audit of the new contracts and public migration announcement with adequate lead time. Red: redeployment without a new audit of the migrated code, or redeployment with fewer than seventy-two hours of public notice to allow users to exit.
Common gray cases
Protocols that operate a perpetual multi-version architecture (V1 and V2 simultaneously live) are distinguished from full migrations; the score applies only to deployments intended to replace prior versions that held user funds.
Notable historical examples
No cross-hacked incidents currently linked in database for this factor.
Measurement what to look for#
Determine whether the protocol retired prior deployed contracts and redeployed to a new address set in the last 12 months.