Same attributes for all connection/ channel/ packet IBC events
Code for extracting IBC events from Tx notifications is currently unnecessarily verbose as event attribute sets for a given category, e.g. connection, vary depending on the actual event. Also, in some handlers there are missing attributes that are useful for monitoring or some relayer strategies.
Emmit events with same attributes in connection handlers. Here are the details:
Add new counterparty connection ID event attribute, counterparty_connection_id, to HandleMsgConnectionOpenInit and HandleMsgConnectionOpenTry
Add following attributes to HandleMsgConnectionOpenAck and HandleMsgConnectionOpenConfirm:
client_id
counterparty_connection_id
counterparty_client_id
Emmit events with same attributes in channel handlers. Here are the details:
HandleMsgChannelOpenAck, HandleMsgChannelOpenConfirm, HandleMsgChannelCloseInit and HandleMsgChannelCloseConfirm:connection_idcounterparty_port_idcounterparty_channel_idAdd following attributes to AcknowledgePacket:
packet_data
Hi, can I work on this?
@dauTT that would be great thanks
Hi, I have changed the connection.proto file and defined a message, MsgConnectionBasic, that will carry all the common attributes of different connections msg. Now I would like to generate the connection.pb.go file but I have problem to use correctly the protoc compiler. Could someone explain me how to generate pb.go file correctly?

I was able to generate the 'pb.go' file that I need with this commands:
protoc -I=. -I=./third_party/proto -I=./proto --go_out=$GOPATH/src ./proto/ibc/connection/connection.proto
but the output is quite different from the other pb.go files in the cosmos-sdk repository.
I believe we will need to wait to fix first #6476, before I can continue with this issue.
@dauTT you can use make proto-gen
Hi @anilCSE ,
I have tried but it doesn't work for me. So I have raised this issue here: #6476
Most helpful comment
Hi, can I work on this?