-
Notifications
You must be signed in to change notification settings - Fork 637
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
ICS24: Change Provable keys #7517
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bit of a nit but since we're using byte(1), byte(2)..etc, can we list them so they are:
- Commitment
- Ack
- Receipt
rather than the reverse
Quality Gate passed for 'ibc-go'Issues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tweaked packet commitment prefix key which was added post PR, do take a quick peek beofr merging if possible!
return []byte(fmt.Sprintf("acks/channels/%s/sequences/%s", channelID, sdk.Uint64ToBigEndian(sequence))) | ||
// PacketCommitmentKey returns the store key of under which a packet commitment is stored. | ||
func PacketCommitmentKey(channelID string, sequence uint64) []byte { | ||
return append(append([]byte(channelID), byte(1)), sdk.Uint64ToBigEndian(sequence)...) | ||
} | ||
|
||
// PacketCommitmentPrefixKey returns the store key prefix under which packet commitments for a particular channel are stored. | ||
func PacketCommitmentPrefixKey(channelID string) []byte { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
though wouldn't this key better belong in channel/v2/types/keys.go
? Its only used for iterating through commitments in grpc req?
Currently similar for v1 but maybe a good idea to move. Leaving as is for now.
Description
These keys are less verbose and aligned to be closer together for the same outgoing chain since we key on channelID first rather than the type of packet msg
closes: #7520
Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
docs/
).godoc
comments.Files changed
in the GitHub PR explorer.SonarCloud Report
in the comment section below once CI passes.