The interface design is wired, according to the comments on cosmos:
/// This function queries transactions for events matching certain criteria.
/// 1. Client Update request - returns a vector with at most one update client event
/// 2. Transaction event request - returns all IBC events resulted from a Tx execution
The first query only return update events, but the argument also provided a event_id field: QueryClientEventRequest.event_id, which IMO is duplicated.
Implement the
query_txsfor Axon ChainEndpoint.The interface design is wired, according to the comments on cosmos:
The first query only return update events, but the argument also provided a event_id field:
QueryClientEventRequest.event_id, which IMO is duplicated.