-
Notifications
You must be signed in to change notification settings - Fork 165
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
Invalid checksum error when deploy contract(version3.6.2) #928
Comments
The format of the NEF hasn't changed with that commit. It seems to only change the allowed size of the I'll try out the new 3.6.2. compiler and see if I can reproduce |
I tried running the const myNef = sc.NEF.fromBuffer(
readFileSync(
"path\\to\\nef\\file"
)
) Do you know which neon-js version you are using? |
|
Can you please share the code snippet used that caused the error and also what you now use that works? The checksum in the file seems correct, so this is a strange case and we need a bit more information to investigate. |
The |
This is what I tested with other versions of the contract. It has not been updated. The code is the same, just the files are different. Please ignore it. |
The problem was occurring because neon-js had a problem when deserializing a compiler that uses all 64 available characters And since the compiler you are using is probably some version from the master branch instead of the one at NuGet, the compiler name occupies all 64 chars ( I created a PR to fix this problem. |
When we deployed the 3.6.2 version contract with
neonjs
, aninvalid checksum
error occurred.I found that the latest version of
n3 compiler 3.6.2
deleted theMaxScriptLength
field of thenefFile file
, which changed the calculation method ofchenkSum
. I guess it may be related to this.neo-project/neo@efa8659#diff-e5a9d7d849aceff46a01663d9e6246d09c4c82e49af60f21dc879d05c40481ee
The text was updated successfully, but these errors were encountered: