hasTx

public boolean hasTx()

required bytes tx = 1;

The serialized bytes of the transaction in Satoshi format.
For version 1:
* It must be signed and completely valid and ready for broadcast (ie it includes the
necessary fees) TODO: tell the client how much fee it needs
* Its first output must be a 2-of-2 multisig output with the first pubkey being the
primary's and the second being the secondary's (ie the script must be exactly "OP_2
ProvideRefund.multisig_key Initiate.multisig_key OP_2 OP_CHECKMULTISIG")
For version 2:
* It must be signed and completely valid and ready for broadcast (ie it includes the
necessary fees) TODO: tell the client how much fee it needs
* Its first output must be a CHECKLOCKTIMEVERIFY output with the first pubkey being the
primary's and the second being the secondary's.

getTx

public com.google.protobuf.ByteString getTx()

required bytes tx = 1;

The serialized bytes of the transaction in Satoshi format.
For version 1:
* It must be signed and completely valid and ready for broadcast (ie it includes the
necessary fees) TODO: tell the client how much fee it needs
* Its first output must be a 2-of-2 multisig output with the first pubkey being the
primary's and the second being the secondary's (ie the script must be exactly "OP_2
ProvideRefund.multisig_key Initiate.multisig_key OP_2 OP_CHECKMULTISIG")
For version 2:
* It must be signed and completely valid and ready for broadcast (ie it includes the
necessary fees) TODO: tell the client how much fee it needs
* Its first output must be a CHECKLOCKTIMEVERIFY output with the first pubkey being the
primary's and the second being the secondary's.

setTx

The serialized bytes of the transaction in Satoshi format.
For version 1:
* It must be signed and completely valid and ready for broadcast (ie it includes the
necessary fees) TODO: tell the client how much fee it needs
* Its first output must be a 2-of-2 multisig output with the first pubkey being the
primary's and the second being the secondary's (ie the script must be exactly "OP_2
ProvideRefund.multisig_key Initiate.multisig_key OP_2 OP_CHECKMULTISIG")
For version 2:
* It must be signed and completely valid and ready for broadcast (ie it includes the
necessary fees) TODO: tell the client how much fee it needs
* Its first output must be a CHECKLOCKTIMEVERIFY output with the first pubkey being the
primary's and the second being the secondary's.

clearTx

The serialized bytes of the transaction in Satoshi format.
For version 1:
* It must be signed and completely valid and ready for broadcast (ie it includes the
necessary fees) TODO: tell the client how much fee it needs
* Its first output must be a 2-of-2 multisig output with the first pubkey being the
primary's and the second being the secondary's (ie the script must be exactly "OP_2
ProvideRefund.multisig_key Initiate.multisig_key OP_2 OP_CHECKMULTISIG")
For version 2:
* It must be signed and completely valid and ready for broadcast (ie it includes the
necessary fees) TODO: tell the client how much fee it needs
* Its first output must be a CHECKLOCKTIMEVERIFY output with the first pubkey being the
primary's and the second being the secondary's.

hasInitialPayment

public boolean hasInitialPayment()

required .paymentchannels.UpdatePayment initial_payment = 2;

To open the channel, an initial payment of the server-specified dust limit value must be
provided. This ensures that the channel is never in an un-settleable state due to either
no payment tx having been provided at all, or a payment that is smaller than the dust
limit being provided.

getInitialPayment

To open the channel, an initial payment of the server-specified dust limit value must be
provided. This ensures that the channel is never in an un-settleable state due to either
no payment tx having been provided at all, or a payment that is smaller than the dust
limit being provided.

setInitialPayment

To open the channel, an initial payment of the server-specified dust limit value must be
provided. This ensures that the channel is never in an un-settleable state due to either
no payment tx having been provided at all, or a payment that is smaller than the dust
limit being provided.

setInitialPayment

To open the channel, an initial payment of the server-specified dust limit value must be
provided. This ensures that the channel is never in an un-settleable state due to either
no payment tx having been provided at all, or a payment that is smaller than the dust
limit being provided.

mergeInitialPayment

To open the channel, an initial payment of the server-specified dust limit value must be
provided. This ensures that the channel is never in an un-settleable state due to either
no payment tx having been provided at all, or a payment that is smaller than the dust
limit being provided.

clearInitialPayment

To open the channel, an initial payment of the server-specified dust limit value must be
provided. This ensures that the channel is never in an un-settleable state due to either
no payment tx having been provided at all, or a payment that is smaller than the dust
limit being provided.

getInitialPaymentBuilder

To open the channel, an initial payment of the server-specified dust limit value must be
provided. This ensures that the channel is never in an un-settleable state due to either
no payment tx having been provided at all, or a payment that is smaller than the dust
limit being provided.

getInitialPaymentOrBuilder

To open the channel, an initial payment of the server-specified dust limit value must be
provided. This ensures that the channel is never in an un-settleable state due to either
no payment tx having been provided at all, or a payment that is smaller than the dust
limit being provided.

hasClientKey

public boolean hasClientKey()

optional bytes client_key = 3;

This field is added in protocol version 2 to send the client public key to the server.
In version 1 it isn't used.
This must be a raw pubkey in regular ECDSA form. Both compressed and non-compressed forms
are accepted. It is only used in the creation of the multisig contract.

getClientKey

public com.google.protobuf.ByteString getClientKey()

optional bytes client_key = 3;

This field is added in protocol version 2 to send the client public key to the server.
In version 1 it isn't used.
This must be a raw pubkey in regular ECDSA form. Both compressed and non-compressed forms
are accepted. It is only used in the creation of the multisig contract.

setClientKey

This field is added in protocol version 2 to send the client public key to the server.
In version 1 it isn't used.
This must be a raw pubkey in regular ECDSA form. Both compressed and non-compressed forms
are accepted. It is only used in the creation of the multisig contract.

clearClientKey

This field is added in protocol version 2 to send the client public key to the server.
In version 1 it isn't used.
This must be a raw pubkey in regular ECDSA form. Both compressed and non-compressed forms
are accepted. It is only used in the creation of the multisig contract.