Describe your idea, in simple words.
In the body or header of the response to the /matches endpoint, include the tip that the result is accurate up to.
Why is it a good idea?
When integrating data from multiple sources, or when implementing time-sensitive / event-sourced applications, it is often important to know at what time the data received is accurate as of. There is a difference between:
- a set of matches for a wallet that has had no activity for a long time
- a set of matches for a wallet against a kupo instance that is not yet up to date
This can also be identified by hitting the health endpoint, but given latency, it can be difficult to know "for sure" that your results are in sync.
That is, the results you get back from /matches could be as of a different slot than the response from /health issued shortly before or shortly after.
Are you willing to work on it yourself?
Willing? yes; Able? probably not.
Describe your idea, in simple words.
In the body or header of the response to the
/matchesendpoint, include the tip that the result is accurate up to.Why is it a good idea?
When integrating data from multiple sources, or when implementing time-sensitive / event-sourced applications, it is often important to know at what time the data received is accurate as of. There is a difference between:
This can also be identified by hitting the health endpoint, but given latency, it can be difficult to know "for sure" that your results are in sync.
That is, the results you get back from
/matchescould be as of a different slot than the response from/healthissued shortly before or shortly after.Are you willing to work on it yourself?
Willing? yes; Able? probably not.