-
Notifications
You must be signed in to change notification settings - Fork 224
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
spec: proof of fork #461
Comments
As far as relationship between this follow up and the Go code:
Thus we should prioritize (1) and (3) as these may be breaking on IBC and Tendermint respectively, while (2) would be less disruptive changes to the RPC. That said, of course figuring out (2) may impact (3), so they need to be somewhat thought of together. Since these changes are to a generally underused component of the system (evidence handling), these changes should not block other integrations against Stargate releases, but they may require testnet restarts. |
@milosevic @josef-widder should we close this? |
Yes. The on-chain accountability protocol is the next thing we are doing, but there are other issues for that. |
Draft of the problem with more of an IBC lens is here.
Primary next step is to flesh out the "proof of fork" data structures and protocol for light clients to submit to full nodes and to on-chain handlers.
See the next steps in the doc and further discussion in the first PR reviews
The text was updated successfully, but these errors were encountered: