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(known-issues): Add EIP 1559 stuck tnx issue #837

Merged
merged 3 commits into from
Jul 17, 2023

Conversation

qbzzt
Copy link
Contributor

@qbzzt qbzzt commented Jul 17, 2023

Closing: DEVRL-1067

@OPMattie
Copy link
Contributor

@qbzzt the detail's good; since it's a complex issue facing both operators and end users, can you add context so users of each type know if it applies to them? I believe the workarounds are different as well.

@qbzzt
Copy link
Contributor Author

qbzzt commented Jul 17, 2023

@qbzzt the detail's good; since it's a complex issue facing both operators and end users, can you add context so users of each type know if it applies to them? I believe the workarounds are different as well.

Not so much node operators, but wallet developers, dapp developers, and users. The workaround is pretty much the same, but I'll clarify how to apply it as each.

Divide the workaround between wallets, dapps, and users.
OP Chain uses EIP-1559, but with different parameters than L1 Ethereum.
As a result, while the base fee on L1 can grow by up to 12.5% in a twelve second period (in the case of a single 30M gas block), the L2 base fee can grow by up to 77% (in the case of six 30M gas blocks).
However, it still shrinks by only up to 12.5% in the same twelve second period (if all the blocks are empty).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's add something to the effect of:

When this happens, some users may see their transaction become stuck. No funds are lost, but the transaction does not clear on its own. We have a workaround that users and wallet operators can implement immediately, and we expect a protocol-level fix to be live by the end of Q4.

@qbzzt qbzzt merged commit 3c2e76a into main Jul 17, 2023
5 checks passed
@qbzzt qbzzt deleted the qbzzt/230717-eip1599-known-issue branch July 17, 2023 22:12
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