Skip to content

smart rollup node: add optional check status param in batcher rpc

What

I add an optional check status param in the batcher RPC. This check allows to tell the rollup node batcher to no try to submit again a message that was already submitted. This a interesting for the evm node for example when it catches up and we don't won't the rollup node to lose all their fund republising messages that was already submitted.

Why

It's going to be useful for the evm node so it's catchup mechanism make the baker burn found less quickly

How

If the flag is true then the message has no counter attached to it and so the id of the message is only based on the message itself. Also if the flag is true we check that the id of the message has no l1 operations linked to it.

Manually testing the MR

Checklist

  • Document the interface of any function added or modified (see the coding guidelines)
  • Document any change to the user interface, including configuration parameters (see node configuration)
  • Provide automatic testing (see the testing guide).
  • For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
  • Select suitable reviewers using the Reviewers field below.
  • Select as Assignee the next person who should take action on that MR
Edited by Sylvain R.

Merge request reports

Loading