Skip to content

Remove the legacy-mock expiry-stamping migration once it is superseded #3978

Description

@barakeinav1

Background

#3785 (#3293) added a one-time migration helper, stamp_expiry_on_legacy_mocks, that stamps an expiry on pre-existing stored MockAttestation entries so the standard cleanup flow can evict them. It now lives in the version-specific migration module crates/contract/src/v3_13_0_state.rs (a free fn, called from the From<MpcContract> impl there).

It is transitional: the migration module is deleted once the migration source version moves past 3.13.0 (routine migration cleanup, cf. #3771), and the helper is removed together with it. Leaving it is harmless (idempotent — with_expiry never extends an existing expiry).

Acceptance Criteria

  • stamp_expiry_on_legacy_mocks (its From-impl call site and its test) is removed together with the v3_13_0_state migration module when the pre-expiry migration is retired.

Resources & Additional Notes

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions