-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: add opcc slashing event #139
Conversation
CHANGELOG.md
Outdated
* [#135](https://github.com/babylonlabs-io/vigilante/pull/135) add opcc slashing event | ||
|
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.
it should be #139
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.
Thanks!
@KonradStaniec Is it okay that for the main
branch we have this piece of code for integration?
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.
@KonradStaniec Is it okay that for the main branch we have this piece of code for integration?
This seems like small piece of code so it should be fine 👍
Also e2e tests are passing so it should it seems that it is possible to subscribe to the messages that do not exists yet on Babylon (MsgEquivocationEvidence
)
Summary
This is a PR to update the BTC Slasher program to support and handle OP stack consumer chain slashing events.
It accompanies babylonlabs-io/babylon-contract#92.
Test plan
Before running integration tests, I needed to set
DOCKER_HOST
:To run tests: