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

proto: allow specifying a base denom in AssetId protos #2732

Merged
merged 1 commit into from
Jun 22, 2023

Conversation

hdevalence
Copy link
Member

This allows RPC clients to use a base denom string wherever they would encode an AssetId.

@hdevalence
Copy link
Member Author

I branched this off of 0.54.1 to allow backports, but it looks like that generated a merge conflict with the proto descriptors. Rebasing onto main.

This allows RPC clients to use a base denom string wherever they would encode
an `AssetId`.
@hdevalence hdevalence force-pushed the add-alt-base-denom-to-asset-id branch from e8c78f7 to 0763144 Compare June 22, 2023 19:50
@hdevalence hdevalence temporarily deployed to smoke-test June 22, 2023 19:51 — with GitHub Actions Inactive
@hdevalence hdevalence merged commit 94f5122 into main Jun 22, 2023
@hdevalence hdevalence deleted the add-alt-base-denom-to-asset-id branch June 22, 2023 19:59
@cratelyn cratelyn added the protobuf-changes Makes changes to the protobuf definitions. label Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
protobuf-changes Makes changes to the protobuf definitions.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants