Skip to content

Support for modern CASM format #655

Closed
@baitcode

Description

@baitcode

Problem statement:

I'm trying to deploy contract built with scarb >= 2.7.0 to sepolia network using recipe from here (kindly provided by @thiagodeev). But all I got was error from the node, stating:

{
     "jsonrpc": "2.0",
     "id": 3,
     "error": {
        "code": 60,
        "message": "The compiled class hash did not match the one supplied in the transaction"
    }
}

As I need this functionality in golang I started digging and realised that library has fallen behind agains the recent casm format, especially it lacks accounting of bytecode_segment_lengths field. That results in incorrect class hash.

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