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

Add ErrorReceipt to 04-channel protobuf definitions #1605

Closed
3 tasks
damiannolan opened this issue Jun 29, 2022 · 1 comment
Closed
3 tasks

Add ErrorReceipt to 04-channel protobuf definitions #1605

damiannolan opened this issue Jun 29, 2022 · 1 comment
Assignees

Comments

@damiannolan
Copy link
Member

Summary

ErrorReceipt defines a type which encapsulates the upgrade sequence and error associated with the
upgrade handshake failure. When a channel upgrade handshake is aborted both chains are expected to increment to the
next sequence.

message ErrorReceipt {
    uint64 sequence = 1;
    string error_msg = 2;
}
  • sequence: Sequence contains the sequence at which the error occurred. Both chains are expected to increment to the next sequence after the upgrade is aborted.
  • error_msg: ErrorMsg contains an arbitrary string which chains may use to provide additional information as to why the upgrade was aborted.

For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged/assigned
@damiannolan damiannolan added this to the 04-channel upgrades alpha milestone Jun 29, 2022
@damiannolan damiannolan mentioned this issue Jun 29, 2022
10 tasks
@damiannolan damiannolan self-assigned this Jun 29, 2022
@crodriguezvega crodriguezvega moved this to Backlog in ibc-go Jun 29, 2022
@crodriguezvega crodriguezvega changed the title Add ErrorReceipt to 04-channel protobuf defintions Add ErrorReceipt to 04-channel protobuf definitions Jun 29, 2022
@damiannolan damiannolan moved this from Backlog to Done in ibc-go Jul 18, 2022
@damiannolan
Copy link
Member Author

#1613

@crodriguezvega crodriguezvega moved this from Todo to Done in ibc-go Nov 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done 🥳
Development

No branches or pull requests

1 participant