Expand description
A node’s view of a HotShot chain
The node API provides a subjective view of the HotShot blockchain, from the perspective of
one particular node. It provides access to information that the
availability API does not, because this information depends on the
perspective of the node observing it, and may be subject to eventual consistency. For example,
/node/block-height may return smaller counts than expected, if the node being queried is not
fully synced with the entire history of the chain. However, the node will eventually sync and
return the expected counts.
Re-exports§
Modules§
- data_
source 🔒 - Data for the
nodeAPI. - query_
data 🔒
Structs§
- Custom
Snafu - SNAFU context selector for the
Error::Customvariant - Limits
- Options
- Query
Snafu - SNAFU context selector for the
Error::Queryvariant - Query
VidSnafu - SNAFU context selector for the
Error::QueryVidvariant - Query
Window Snafu - SNAFU context selector for the
Error::QueryWindowvariant - Request
Snafu - SNAFU context selector for the
Error::Requestvariant - Resource
Sync Status - A summary of the
SyncStatusfor a single resource (e.g. blocks, or leaves). - Sync
Status Query Data SyncStatusfor the entire database.- Sync
Status Range - The
SyncStatusdescribing a range of consecutive objects of a single type. - Time
Window Query Data - Response to a
/:resource/windowquery.
Enums§
- Error
- Sync
Status - A status of a set of resources, regarding its presence in the database.
- Window
Start