FuelLabs/fuel-core

WASM block production can fail if new `fuel-core` supports new types of transactions

Open

#2,679 建立於 2025年2月7日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)Rust (57,084 star) (2,861 fork)batch import
buggood first issue

描述

If we add new types like BlockV2 or a new type of transaction, the old WASM code can't deserialize them.

The current WASM executor will ruin the whole block during production if one of the transactions is new.

We must teach the WASM executor to deserialize transactions individually and discard unserializable transactions.

貢獻者指南

技術棧
rustwasm
領域
blockchain
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Rust programmingWASM conceptsFuel protocol basics
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
The issue is to modify the WASM executor in fuel core to handle individual transaction deserialization and skip unknown ones. Key files likely involve the WASM block producer code, possibly in crates/fuel core/src/executor or similar. One should look for existing deserialization logic for transactions in the WASM executor and implement fallback to skip transactions that fail to deserialize.
WASM block production can fail if new `fuel-core` supports new types of transactions · FuelLabs/fuel-core#2679 | Good First Issue