[Din] draft-mazieres-dinrg-scp-04 (page 16) transitioning from prepare to commit.

[Piers Powlesland <[e-mail]>]

At the end of section 3.6 there is the following statement.

   A node leaves the PREPARE phase and proceeds to the COMMIT phase when
   there is some ballot "b" for which the node confirms "prepare(b)" and
   accepts "commit(b)".  (If nodes never changed quorum slice mid-
   protocol, it would suffice to accept "commit(b)".  Also waiting to
   confirm "prepare(b)" makes it easier to recover from liveness
   failures by removing Byzantine faulty nodes from quorum slices.)

I'm trying to understand how we know that when a node accepts
commit(b), the network will come to agreement on b.value. I'm
considering the case where nodes do not change slice mid-protocol
where a node accepts commit(b) via quorum threshold.

So far I have come up with this:

We know that the quorum of nodes nodes that have voted to commit(b)
cannot vote for another ballot, although they potentially could accept
commit for a different ballot and they could also abort their vote for
commit(b).

But we know that a vote to commit(b) indicates that these nodes have
left the nomination phase and therefore can only change the value in
their ballots through accepting incompatible ballots via blocking
threshold, since we have seen a quorum of nodes vote commit(b) we know
that there is at least one of these nodes in all quorums and therefore
no quorum could accept,  prepared or committed, any ballot with a
value other than b.

So we can say securely that the nodes we have seen vote commit(b),
cannot accept a commit with a different value or abort their vote.

Now I'm wondering how do we know at this point that the network will
not get stuck? For instance how do we know that a quorum that contains
one of the nodes that has voted to commit(b), may not have nodes that
vote for a higher incompatible ballot, that they can never accept?

So my thinking thus far is that:

The node that has voted to commit(b) in this quorum must have seen
every node in the quorum accept prepare(b). If we consider any one of
those nodes that have accepted prepare(b), in order for it to accept a
new ballot prepared it will need to hear from the rest of its quorum
and when it does hear from the rest of its quorum, it will in fact
confirm prepare(b) at which point the node stops considering new
values for its ballots. So we can see that nodes will not get stuck
voting for higher incompatible ballots.

It would be good to know if I'm on the right track or If I have gone
off the deep end? And also I'm still not clear at all on why nodes
changing mid slice makes it necessary to confirm prepare(b) and accept
commit(b) so any explanation of that would be great!

Thanks,

Piers