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

Adding V3 pool roles #1200

Merged
merged 1 commit into from
Nov 28, 2024
Merged

Adding V3 pool roles #1200

merged 1 commit into from
Nov 28, 2024

Conversation

gmbronco
Copy link
Collaborator

closes #1086

Copy link

changeset-bot bot commented Nov 28, 2024

🦋 Changeset detected

Latest commit: 879d35e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
backend Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

"""
Account empowered to set static swap fees for a pool (when 0 on V2 swap fees are immutable, on V3 delegate to governance)
"""
swapFeeManager: Bytes
Copy link
Collaborator

Choose a reason for hiding this comment

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

not sure why this is bytes, lets make it string

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I guess Bytes naming comes from the contracts and it's meant to represent 0x strings. In TS it's just a String alias like BigDecimal is:
https://github.com/balancer/backend/blob/pool-roles/codegen.ts/#L15-L16
Maybe we should remove the mappings altogether to make it more understandable in the docs?

Copy link
Collaborator

Choose a reason for hiding this comment

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

agree, lets get rid of bytes and just use strings

Copy link
Collaborator

@franzns franzns Nov 28, 2024

Choose a reason for hiding this comment

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

just change the owners to strings in the schema for now, leave the mapping as is

@franzns
Copy link
Collaborator

franzns commented Nov 28, 2024

I would only change the owners types to string instead of bytes. Not sure why the owner was bytes before. Rest looks good

@gmbronco
Copy link
Collaborator Author

gmbronco commented Nov 28, 2024

I would only change the owners types to string instead of bytes. Not sure why the owner was bytes before. Rest looks good

it might be a consistency problem, because all other addresses are bytes as well.

@franzns
Copy link
Collaborator

franzns commented Nov 28, 2024

Ok. Lets leave it like this then and refactor another time 👍

@franzns franzns merged commit 16aebc3 into v3-canary Nov 28, 2024
1 check passed
@franzns franzns deleted the pool-roles branch November 28, 2024 11:00
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.

add owners for v3 pools
2 participants