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

Increase wasm max size #72

Closed
maurolacy opened this issue Dec 18, 2024 · 1 comment · Fixed by #75
Closed

Increase wasm max size #72

maurolacy opened this issue Dec 18, 2024 · 1 comment · Fixed by #75

Comments

@maurolacy
Copy link
Contributor

Required by over-sized babylon-contract, after latest rewards distribution functionality (babylonlabs-io/babylon-contract#96).

@maurolacy
Copy link
Contributor Author

maurolacy commented Dec 18, 2024

By the way, using the latest contract instantiation logic, this is failing silently with no error message AFAIK.

Only way to detect this that I found, was to list the contracts and notice babylon-contract was missing:

$ docker exec ibcsim-bcd bcd query wasm list-code -o json | jq -r .code_infos[].data_hash | while read H; do grep -i $H $(git rev-parse --show-toplevel)/../babylon-contract/artifacts/checksums.txt ; done
5:88b2ca0aa35cad63067817ce6ae28b05a4be74a16f586814b06b74f40028d4e0  btc_staking.wasm
3:4bba07dea4b28415d557af70a43ebe0db26f62662920b4edf67ebda05ec8d8d6  btc_finality.wasm
$

That, and a good deal of guessing and head scratching.

It would be very good to improve error handling in the SDK, so that these errors are not being swallowed along the way.
Update: Created #73 to track this.

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