You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The message_hash field in the L1HandlerTxnReceipt structure is currently defined as a u64.
This type is insufficient because L1 message hashes, a defined in ethereum-based, are represented as 256-bit values (H256).
Expected behavior:
the message_hash field should be defined as H256 to correctly represent the 256-bit nature of the hash
Steps to reproduce:
Related code:
/// receipt for l1 handler transaction#[derive(Clone,Debug,Eq,Hash,PartialEq,Serialize,Deserialize)]pubstructL1HandlerTxnReceipt<F>{/// The message hash as it appears on the L1 core contract#[serde(with = "NumAsHex")]pubmessage_hash:u64,#[serde(flatten)]pubcommon_receipt_properties:CommonReceiptProperties<F>,}
Other information:
The text was updated successfully, but these errors were encountered:
Bug Report
types-rs version:
Current behavior:
The message_hash field in the L1HandlerTxnReceipt structure is currently defined as a u64.
This type is insufficient because L1 message hashes, a defined in ethereum-based, are represented as 256-bit values (H256).
Expected behavior:
the message_hash field should be defined as H256 to correctly represent the 256-bit nature of the hash
Steps to reproduce:
Related code:
Other information:
The text was updated successfully, but these errors were encountered: