Additional Related Work Sample Clauses

Additional Related Work. ‌ Threshold signatures [43, 80, 50, 85, 10, 55] can guarantee that a sufficiently large number of parties signed the message, while keeping the signature-length (including all information needed to verify) independent of n. However, threshold signatures require the keys to be generated by a trusted party in a correlated way (e.g., as a Shamir sharing of the signing key), and the signature- reconstruction protocol of existing schemes does not offer succinct aggregation in “small” batches. SRDS imply threshold signatures by having the setup algorithm produce the PKI for the parties, and using the aggregation algorithm to reconstruct a signature. We note that Xxxxxx et al. [70] constructed fully distributed threshold signatures that do not require any setup assumptions. However, this scheme is not applicable in our setting, since it requires an interactive key-generation protocol to generate the public and secret keys, and this protocol in turn uses a broadcast channel. In fact, as indicated by our lower bound, some form of private-coin setup is inherently needed for constructing SRDS. Multi-signatures [60, 77, 10, 5, 72, 13] guarantee that a subset of parties signed the message. Unlike threshold signatures, correlated trusted setup is not needed and a bulletin-board PKI suffices; in addition, some of the constructions enable succinct aggregation in “small” batches. Aggregate signatures [12, 73, 11, 72, 69, 56] are a similar primitive that allows aggregating signatures on different messages. The main distinction of SRDS is succinctness that enables verification without knowing the signing parties. This property is crucial for our BA protocol construction. Group signatures [27] and ring signatures [84] allow any individual party to sign a message on behalf of a set while hiding their identity. This is different than our setting where we need to prove that a majority of the parties signed the message. | |
Additional Related Work. ‌ As mentioned earlier, the t + 1 lower bounds for deterministic BA [FL82, DS83] were extended to rule out strict-constant-round t-secure randomized BA for t = Θ(n) [CMS89, KY86, CPS19]; these bounds show that any such r-round BA must fail with probability at least (c r)−r for a constant c, a result that is matched by the protocol of [GGL22]. Xxxxx et al. [CHM+22] showed that for t > n/3, two-round BA is unlikely to reach agreement with constant probability, implying that the expected round complexity must be larger; this essentially matches Xxxxxx’x XX [Mic17] that terminates in three rounds with probability 1/3. Attiya and Censor-Hillel [AC10] extended the results on worst-case round complexity for t = Θ(n) from [CMS89, KY86] to the asynchronous setting, showing that any r-round A-BA must fail with probability 1/cr for some constant c. In the dishonest-majority setting, expected-constant-round broadcast protocols were initially studied by Xxxxx et al. [GKKO07], who established feasibility for t = n/2 + O(1) as well as a negative result. A line of work [FN09, CPS20, WXDS20, WXSD20, SLM+23] established expected- constant-round broadcast for any constant fraction of corruptions under cryptographic assumptions. Synchronous and (binary) asynchronous OCC protocols in the information-theoretic setting were discussed earlier. Using the synchronous protocol in [BE03], Xxxxxx and Xxxxx [MR90] showed how to realize a perfectly unbiased common coin in expected-constant rounds for t < n/3 over secure channels (recall that this task is impossible in asynchronous networks [dSKT22]). In the cryptographic setting, both synchronous and asynchronous OCC protocols with optimal resiliency are known, relying on various computational assumptions; we mention a few here. Beaver and So [BS93] gave two protocols tolerating t < n/2 corruptions in synchronous networks, which are secure under the quadratic residuosity assumption and the hardness of factoring, respectively. Xxxxxx et al. [CKS05] presented two protocols for t < n/3 and asynchronous networks, which are secure in the random oracle model based on the RSA and Xxxxxx-Xxxxxxx assumptions, respectively. Xxxxxxx [Nie02] showed how to eliminate the random oracle and construct an asynchronous OCC protocol relying on standard assumptions alone (RSA and DDH). Although these constructions are for asynchronous networks, they can be readily extended to work in synchronous networks for t < n/2 (e.g., so that they can be used in the co...
Additional Related Work. The literature on Byzantine agreement is vast (especially, on complete networks), and we limit ourselves to those that are most relevant to this work, mainly focusing on sparse networks. Most prior works on Byzantine protocols on sparse networks assume an underlying expander graph, where the expansion properties prove crucial in solving fundamental problems such as agreement and leader election, see, e.g., [19, 41, 30]. The protocol of [30] builds an underlying communication mechanism where messages can be relayed with only polylog (n) overhead. The issue with all the above protocols, as mentioned earlier, is that they assume that nodes have global knowledge of the network topology to begin with. Such an assumption does not work where nodes start with local knowledge of only themselves and their immediate neighbors, as is common in real-world P2P networks (including those that implement cryptocurrencies and blockchains) which are bounded degree and sparse. Xxxxxx and Xxxxx [13, 12] improved on the efficiency of Dwork et al [19]. Their main result is an algo- rithm that achieves consensus in the butterfly network using O(t +ln n ln ln n) one-bit parallel transmission steps while tolerating t = O(n/ ln n) corrupted processors and having O(t ln t) confused processors (i.e., uncorrupted processors that have decided on the incorrect bit). The number of rounds, corrupted processors that can be tolerated, and confused processors in this result are all asymptotically optimal for the butterfly network. Ben-Or and Xxx designed a bounded degree network and an almost-everywhere agreement al- gorithm that is fully polynomial and tolerates a linear number of faults with high probability if the faulty processors are randomly located throughout the network [11]. King et al. [29] describe protocols for Leader Election and Byzantine Agreement that take polylogarithmic rounds and require each processor to send and process a polylogarithmic number of bits. These protocols only run on complete networks and do not apply to sparse networks. The work of [4] presented a fully-distributed algorithm for Byzantine agreement in the presence of Byzantine nodes and high adversarial churn. The algorithm could tolerate (only) up to √n/ polylog (n) Byzantine nodes and up to √n/ polylog (n) churn per round and took a O(polylog (n)) number of rounds. The work of [5] used the Byzantine agreement protocol of [4] and designed a fully-distributed algorithm for Byzantine leader election that coul...

Related to Additional Related Work

  • Related Work Leave not to exceed one (1) year may be granted to an employee to accept a position of fixed duration outside of State service which is funded by a government or private foundation grant and which is related to the employee's current work.

  • Performance of the Work The Contractor shall perform all of the Work required for the complete and prompt execution of everything described or shown in, or reasonably implied from the Contract Documents for the above referenced Project.

  • Additional Work If changes in the work seem merited by Consultant or the City, and informal consultations with the other party indicate that a change is warranted, it shall be processed in the following manner: a letter outlining the changes shall be forwarded to the City by Consultant with a statement of estimated changes in fee or time schedule. An amendment to this Agreement shall be prepared by the City and executed by both Parties before performance of such services, or the City will not be required to pay for the changes in the scope of work. Such amendment shall not render ineffective or invalidate unaffected portions of this Agreement.

  • Modified Work/Return to Work Programs The Employer and the Union recognize the purpose of modified work/return to work programs, is to provide fair and consistent practices for accommodating nurses who have been ill, injured or permanently disabled, to enable their safe return to work. The parties undertake to provide safe and meaningful employment for all nurses based on the following objectives and principles:

  • PERFORMANCE OF THE CONTRACT II.1.1. The Contractor shall perform the Contract to the highest professional standards. The Contractor shall have sole responsibility for complying with any legal obligations incumbent on him, notably those resulting from employment, tax and social legislation. II.1.2. The Contractor shall have sole responsibility for taking the necessary steps to obtain any permit or licence required for performance of the Contract under the laws and regulations in force at the place where the tasks assigned to him are to be executed. II.1.3. Without prejudice to Article II.3 any reference made to the Contractor’s staff in the Contract shall relate exclusively to individuals involved in the performance of the Contract. II.1.4. The Contractor must ensure that any staff performing the Contract have the professional qualifications and experience required for the execution of the tasks assigned to them. II.1.5. The Contractor shall neither represent the Agency nor behave in any way that would give such an impression. The Contractor shall inform third parties that he does not belong to the European public service. II.1.6. The Contractor shall have sole responsibility for the staff who execute the tasks assigned to him. II.1.7. In the event of disruption resulting from the action of a member of the Contractor's staff working on Agency premises or in the event of the expertise of a member of the Contractor's staff failing to correspond to the profile required by the Contract, the Contractor shall replace him without delay. The Agency shall have the right to request the replacement of any such member of staff, stating its reasons for so doing. Replacement staff must have the necessary qualifications and be capable of performing the Contract under the same contractual conditions. The Contractor shall be responsible for any delay in the execution of the tasks assigned to him resulting from the replacement of staff in accordance with this Article. II.1.8. Should any unforeseen event, action or omission directly or indirectly hamper execution of the tasks, either partially or totally, the Contractor shall immediately and on his own initiative record it and report it to the Agency. The report shall include a description of the problem and an indication of the date on which it started and of the remedial action taken by the Contractor to ensure full compliance with his obligations under the Contract. In such event the Contractor shall give priority to solving the problem rather than determining liability. II.1.9. Should the Contractor fail to perform his obligations under the Contract in accordance with the provisions laid down therein, the Agency may - without prejudice to its right to terminate the Contract - reduce or recover payments in proportion to the scale of the failure. In addition, the Agency may impose penalties or liquidated damages provided for in Article II.16.

  • Modified Work Where the Hospital and the Union agree, the Hospital may implement modified/rehabilitative work programs in order to assist employees returning to work following illness or injury. To facilitate these programs, it is understood and agreed that provisions of the collective agreement may, where agreed, be varied. The specific terms of the program will be signed by the Hospital and the Union.

  • Modified Work Program The Employer shall provide modified work for any employee injured on the job as per the requirements of the Workers’ Safety and Insurance Board. The employee must co-operate in developing and participating in, a modified work program suited to his capabilities, and with the approval of his physician and/or the WSIB. Both the Employer and the employee shall work together to return the employee to good health and his regular duties.

  • Modified Work/Return to Work (a) The parties recognize the duty of reasonable accommodation for individuals under the Human Rights Code of Ontario and agree that this Collective Agreement will be interpreted in such a way as to permit the Employer and the Union to discharge that duty. (b) If an employee becomes disabled, including WSIB, with the result that she is unable to perform the regular functions of her position, the Employer may determine a special classification and salary, with the hope of providing an opportunity for continued employment. Positions established under this article will not constitute new classifications and shall lapse upon the termination, resignation, or retirement of the employee in question. (c) Prior to any disabled employee returning to work from a disability including WSIB to a modified/light/alternate work program, the Employer will notify and meet with members of the bargaining unit executive to consult on a back to work program for the worker. Any agreement resulting from these discussions which conflicts with the collective agreement shall, subject to agreement by the Union, prevail over any provision of this agreement in the event of a conflict. Nothing in this language obligates the Employer to establish a modified/ light/alternative work program, except as required by law.

  • Acceptance of the Work 19.1 The Contractor shall correct any Work that fails to conform to the requirements of the Contract Documents where such failure to conform appears during the progress of the Work, and shall remedy any defects due to faulty permitting, design, materials, equipment or workmanship which appear within a period of one year from the Date of Final Settlement of the Contract or within such longer period of time as may be prescribed by law or by the terms of any applicable special guarantee required by the Contract Documents. The provisions of this Article apply to Work done by Subcontractors as well as to Work done by direct employees of the Contractor, and are in addition to any other remedies or warranties provided by law. 19.2 No act of, or failure to act by, the Owner or the Owner's Representative, either in superintending or directing the Work, or any extension of time for the completion of the Work, shall be regarded as an acceptance of such Work or any part thereof, or of materials used therein, either wholly or in part. Acceptance shall be evidenced only by the final certificate of the Owner. Before any final certificate shall issue, Contractor shall execute an affidavit on the certificate that it accepts the same in full payment and settlement of all claims on account of Work done and materials furnished under this Contract, and that all claims for materials provided or labor performed have been paid or set aside in full. No waiver of any breach of this Contract by the Owner or anyone acting on Owner's behalf shall be held as a waiver of any other subsequent breach thereof. 19.3 Contractor agrees to guarantee all work under this Contract for the periods specified in the RFP from the date of Final Settlement by the Owner. If any unsatisfactory condition or damage develops within the time of this guaranty due to permitting, design, materials or workmanship that are defective, inferior, or not in accordance with the Contract, as reasonably determined by the Owner or the Owner’s Representative, then the Contractor shall, when notified by the Owner or OR, immediately place such guaranteed Work in a condition satisfactory to the Owner or OR.

  • Additional Termination Provisions Notwithstanding and in addition to the foregoing, in the event that (i) a Mortgage Loan becomes delinquent for a period of 90 days or more (a "Delinquent Mortgage Loan") or (ii) a Mortgage Loan becomes an REO Property, the Purchaser may at its election terminate this Agreement with respect to such Delinquent Mortgage Loan or REO Property, upon 15 days' written notice to the Seller.