Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

transfer: add bridge function #1762

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

transfer: add bridge function #1762

wants to merge 1 commit into from

Conversation

vlopes11
Copy link
Contributor

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.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants