Skip to content

(feat) Contract migration system for sway contracts #289

@DefiCake

Description

@DefiCake

Currently, our approach to the sway contracts is really raw.

Unlike with solidity, where store artifacts data such as addresses, bytecode, storage layout and ABIs, and use all of these to run automated checks against new deployments, sway contracts deployment are done blindly.

We need to come up with a way to add some safety to the current process.

Currently set to XL: this task needs to be divided in smaller tasks

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