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 WriteAcknowledgement emits a recv_packet event with a single attribute. This assumes that the write acknowledgement function is called along with the WriteReceipt function that has all the other packet attributes. However, with the introduction of asynchronous acks, written acknowledgements may not happen in the same tx as the packet receipt.
Thus, we will still want all the relevant attributes emitted during the WriteAcknowledgement call so that a relayer can use the events of that single tx to construct the MsgAcknowledgement to relay (except for the proof).
The text was updated successfully, but these errors were encountered:
Currently
WriteAcknowledgement
emits arecv_packet
event with a single attribute. This assumes that the write acknowledgement function is called along with theWriteReceipt
function that has all the other packet attributes. However, with the introduction of asynchronous acks, written acknowledgements may not happen in the same tx as the packet receipt.Thus, we will still want all the relevant attributes emitted during the
WriteAcknowledgement
call so that a relayer can use the events of that single tx to construct theMsgAcknowledgement
to relay (except for the proof).The text was updated successfully, but these errors were encountered: