Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for modern CASM format #655

Open
baitcode opened this issue Jan 17, 2025 · 2 comments · May be fixed by #656
Open

Support for modern CASM format #655

baitcode opened this issue Jan 17, 2025 · 2 comments · May be fixed by #656

Comments

@baitcode
Copy link

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.

@baitcode
Copy link
Author

Additionally, I forgot to mention that ABI field in casm is not string anymore, and also required workarond.

@baitcode
Copy link
Author

@thiagodeev @Olexandr88

I'd be grateful if you could help me to submit those changes!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant