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
Problem: for caching purposes, users want to keep track of the last confirmation tx block ID / timestamp. They will then query newer objects by block ID instead of timestamp.
Add startBlock and endBlock parameters to the messages and posts endpoints.
Corner cases
Unconfirmed messages
Unconfirmed messages should always be considered as more recent than confirmed messages.
Specifying start/end dates and blocks
This should return a 422 error.
The text was updated successfully, but these errors were encountered:
Problem: for caching purposes, users want to keep track of the last confirmation tx block ID / timestamp. They will then query newer objects by block ID instead of timestamp.
Add
startBlock
andendBlock
parameters to the messages and posts endpoints.Corner cases
Unconfirmed messages
Unconfirmed messages should always be considered as more recent than confirmed messages.
Specifying start/end dates and blocks
This should return a 422 error.
The text was updated successfully, but these errors were encountered: