Common use of Technical Overview Clause in Contracts

Technical Overview. We first would like to stress the complexity of the problem by examining state-of-the-art authenticated BA protocols achieving optimal corruption resilience. Intuitively, without setup and given t < n , a quorum consisting of at least 2 3 of parties suffices to convince an honest party to adopt a value, as a counting argument shows that no quorum for a different value can exist. This is no longer the case when one demands t < n , and the overwhelming majority of protocols make use of signature based equivocation checks to assert that only one value will be adopted by honest parties during the protocol. Any attempt to increase the size of a quorum can be met with silence from corrupt parties, resulting an unhalting executions due to t < n . On the other hand, any attempt to relax equivocation checks can be met with agreement violation attacks by corrupt parties. This forces one to rethink the problem from a first principles approach.