The decode engine currently lacks the ability to parse SCSpecStructV0 types directly from compiled Soroban WASM contract bytes. We need to implement extraction logic to parse custom struct definitions embedded within WASM contract environment segments.
Issues/what to fix
- Implement extraction of the
SCSpecStructV0 environment spec entries from WASM custom sections.
- Map the extracted byte streams into the corresponding stellar-xdr types.
- Ensure the extraction process gracefully handles missing or malformed WASM segments without crashing.
Files location
crates/core/src/spec/decoder.rs, crates/core/src/spec/wasm.rs (if applicable)
Expected result
The system can successfully read a WASM blob and return a list of SCSpecStructV0 definitions embedded within it, enabling custom struct type resolution.
Contributor telegram group
https://t.me/+sII7WPhll2liMGNk
The decode engine currently lacks the ability to parse
SCSpecStructV0types directly from compiled Soroban WASM contract bytes. We need to implement extraction logic to parse custom struct definitions embedded within WASM contract environment segments.Issues/what to fix
SCSpecStructV0environment spec entries from WASM custom sections.Files location
crates/core/src/spec/decoder.rs, crates/core/src/spec/wasm.rs (if applicable)
Expected result
The system can successfully read a WASM blob and return a list of
SCSpecStructV0definitions embedded within it, enabling custom struct type resolution.Contributor telegram group
https://t.me/+sII7WPhll2liMGNk