r0gue-io/pop-cli

feat: get runtime metadata from WASM file

Open

#507 opened on Apr 2, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (39 forks)github user discovery
DevExenhancementgood first issuelow

Repository metrics

Stars
 (113 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Why do we need this feature?

We learnt that this feature is used across commands like pop bench and pop try-runtime and it does increase the experience significantly.

  • With pop bench, current issue is with the hooks and pallet names.
  • With pop try-runtime, we can use this feature to compare the spec version / name of a remote node and a provided blob and throws the error early.

Current Status

Latest branch of https://github.com/chevdor/subwasm works well but the published version on crates.io is not up-to-date which makes the remote crate not compatible with our codebase. Need to consider alternative approach or re-implement our own version of the functionalities of subwasm that we need.

Contributor guide

Research direction
Investigate how to extract runtime metadata from WASM blobs. Study the subwasm crate codebase for inspiration, or explore the Substrate runtime API for spec version and pallet names. Then implement a solution in pop cli.
Tech stack
rust
Domain
backendblockchaincli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustWASM basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45