Get desktop application:
View/edit binary Protocol Buffers messages
WatchOnly exposes RPCs used by a remote signer to connect to a watch-only node.
SignCoordinatorStreams dispatches a bi-directional streaming RPC that allows a remote signer to connect to a watch-only node and remotely provide signatures and ECDH results on demand.
The request ID this response refers to.
The remote signer responses can only be of certain types.
The Signer Registration message is sent by the remote signer when it connects to the watch-only lnd node, to initialize a handshake between the nodes.
To ensure that the remote signer is still active and alive, the watch-only node can send a Ping message to remote signer. This Pong message should then be sent by the remote signer to respond to the Ping message.
The remote signer's corresponding response to a Shared Key request.
The remote signer's corresponding response to a Sign Message request.
The remote signer's corresponding response to a Mu Sig2 Session request.
The remote signer's corresponding response to a Mu Sig2 Register Nonces request.
The remote signer's corresponding response to a Mu Sig2 Register Combined Nonces request.
The remote signer's corresponding response to a Mu Sig2 Get Combined Nonces request.
The remote signer's corresponding response to a Mu Sig2 Sign request.
The remote signer's corresponding response to a Mu Sig2 Combine Sig request.
The remote signer's corresponding response to a Mu Sig2 Cleanup request.
The remote signer's corresponding response to a Sign Psbt request.
If the remote signer encounters an error while processing a request, it will respond with a SignerError message that details the error.
A unique request ID of a SignCoordinator gRPC request. Useful for mapping requests to responses. Note that request_id 1 is reserved for the handshake with between watch-only node and the remote signer.
Messages between the watch-only node and the remote signer can only be of certain types.
The Registration Response message is returned by the watch-only lnd as a response to SignerRegistration message.
To ensure that the remote signer is still active and alive, the watch-only lnd can send a Ping message to the remote signer, which should then respond with the respective Pong message.
Requests a shared public key from the remote signer.
Requests that the remote signer signs the passed message.
Requests a MuSig2 Session of the remote signer.
Requests that the remote signer registers a nonce with the referenced MuSig2 Session.
Requests that the remote signer registers a combined nonce with the referenced MuSig2 Session.
Requests that the remote signer gets a combined nonce with the referenced MuSig2 Session.
Requests that the remote signer signs the passed message digest with the referenced MuSig2 Session.
Requests that the remote signer combines and adds the passed partial signatures for the referenced MuSig2 Session.
Requests that the remote signer removes/cleans up the referenced MuSig2 session.
Requests that the remote signer signs the passed PSBT.
Used in:
Holds the signature generated by the watch-only node when signing the registration_challenge provided by the remote signer in SignerRegistration.
Contains information about the watch-only lnd that may be useful for the remote signer.
Used in:
The registration response indicates either a successful registration or an error.
Sent by the watch-only lnd when the remote signer registration is successful.
Contains details about any errors that occurred during remote signer registration.
Used in:
Details an error which occurred on remote signer.
Used in:
The registration challenge allows the remote signer to pass data that will be signed by the watch-only lnd. The resulting signature will be returned in the RegistrationResponse message.
The registration info contains details about the remote signer that may be useful for the watch-only lnd.