Closed fedsten closed 3 years ago
This is a protocol-specific parameter, how the agreement is reached defined by particular protocol. For instance, with RGB this is a ContractId, i.e. hash of the genesis, so all parties will know it beforehand.
Was closed with the commitment referenced above. It states in the text that the parameter should be agreed between parties beforehand, or otherwise defaults to 0
lnpbp-3 specification states that the committing and verifying parties should agree on a commitment-specific parameter
c
, which is then used to compute the index of the output containing the commitment. It is unclear to me when and how the agreement on this parameter happens. In particular if Alice agrees with Bob on a specificc
parameter, she may also agree at the same time with Carol on an alternativec
parameter, resulting in two different output indexes and therefore making it possible for Alice to double spend her tokens showing two different commitments in two different outputs of the same transaction to Bob and Carol, with neither of them being able to notice the other hidden commitment. If, on the other hand,c
is previously defined in the commitment of the parent transaction, this should be described into lnpbp-1 commit procedure.