Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit introduces a new bridge functionality to the transfer contract's state. This function enables any sequencer to register as a bridge provider upon staking a balance into the bridge. The authorized sequencer can then facilitate up to the amount of their stake in bridge operations.
Adopting an optimistic approach, the bridge will process transactions without immediately verifying L1 associated events. However, it will keep track of these events and wait for several blocks before considering a transaction finalized. If a fraud proof is presented, demonstrating that a bridge operation was carried out without a valid L1 event, the responsible sequencer stands to lose all rewards and staked amount. In contrast, the individual who exposed the fraudulent activity will be rewarded with the ill-gotten amount.