-
Notifications
You must be signed in to change notification settings - Fork 410
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
non-determined gas consumed #910
Comments
To track this down, we need the contract (wasm) and the message that triggered it (and the state). This should be executable in pure rust in cosmwasm-vm and see if the gas from the vm is different, which you are expecting. However, please do not post that here, we have security@confio.gmbh for that. More information can be seen here: https://github.com/CosmWasm/advisories/blob/main/SECURITY.md We would need a reproducible test case we can run locally to investigate more. |
Maybe we also need to take a moment to narrow down the problem. |
Just want to note that events aren't an alternative mechanism for observing consensus state. They don't, and can't, make any guarantees re: ordering, consistency, or determinism. If you need those guarantees, you need to consume consensus state directly, you can't use an event subscription. |
In v0.29 non deterministic events were addressed. @bruce-wayne2 can you run your tests with that version again? |
I'm tracking down an issue that is causing non-functioning consensus between nodes.
When I execute a contract method on Wormhole, the gas consumption returned by the method is inconsistent between each node.
The gas consumption of one part is 309187 and the other part is 309188.
All nodes run in docker containers.
wasmd version:
v0.27.0
wasmvm version:
v1.0.0
libwasmvm version:
libwasmvm_muslc.x86_64.a
I output the gas consumption for each step:
node1:
node2:
wasmd/x/wasm/keeper/keeper.go
Line 933 in 8213046
The text was updated successfully, but these errors were encountered: