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
That wouldn't work in case of reorgs. An alternative would be to increment a counter for each rpc request and/or pass the block hash of the current tip.
RPC responses should include a monotonically updating metric that guarantees to be correct any value equal or less-than itself.
The only monotonically updating metric in bitcoin is the 'total-work-done'. That even in the case of a reorg, must always update monotonically.
PRC responses should have a 'correct as of: (total-work-done)' metric.
Clients of the RPC can sort responses by the (total-work-done) metric to find the most current result. (say if querying a few servers at once).
The text was updated successfully, but these errors were encountered: