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
UnreceivedAcknowledgements currently takes in a list of acknowledgements and checks to see if the packet commitment still exists. The list of acknowledgements is obtained via a gRPC which returns all existing acknowledgements (even if the have been acknowledged on the sending chain). That gRPC should take in an optional list of packet commitments and only return acknowledgements for that list of packet commitments.
Problem Definition
The issue is acknowledgements live forever so it isn't sustainable to expect a relayer to be able to query for all ack sequences. Currently such a query returns ~64k sequences
Proposal
Add an additional field to the QueryPacketAcknowledgementsRequest which takes in a list of packet commitments. For each packet commitment, if the acknowledgement has been written, that sequence should be added to the array returned in the QueryPacketAcknowledgementsResponse
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged/assigned
The text was updated successfully, but these errors were encountered:
colin-axner
changed the title
UnreceivedAcks should take in packet commitment sequences not a list of acknowledgements
Allow PacketAcknowledgements to take in packet commitments for filtering
Sep 2, 2021
@colin-axner This should remain backwards compatible right? If no commitments are included in the req, all should be added to the returned array as it works today, correct?
@colin-axner This should remain backwards compatible right? If no commitments are included in the req, all should be added to the returned array as it works today, correct?
Summary
UnreceivedAcknowledgements
currently takes in a list of acknowledgements and checks to see if the packet commitment still exists. The list of acknowledgements is obtained via a gRPC which returns all existing acknowledgements (even if the have been acknowledged on the sending chain). That gRPC should take in an optional list of packet commitments and only return acknowledgements for that list of packet commitments.Problem Definition
The issue is acknowledgements live forever so it isn't sustainable to expect a relayer to be able to query for all ack sequences. Currently such a query returns ~64k sequences
Proposal
Add an additional field to the
QueryPacketAcknowledgementsRequest
which takes in a list of packet commitments. For each packet commitment, if the acknowledgement has been written, that sequence should be added to the array returned in theQueryPacketAcknowledgementsResponse
For Admin Use
The text was updated successfully, but these errors were encountered: