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

fix: ensure no invalid opcodes in wasm light client binary #92

Merged
merged 1 commit into from
May 26, 2023

Conversation

benluelo
Copy link
Contributor

@benluelo benluelo commented May 24, 2023

also added a check to ensure that sign-ext opcodes don't find their way back into the binary.

this also provides a significant improvement to the size of the binary, from 2.8M to 1.1M (758K to 322K gzipped).

closes #91

@benluelo benluelo force-pushed the 91-wasm-light-client-contains-invalid-opcodes branch from 10182ee to bd9fc0d Compare May 24, 2023 22:44
cor
cor previously approved these changes May 24, 2023
@benluelo benluelo force-pushed the 91-wasm-light-client-contains-invalid-opcodes branch from bd9fc0d to 524c0b8 Compare May 24, 2023 22:58
@benluelo benluelo requested a review from aeryz May 24, 2023 23:04
@benluelo benluelo force-pushed the 91-wasm-light-client-contains-invalid-opcodes branch from 524c0b8 to c09430f Compare May 26, 2023 10:46
@benluelo benluelo merged commit 82ad5ef into main May 26, 2023
@benluelo benluelo deleted the 91-wasm-light-client-contains-invalid-opcodes branch May 26, 2023 10:56
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 this pull request may close these issues.

Wasm light client contains invalid opcodes
4 participants