-
Notifications
You must be signed in to change notification settings - Fork 105
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
Support EIP-1559
transactions with ZetaClient
#1952
Comments
@ws4charlie would you see an issue with using EIP-1559 transactions with ZetaClient? |
Here is a comparison of a legacy transaction and an EIP-1559 transaction: Transaction fee:
Transaction building:
Pending Transaction replacement: A legacy transaction can be replaced by a new transaction with
An EIP-1559 transaction can be replaced by a new transaction with
See Alchemy doc: https://docs.alchemy.com/docs/retrying-an-eip-1559-transaction When the gas stability pool kicks in: Two tasks to switch to EIP-1559
|
If we can do this as a first step, this would work. We will refactor the CCTX object later |
Is the formula Same for the gas tip , do you think that should be higher for tx's which are more important for the network ? |
It's a not a standard. It comes from the gas estimator. I think it's fine. We already have the mechanism of replacing/retrying a TSS transaction. |
EIP-1559
transactions with ZetaClientEIP-1559
transactions with ZetaClient
Describe the Issue
Send
EIP-1559
transactions using fee market mechanism on ZetaClient and prevent using legacy transactionsContext: #1900 (comment)
The text was updated successfully, but these errors were encountered: