Node API
Complements the availability API by serving eventually consistent data that is not necessarily agreed upon by all nodes
The availability API provides a pure view of snapshots of the Espresso blockchain at various points in time. Because it strives for robustness and purity, it does not include aggregate statistics like block or transaction counts, which may briefly return incorrect results and will gradually correct themselves as missing data is fetched. The node API does provide this data, making it a useful complement to the availability API.
In other words, while the availability API is a view of the blockchain abstractly, the node API provides information about this node's view of the chain, at the present moment in time.
Endpoints
GET /node/block-height
/node/block-height
Get the height of the chain as known to this node. This is equal to one more than the height of the latest known block. It is not a count of the blocks in this node's database, as blocks earlier than the latest known block could be missing.
Returns integer
integer
GET /node/transactions/count
/node/transactions/count
Get the number of finalized transactions. This count may be too low if blocks are missing from the database.
Returns integer
integer
GET /node/payloads/total-size
/node/payloads/total-size
Get the total size, in bytes, of all finalized block payloads. This count may be too low if blocks are missing from the database.
Returns integer
integer
GET /node/vid/share
/node/vid/share
Get the VID share belonging to this node for a given block.
Paths
/node/vid/share/:height
/node/vid/share/hash/:hash
/node/vid/share/payload-hash/:payload-hash
Parameters
Returns VidShare
VidShare
The specific format of this type is not currently specified, but it can be deserialized and interpreted in Rust using the VidShare
type.
GET /node/sync-status
/node/sync-status
Get the node's progress in syncing with the latest state of blockchain.
If the node is fully synced (that is, all the missing
counts are 0 and pruned_height
is null
or 0) other endpoints in this API should give accurate results.
Returns
GET /node/header/window
/node/header/window
Get a range of consecutive headers by timestamp window.
Returns all available headers, in order, whose timestamps fall between :start
(inclusive) and :end
(exclusive), or between the block indicated by :height
or :hash
(inclusive) and :end
(exclusive). The response also includes one block before the desired window (unless the window includes the genesis block) and one block after the window. This proves to the client that the server has not omitted any blocks whose timestamps fall within the desired window.
It is possible that not all blocks in the desired window are available when this endpoint is called. In that case, whichever blocks are available are included in the response, and next
is null
to indicate that the response is not complete. The client can then use one of the /from/
forms of this endpoint to fetch the remaining blocks from where the first response left off, once they become available. If no blocks are available, not even prev
, this endpoint will return an error.
Paths
/node/header/window/:start/:end
/node/header/window/from/:height/:end
/node/header/window/from/hash/:hash/:end
Parameters
Returns
Last updated