package iohk.chain.watch

Get desktop application:
View/edit binary Protocol Buffers messages

• rpc BlockSubscription (BlockSubscriptionRequest, stream types.Block)

  watch.proto:37

  get a stream of blocks succesfully processed by the node, this means they are already validated. the parent of a block will always be streamed before the block itself.

  message BlockSubscriptionRequest

  watch.proto:7

  (message has no fields)

• rpc TipSubscription (TipSubscriptionRequest, stream types.Header)

  watch.proto:40

  get tip updates

  message TipSubscriptionRequest

  watch.proto:9

  (message has no fields)

• rpc SyncMultiverse (SyncMultiverseRequest, stream types.Block)

  watch.proto:47

  Fetch all blocks from the blockchain storage that are descendant from the given checkpoints, The blocks are fetched from all possible branches, observing parent-to-child order. The order in which any two blocks from divergent branches are sent is not specified and should not be relied upon.

  message SyncMultiverseRequest

  watch.proto:13

  • repeated bytes from = 1

    Block IDs to start synchronization from. The client should examine previously synchronized blockchain storage, and include the ID of the latest block at or earlier than the stability depth in that saved state, as well as tips of all valid branches existing in that state. The server should prune the block IDs in the list, discarding any block IDs not found in the blockchain storage (which might be on discarded branches), as well as any blocks that are ancestors of other blocks identified in the list. The server responds with a stream sending any valid blocks on the (possibly forked) chain that are descendants of the remaining blocks in the list, unless the list is empty, in which case the server sends all blocks starting from genesis. The stream should uphold the parent-to-child order of the blocks, i.e. no block gets sent before its parent.

(message has no fields)