You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we're storing binaries in the repository. I'd much rather that we store the contract code here, or alternatively put the contracts in another repository, which is built in CI. I think that this would make the flow clearer. I've noticed that no PR's to the wasm-clients branch actually pass the tests for the wasm client, and I have a feeling that could be in the contract. Each one always complains of a missing timestamp field.
From looking at wasm.proto and the tendermint proto file, we can see that that tendermint has a timestamp, while in wasm, we are dealing with only a data field. I'm going to assume that the isssue is where these interact.
The text was updated successfully, but these errors were encountered:
faddat
changed the title
Improve WASM client development flow
Consensus state in the wasm client
Sep 9, 2023
Currently, we're storing binaries in the repository. I'd much rather that we store the contract code here, or alternatively put the contracts in another repository, which is built in CI. I think that this would make the flow clearer. I've noticed that no PR's to the wasm-clients branch actually pass the tests for the wasm client, and I have a feeling that could be in the contract. Each one always complains of a missing timestamp field.
From looking at wasm.proto and the tendermint proto file, we can see that that tendermint has a timestamp, while in wasm, we are dealing with only a data field. I'm going to assume that the isssue is where these interact.
The text was updated successfully, but these errors were encountered: