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

feat(Upgrade): Fee payment #7938

Closed
Tracked by #7935
LHerskind opened this issue Aug 13, 2024 · 0 comments · Fixed by #9296
Closed
Tracked by #7935

feat(Upgrade): Fee payment #7938

LHerskind opened this issue Aug 13, 2024 · 0 comments · Fixed by #9296
Assignees

Comments

@LHerskind
Copy link
Contributor

LHerskind commented Aug 13, 2024

The collateral that is deposited into the fee bridge needs to decide which instance it honours in case of an upgrade.

For example, it is following along, an upgrade would mean that there is no collateral to transfer funds to the sequencer to cover the fees paid in the blocks. If this causes a failure to execute that is essentially bricking the old instance, so it should be possible to address separately.

For example, one might be able to check a value in the original bridge, if it is no longer the rollup itself, it might need to alter the fee bridge.

A separate thing to consider, if this is using multiple different bridges, it will be different types or messages that is received on the L2 side of things. Meaning that the L2 contract might not allow inserting directly unless we can let it learn that things have changed, so we might need to look into either having a contract where assets might be deposited into multiple different rollups, or passing along with the constants the address of the "current" fee bridge.

@github-project-automation github-project-automation bot moved this to Todo in A3 Aug 13, 2024
@LHerskind LHerskind changed the title feat: Fee payment feat(Upgrade): Fee payment Aug 15, 2024
@LHerskind LHerskind added this to the TestNet milestone Aug 22, 2024
@LHerskind LHerskind self-assigned this Oct 23, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in A3 Oct 24, 2024
@iAmMichaelConnor iAmMichaelConnor removed this from A3 Oct 28, 2024
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 a pull request may close this issue.

2 participants