mirror of
https://github.com/nspcc-dev/neo-go.git
synced 2026-03-01 04:28:51 +00:00
Testnet state mismatch at 4368840 #1338
Labels
No labels
I1
I2
I3
I4
S1
S2
S3
S4
U0
U1
U2
U3
U3
U4
blocked
bug
bug
cli
compiler
config
config
consensus
dependencies
discussion
documentation
enhancement
epic
feature
go
good first issue
help wanted
neotest
network
oracle
performance
question
rpc
security
smartcontract
task
task
task
test
vm
wallet
windows
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neo-go#1338
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @roman-khimov on GitHub (Jul 25, 2024).
Originally assigned to: @roman-khimov on GitHub.
Current Behavior
State mismatch.
Expected Behavior
State match.
Possible Solution
Fix the damn thing.
Steps to Reproduce
Testnet.
Context
Testnet!
Regression
No.
Your Environment
uname -a):@roman-khimov commented on GitHub (Jul 25, 2024):
Tx:
Script (deployment):
@roman-khimov commented on GitHub (Jul 25, 2024):
Manifest:
@roman-khimov commented on GitHub (Jul 25, 2024):
@roman-khimov commented on GitHub (Jul 26, 2024):
@lock9, can this transaction be one of yours? I'm interested in how this manifest was produced, fixing the node side is rather trivial, but I don't see how this can happen in a regular compiler use flow.
@lock9 commented on GitHub (Jul 26, 2024):
Hello @roman-khimov,
Yes, that's mine. Maybe it's my serialization / deserialization code that has caused this?
Note: Maybe it's unrelated (probably is), but I saw this error https://github.com/neo-project/neo/issues/3439 when I tried to send a transaction using an incorrect network magic.

Nef serialization code:
@roman-khimov commented on GitHub (Jul 26, 2024):
It's all about the manifest. Compiler outputs valid manifest on its own (with all fields), but if you do some additional processing then empty values can get mangled.
@lock9 commented on GitHub (Jul 26, 2024):
Hm. Could that be caused by mismatching NEF/manifest? Is the manifest generated when there are compilation errors? I saw some weird behavior when I tried to recompile and redeploy a contract with syntax errors.
Could concurrency cause that? I also recompile my files frequently (automatically)
Maybe I formated the manifest json (added indentation) before deploying it (I can't recall it)
@roman-khimov commented on GitHub (Jul 26, 2024):
It's not indented, but it looks like it was edited somehow. Compiler always emits groups/trusts/features fields, but they're missing from the manifest.
@lock9 commented on GitHub (Jul 26, 2024):
I didn't make those changes manually. I remember being confused about the permissions, but I'm sure I didn't change the manifest.