Proto commits in input-output-hk/chain-libs

These 47 commits are when the Protocol Buffers files have changed:

2021-10-13

network: Reworded the doc on SyncMultiverseRequest Avoid unclear use of "below".

The documentation is generated from this commit.

Document a special case of SyncMultiverse In case there are no checkpoint blocks known by the server, it will stream blocks from the genesis, as a way to do full sync.

Change parameter fields for SyncMultiverseRequest Use block ID checkpoints instead of a single starting length.

Reorg watch proto in chain-network Reuse protobuf message types between the node and watch protocols: share the definitions of common message types in protobuf package iohk.chain.types, shared between node and watch service packages. Change the namespacing of the code generated by tonic-build to allow reuse in the Rust module system.

Remove mempool subscription from watch.proto No need for this functionality right now.

Renamed the client subscription service to Watch The SubscriptionService name is a bit generic and makes stupid generated module names for the service and client implementations of the protocol.

Moved the watch protocol to chain-network Removed chain-watch as a separate crate.

setup basic PoC watch.proto

2021-09-08

setup basic PoC watch.proto

2021-04-16

Change PeersResponse format

2020-11-23

chain-network: use checkpoints mechanism in PullBlocks similar to PullBlocksToTip

chain-network: add PullBlocks endpoint to request a range of blocks

2020-10-02

Added client side node ID auth to protocol Added RPC method ClientAuth to provide authenticated node ID also from the client side. The server's HandshakeResponse now features a nonce that the client signs to create a signature for its node ID.

Add node ID authentication to protocol handshake

2020-05-04

Remove folders network-core and network-grpc Clean up the code for old tokio 0.1 crates.

Begin porting network to tonic and tokio 0.2 Replacing network-core and network-grpc with a single crate, chain-network. It combines the functionality of two (the protocol abstraction layer in mod core, the gRPC implementation in mod grpc, common data type definitions and error types), ported to tokio 0.2 APIs and tonic/hyper as the gRPC stack.

2020-04-02

bottle in sea network service

2020-03-11

Begin porting network to tonic and tokio 0.2 Replacing network-core and network-grpc with a single crate, chain-network. It combines the functionality of two (the protocol abstraction layer in mod core, the gRPC implementation in mod grpc, common data type definitions and error types), ported to tokio 0.2 APIs and tonic/hyper as the gRPC stack.

2020-02-13

add peers message in protobuf

2019-09-17

network: Rename Content to Fragment In service type name and the subscription method name of what was named "content" use "fragment" for consistency with other naming.

2019-07-23

network: Add Handshake method The Handshake RPC method is a way to query the server for the supported protocol and the genesis block hash, so that the client can detect a wrong chain or an incompatible peer.

2019-07-12

chain-core, network: Rename Message to Fragment

2019-07-01

network: PushHeaders and missing blocks event Add a new BlockEvent variant, missing, with a PullHeadersRequest structure that the service can use as a reverse PullHeaders request. Add method PushHeaders to respond to this solicitation by sending up a chain of headers.

2019-06-07

network: Added method PullHeaders Reusing some NTT prior art, add a method that pulls blockchain headers between one of the checkpoint IDs of blocks present at the requester, and the ID of a block up to which the chain needs to be retrieved.

2019-05-13

network: Redesign block subscription for upload Block subscription stream now can retrieve solicitations for blocks from the client, which can fulfill the solictitation with client streaming method UploadBlocks.

2019-04-24

Rename repeated field in protobuf type BlockIds Rename id to ids so that it looks more natural in generated code.

2019-04-08

network: pass node ID along with subscriptions Change the gRPC protocol and network-core abstractions to pass the subscriber's node ID along with subscription requests. Currently this is to be implemented via gRPC metadata (an HTTP header); later on the ID may need to be verifiable with the connection's TLS certificate. Start with the server side, not yet supported on the client. Drop the sender ID field from Gossip.

2019-03-27

network: Restore Gossip as batch message For Poldercast to work as per the paper, it's important to receive gossip updates in batches of node messages.

Rework the node gossip protocol Make node gossip propagated bidirectionally, like blocks and transactions. Each gossip message carries information on a single node.

network: Renamed TransactionService To ContentService, serving messages.

2019-03-21

network-grpc: Remove a disused protobuf type BlockSubscriptionRequest is no more.

network: Introduce bidirectional subscriptions Added bidirectional subscription methods to gRPC protobuf definitions and network-core client API (server support pending).

network-grpc: remove announce response types

2019-03-18

Consolidate protobuf in network-grpc Remove codes.proto and move node.proto under network-grpc as the only user of the protobuf files.

2019-03-05

Drop redundant methods.

Support announce transactions method.

Implement block announcement protocol.

Gossip protocol implementation.

2019-03-01

Add get transactions support in grpc.

Introduce protocol conformant API in the network service.

Convert TipRequest to return Header instead of (id,date).

2019-02-25

network: Added gRPC method SubscribeToBlocks Designed the subscription API for the block service and its network-core counterpart.

2019-01-30

network: Rename StreamBlocksTo* to PullBlocksTo* "Stream" looks redundant in protobuf, especially in generated names like StreamBlocksToTipStream; "Pull" better reflects the use case.

2019-01-17

Crate network-core Moved the abstract network interface definitions, incubated in network-grpc, to a new dedicated crate network-core. The interfaces rely on enum types generated from protobuf descriptions. For this, the protobuf declarations of enums have been split out into a dedicated package codes.proto which is used by the build script of network-core to generate the types and make them available as module codes.

2019-01-09

network-grpc: Flatten and simplify the protocol The named wrapper types are redundant, both for their intended purpose and in the wire format. Field ids in a message sufficiently identify the purpose and format of the field value. Therefore, the type definitions in types.proto have been removed. The proto package name has been changed to iohk.chain.node to reflect the now-generic nature of the protocol.

network-grpc: Redesign for abstract network serialization We cannot rely on From impls to convert between chain types associated with the Node impl and protobuf data types, as these would have to be defined somewhere that is gnostic of both the gRPC network protocol and the concrete chain implementation. Part of the solution is changing the protobuf definitions for basic chain data types to allow opaque serialization. Thankfully, the only such message type that sported specific fields was BlockDate, so this is redefined to carry opaque bytes. At the same time HeaderHash is renamed to BlockId to match the naming used by the chain abstraction traits.

Initial code for network-grpc server Moved from the internal project and adapted to chain-core definitions. The abstract interface is defined in network_core, to be moved to its own crate.