feat: add disableMessageFromOriginEvent to AbsInbox - #346
Conversation
|
We require contributors to sign our Contributor License Agreement. In order for us to review and merge your code, please sign the linked documents below to get yourself added. https://na3.docusign.net/Member/PowerFormSigning.aspx?PowerFormId=b15c81cc-b5ea-42a6-9107-3992526f2898&env=na3&acct=6e152afc-6284-44af-a4c1-d8ef291db402&v=2 |
|
Jorge Silva seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
|
pretty sure |
* example * fix hardhat tests
|
We require contributors to sign our Contributor License Agreement. In order for us to review and merge your code, please sign the linked documents below to get yourself added. https://na3.docusign.net/Member/PowerFormSigning.aspx?PowerFormId=b15c81cc-b5ea-42a6-9107-3992526f2898&env=na3&acct=6e152afc-6284-44af-a4c1-d8ef291db402&v=2 |
The existing
InboxMessageDeliveredFromOriginevent emitted by sendL2MessageFromOrigin omits the messageData to save gas. This forces off-chain indexers to retrieve the calldata for each tx, slowing down synchronization and increasing complexity.This PR introduces a configurable option to change the event emitted by
sendL2MessageFromOriginin the Inbox contracts.The goal is to enable faster and simpler synchronization for off-chain services, particularly for L3 appchains where minimizing L1/L2 settlement gas costs is less critical than data accessibility speed.