Skip to content

Commit c1f8829

Browse files
committed
coalition proposals commit to specific listen announcements
1 parent cdd78b6 commit c1f8829

1 file changed

Lines changed: 14 additions & 1 deletion

File tree

02_coalition_formation.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,11 @@ Short-lived listen advertisements may be signed by "makers" using their online k
116116

117117
Alternatively, negotiation with listening but unaddressible UTXO owners can be made possible using an opt-in gossip layer. On this layer, it's permitted to broadcast partially accepted proposals. See below for a discussion of flood protection considerations in this setting.
118118

119-
### Co-spend proposals
119+
Listen advertisements can specify constraints for proposals being entertained, indicating that proposals outside of the constrained subspace (see coalition proposal details below for specifics) are unacceptable at any price.
120+
121+
Finally, listen advertisements also indicate the owner's willingness to serve as a validator node in transaction construction, as either demanding to be a one, opting in at the aggregator's discretion, or declining. The aggregator has an incentive be a validator (and to do so honestly), but is not required to.
122+
123+
### Co-Spend proposals
120124

121125
Co-spend proposals specify a set of outpoints of coins intended to be spent together. Fully accepted proposals take effect contingent on the conditions they specify, such as the range of feerates the offer is valid under, `nLocktime` ranges, or whether or not txid stability is required (i.e. only SegWit inputs). The effect of a proposal is some confidential redistribution of the input funds, e.g. fees negotiated between the transacting parties.
122126

@@ -162,6 +166,15 @@ Any peer may attempt to construct a coalition proposal by aggregating unanimousl
162166

163167
Unlike co-spend proposals, coalition proposals are accepted with a regular signature by the online key. This makes them tractable for aggregators to make coalition proposals that revise the payoff or omit peers who didn't accept. As discussed above, coalition proposals aren't mutually exclusive. If a peer rejects a coalition proposal due to the inclusion of a specific proposal, it may broadcast a counter final proposal of its own, so there's no mechanism for explicit rejection.
164168

169+
A coalition proposal also specifies a concrete transaction construction
170+
protocol version, and commits to a specific set of listen advertisements
171+
associated with the specified UTXOs, which have either demanded or opted into
172+
serving as validators. These peers agree to allow other peers to connect to
173+
them and facilitate in gossip. Depending on the liveness requirements of
174+
byzantine agreement for the subsequent transaction construction protocol, the
175+
aggregator may specify validators at their discretion and named parties may
176+
accept or decline.
177+
165178
#### Bootstrapping consensus for transaction construction
166179

167180
Once a coalition proposal is fully accepted, a coalition has been formed, complete with a payoff imputation. The online keys are then used to initiate a consensus protocol to construct the full transaction.

0 commit comments

Comments
 (0)