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: add gas estimation logistics to Skyway #1243

Merged
merged 3 commits into from
Aug 4, 2024

Conversation

byte-bandit
Copy link
Contributor

@byte-bandit byte-bandit commented Aug 4, 2024

Related Github tickets

Background

This change adds the needed building bricks for gas estimation to the Skyway module, which works independently from the consensus module and regular relay messages. Ideally, the Skyway stuff should be boiled down to only perform some additional logic on top of the CQ, but for now, we will have to live with this solution.

Testing completed

  • test coverage exists or has been added/updated
  • tested in a private testnet

Breaking changes

  • I have checked my code for breaking changes
  • If there are breaking changes, there is a supporting migration.

@byte-bandit byte-bandit requested a review from maharifu August 4, 2024 16:57
x/skyway/module.go Dismissed Show resolved Hide resolved
@byte-bandit
Copy link
Contributor Author

@maharifu Since you're off today, I'm going to merge to gain some velocity. Feel free to still take a look, any findings can be addressed in a follow up.

@byte-bandit byte-bandit merged commit 157916e into palomachain:dev16 Aug 4, 2024
4 checks passed
@byte-bandit byte-bandit deleted the feat/skyway-pigeon-feed branch August 4, 2024 17:33
maharifu pushed a commit that referenced this pull request Aug 16, 2024
# Related Github tickets

- VolumeFi#1761
- VolumeFi#344

# Background

This change adds the needed building bricks for gas estimation to the
Skyway module, which works independently from the consensus module and
regular relay messages. Ideally, the Skyway stuff should be boiled down
to only perform some additional logic on top of the CQ, but for now, we
will have to live with this solution.

# Testing completed

- [x] test coverage exists or has been added/updated
- [ ] tested in a private testnet

# Breaking changes

- [x] I have checked my code for breaking changes
- [x] If there are breaking changes, there is a supporting migration.
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.

1 participant