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

[xgreenx]

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.

[MitchTurner]

and discard unserializable transactions.

This seems dangerous and will result in a fork. Don't we want to fail/stop if there is something it can't deserialize?

[MitchTurner]

@xgreenx I think we should discuss the desired behavior here more ^^^

[xgreenx]

It will not cause a fork, because it is logic on the block producer side, not validation side. Validation still should fail