Get desktop application:
View/edit binary Protocol Buffers messages
broadcast receives a reply of Acknowledgement for each common.Envelope in order, indicating success or type of failure
Status code, which may be used to programatically respond to success/failure
Info string which may contain additional information about the status returned
deliver first requires an Envelope of type DELIVER_SEEK_INFO with Payload data as a mashaled SeekInfo message, then a stream of block replies is received.
Cluster defines communication between cluster members.
Step passes an implementation-specific message to another cluster member.
StepRequest wraps a message that is sent to a cluster member.
consensus_request is a consensus specific message.
submit_request is a relay of a transaction.
StepResponse is a message received from a cluster member.
Service ClusterNodeService defines communication between cluster members.
Step passes an implementation-specific message to another cluster member.
ClusterNodeServiceStepRequest wraps a message that is sent to a cluster member.
node_conrequest is a consensus specific message between the cluster memebers.
node_tranrequest is a relay of a transaction.
Auth authentiates the member that initiated the stream
ClusterNodeServiceStepResponse is a message received from a cluster member.
Simply specified as number of messages for now, in the future we may want to allow this to be specified by size in bytes
The byte count of the serialized messages in a batch cannot exceed this value.
The byte count of the serialized messages in a batch should not exceed this value.
Any duration string parseable by ParseDuration(): https://golang.org/pkg/time/#ParseDuration
ChannelRestrictions is the mssage which conveys restrictions on channel creation for an orderer
The max count of channels to allow to be created, a value of 0 indicates no limit
ConsensusRequest is a consensus specific message sent to a cluster member.
Used in:
The consensus type: "solo" or "etcdraft".
Opaque metadata, dependent on the consensus type.
The state signals the ordering service to go into maintenance mode, typically for consensus-type migration.
State defines the orderer mode of operation, typically for consensus-type migration. NORMAL is during normal operation, when consensus-type migration is not, and can not, take place. MAINTENANCE is when the consensus-type can be changed.
Used in:
Carries a list of bootstrap brokers, i.e. this is not the exclusive set of brokers an ordering service
Each broker here should be identified using the (IP|host):port notation, e.g. 127.0.0.1:7050, or localhost:7050 are valid entries
NodeAuthRequest for authenticate the stream between the cluster members
Used in:
version represents the fields on which the signature is computed
signature is verifiable using the initiator's public key
timestamp indicates the freshness of the request; expected to be within the margin of the responsder's local time
from_id is the numerical identifier of the initiator of the connection
to_id is the numerical identifier of the node that is being connected to
session_binding is verifiable using application level protocol
NodeConsensusRequest is a consensus specific message sent to a cluster member.
Used in:
NodeTransactionOrderRequest wraps a transaction to be sent for ordering.
Used in:
last_validation_seq denotes the last configuration sequence at which the sender validated this message.
content is the fabric transaction that is forwarded to the cluster member.
SeekInfo specifies the range of requested blocks to return If the start position is not found, an error is immediately returned Otherwise, blocks are returned until a missing block is encountered, then behavior is dictated by the SeekBehavior specified.
The position to start the deliver from
The position to stop the deliver
The behavior when a missing block is encountered
How to respond to errors reported to the deliver service
Defines what type of content to deliver in response to a request
If BLOCK_UNTIL_READY is specified, the reply will block until the requested blocks are available, if FAIL_IF_NOT_READY is specified, the reply will return an error indicating that the block is not found. To request that all blocks be returned indefinitely as they are created, behavior should be set to BLOCK_UNTIL_READY and the stop should be set to specified with a number of MAX_UINT64
Used in:
SeekContentType indicates what type of content to deliver in response to a request. If BLOCK is specified, the orderer will stream blocks back to the peer. This is the default behavior. If HEADER_WITH_SIG is specified, the orderer will stream only a the header and the signature, and the payload field will be set to nil. This allows the requester to ascertain that the respective signed block exists in the orderer (or cluster of orderers).
Used in:
SeekErrorTolerance indicates to the server how block provider errors should be tolerated. By default, if the deliver service detects a problem in the underlying block source (typically, in the orderer, a consenter error), it will begin to reject deliver requests. This is to prevent a client from waiting for blocks from an orderer which is stuck in an errored state. This is almost always the desired behavior and clients should stick with the default STRICT checking behavior. However, in some scenarios, particularly when attempting to recover from a crash or other corruption, it's desirable to force an orderer to respond with blocks on a best effort basis, even if the backing consensus implementation is in an errored state. In this case, set the SeekErrorResponse to BEST_EFFORT to ignore the consenter errors.
Used in:
Used in:
(message has no fields)
SeekNextCommit refers to the next block that will be committed
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in: ,
Used in:
SubmitRequest wraps a transaction to be sent for ordering.
Used in:
last_validation_seq denotes the last configuration sequence at which the sender validated this message.
content is the fabric transaction that is forwarded to the cluster member.
SubmitResponse returns a success or failure status to the sender.
Used in:
Status code, which may be used to programatically respond to success/failure.
Info string which may contain additional information about the returned status.
TransactionOrderResponse returns a success or failure status to the sender.
Used in:
Status code, which may be used to programatically respond to success/failure.
Info string which may contain additional information about the returned status.