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
It would be useful to have this data already from the API call, and not have to compute it myself (the light client delays in providing the block header in some occasions, and that affects other internal operations).
The UTC timestamp of the block at its proposal would be best. The sampling scheduled task heavily relies on this timestamp, and I'd prefer to have the most accurate one.
The text was updated successfully, but these errors were encountered:
Hey there, could the
V2
API schema be extended to provide the block's timestamp in its header?I'm talking about this endpoint:
It would be useful to have this data already from the API call, and not have to compute it myself (the light client delays in providing the block header in some occasions, and that affects other internal operations).
The UTC timestamp of the block at its proposal would be best. The sampling scheduled task heavily relies on this timestamp, and I'd prefer to have the most accurate one.
The text was updated successfully, but these errors were encountered: