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

Refactor IBC packet definitions to have clear separation b/w provider and consumer #77

Open
Tracked by #272
gusin13 opened this issue Sep 17, 2024 · 0 comments
Open
Tracked by #272
Assignees

Comments

@gusin13
Copy link
Contributor

gusin13 commented Sep 17, 2024

The IBC packet definitions are bit scattered in codebase and needs some refactoring to have clear separation b/w the packets flowing from

Provider -> Consumer
Consumer -> Provider

message ConsumerIBCPacket {
repeated SlashedFinalityProvider slashed_fp = 1;
}

message ConsumerRegisterIBCPacket {
// consumer_name is a unique identifier for the consumer chain
string consumer_name = 1;
// consumer_description is a brief explanation of the consumer chain's purpose
string consumer_description = 2;
}
// ConsumerSlashingIBCPacket defines the slashing information that a Consumer sends to Babylon's ZoneConcierge upon a
// Consumer slashing event.
// It includes the FP public key, the Consumer block height at the slashing event, and the double sign evidence.
message ConsumerSlashingIBCPacket {
/// evidence is the FP slashing evidence that the Consumer sends to Babylon
babylon.finality.v1.Evidence evidence = 1;
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants