You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we do not have any easy way to retrieve our states as ssz objects, instead
their json representation is returned with fields encoded in base64.
Describe the solution you'd like
Our debug endpoints instead return the ssz representation of the state. Since
these endpoints are only for debugging runtime problems it would make sense for
them to be ssz encoded.
Describe alternatives you've considered
Manually converting the current format would be cumbersome.
The text was updated successfully, but these errors were encountered:
@terencechain that would be really hard if we tried to amend our current blocks endpoint to return ssz. You mean adding a new debug endpoint called debug/blocks that returns [][]byte ?
For less UX friction, I think it has be a separate end point. Use case is to rerun state transition. Having ssz state is not enough without ssz block to rerun the state transition to debug consensus issues
馃殌 Feature Request
Description
Currently we do not have any easy way to retrieve our states as ssz objects, instead
their json representation is returned with fields encoded in base64.
Describe the solution you'd like
Our debug endpoints instead return the ssz representation of the state. Since
these endpoints are only for debugging runtime problems it would make sense for
them to be ssz encoded.
Describe alternatives you've considered
Manually converting the current format would be cumbersome.
The text was updated successfully, but these errors were encountered: