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 fee manager to consensus #1245

Merged
merged 1 commit into from
Aug 6, 2024

Conversation

byte-bandit
Copy link
Contributor

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

Background

The fee manager smart contract will be independent from compass and the bridge. It will need to be deployed manually before compass, and ownership will have to be passed to compass after its deployment.

Caution

There is no support yet for automatic compass upgrades, as they will require a handover of the fee manager just like ERC20 tokens. This will be added in a follow up MR.

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.

Copy link
Contributor

@maharifu maharifu left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@byte-bandit byte-bandit merged commit 0792b6d into palomachain:dev16 Aug 6, 2024
4 checks passed
@byte-bandit byte-bandit deleted the feat/fee-mgr branch August 6, 2024 14:28
maharifu pushed a commit to VolumeFi/paloma that referenced this pull request Aug 16, 2024
# Background

The fee manager smart contract will be independent from compass and the
bridge. It will need to be deployed manually before compass, and
ownership will have to be passed to compass after its deployment.

> [!CAUTION]
> There is no support yet for automatic compass upgrades, as they will
require a handover of the fee manager just like ERC20 tokens. This will
be added in a follow up MR.

# 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.

2 participants