Seeking Alternatives for Outdated py-wasm Package

Problem

Our binary parser relies on the third-party Wasm interpreter py-wasm, which has not been maintained since 2019. Since then, the Wasm specification has evolved, introducing new instructions (#523) and possibly other features not supported by py-wasm. This issue is particularly critical as it blocks us from upgrading the Rust compiler version, which relies on these new instructions.

Temporary solution

To address this issue, we have decided to fork py-wasm and implement the missing instructions ourselves.

Long-term goal

Our ultimate goal is to identify a well-maintained third-party package developed by a reliable organization or company that can be adopted as a replacement.

Action Items

1. Forking and Implementation: We will fork py-wasm to our repository and implement missing instructions to maintain compatibility with the latest Wasm specifications.
2. Search for Alternatives: Concurrently, we are actively searching for alternative, well-maintained Wasm binary parser packages to replace py-wasm in the long term.

Start by reviewing how the binary parser depends on the outdated py-wasm package and compare that dependency with the Runtime Verification fork. Investigate maintained third-party Wasm parser alternatives and their support for newer instructions. Done means identifying a viable replacement or documenting why the fork must remain the long-term solution.