Allows clients to observe the status of their submissions.
CommandsValidation may be submitted via the Command Submission Service.
The on-ledger effects of their submissions are disclosed by the
TransactionValidation Service.
CommandsValidation may fail in 4 distinct manners:
INVALID_PARAMETER gRPC error on malformed payloads and missing
required fields.
Failure communicated in the SubmitResponse.
Failure communicated in a CompletionValidation.
A Checkpoint with record_time > command mrt arrives through the
CompletionValidation Stream, and the command's CompletionValidation was not visible
before. In this case the command is lost.
Clients that do not receive a successful completion about their
submission MUST NOT assume that it was successful.
Clients SHOULD subscribe to the CompletionStream before starting to
submit commands to prevent race conditions.
Interprocess tracing of command submissions may be achieved via Zipkin
by filling out the trace_context field.
The server will return a child context of the submitted one, (or a new
one if the context was missing) on both the CompletionValidation and TransactionValidation streams.
Allows clients to observe the status of their submissions.
CommandsValidation may be submitted via the Command Submission Service.
The on-ledger effects of their submissions are disclosed by the TransactionValidation Service.
CommandsValidation may fail in 4 distinct manners:
INVALID_PARAMETER gRPC error on malformed payloads and missing required fields.
Failure communicated in the SubmitResponse.
Failure communicated in a CompletionValidation.
A Checkpoint with record_time > command mrt arrives through the CompletionValidation Stream, and the command's CompletionValidation was not visible before. In this case the command is lost.
Clients that do not receive a successful completion about their submission MUST NOT assume that it was successful.
Clients SHOULD subscribe to the CompletionStream before starting to submit commands to prevent race conditions.
Interprocess tracing of command submissions may be achieved via Zipkin by filling out the trace_context field.
The server will return a child context of the submitted one, (or a new one if the context was missing) on both the CompletionValidation and TransactionValidation streams.