Expand description
Pull complete NEAR indexer messages over HTTP without running a node.
Client::poll returns ordered rollback/application work. Process the whole
Update and persist its checkpoint in the same transaction as consumer
state. The client never advances a cursor or acknowledges queue delivery.
Re-exports§
pub use near_kit;
Structs§
- Backoff
- Retry delays for one failing request; start a new one per request.
- Checkpoint
- The last block durably processed by a consumer, exclusive on the next poll.
- Client
- Sequential, pull-based indexing; consumer speed supplies backpressure.
- Crypto
Hash - A 256-bit hash used in NEAR Protocol.
- Header
- Minimal ancestry and finality context from the ordinary block RPC.
- Indexer
Block - Official indexer payload with the endpoint’s explicit execution coverage.
- Plan
- The headers of an
Update, before any block is fetched. - Retry
- How to retry after one failed attempt.
- Retry
Policy - Pacing for retrying one request at a time.
- Streamer
Message - Resulting struct represents block with chunks
- Update
- Work to apply atomically with its checkpoint; dropping it acknowledges nothing.