Make 02-client messages modular #7155
Labels
S:proposed
T: Dev UX
UX for SDK developers (i.e. how to call our code)
Type: Code Hygiene
General cleanup and restructuring of code to provide clarity, flexibility, and modularity.
Milestone
Summary
Reduce
02-client
messages into a singular concrete implementation so every client doesn't need to reproduce code.Problem Definition
While implementing solo machine I basically copy pasted the tendermint client messages. I think all clients would end up doing the same since there isn't much flexibility needed in creating clients, updating clients, and submitting misbehaviour.
Proposal
Move
MsgCreateClient
,MsgUpdateClient
andMsgSubmitMisbehaviour
to02-client
types with the following definitions:This will reduce redundant code. The only downside I see is storing the client state and consensus state in
MsgCreateClient
since their might be some overlap.For Admin Use
The text was updated successfully, but these errors were encountered: