Shared Coin Sample Clauses

Shared Coin. Algorithm 2.22 Shared Coin (code for node u) 1: Choose local coin cu = 0 with probability 1/n, else cu = 1
Shared Coin. ‌ ∈ We describe here an asynchronous protocol for a shared coin with a constant success rate against the delayed-adaptive adversary. We assume that for every r N, shared_coin(r) is invoked by all correct processes and that the invocation of shared_coin(r) by some process p is causally independent of its progress at other processes. The definition of a shared coin is given below. ► Definition 2 (Shared Coin). A shared coin with success rate ρ is a shared object that gener- ates an infinite sequence of binary outputs. For each execution of the procedure shared_coin(r) with r ∈ N, all correct processes output b with probability at least ρ, for any value b ∈ {0, 1}. The pseudo-code for our shared coin is presented in Algorithm 1. Our protocol is composed of two phases of messages passing. Each process first samples the VRF with its private key and the protocol’s argument in order to generate a random initial value. For brevity, we denote by V RFi the VRF with pi’s private key. Using a VRF to generate a random initial value effectively weakens the adversary as Byzantine processes can neither choose their initial values nor equivocate. If a Byzantine process would try to act maliciously, the VRF proof would easily expose it and its message would be ignored. In each phase of the protocol, each process sends one value to every other process. The receiver validates the received values using the VRF proofs, which are sent along with the values. We omit the proof validation from the code for clarity. After two phases of communication, each process chooses the minimum value it received in the second phase and outputs its least significant bit. We follow the concept of a common core, as presented by Attiya and ▇▇▇▇▇ for the crash failure model [6], and argue that if a core of f + 1 correct processes hold the global minimum value at the end of phase 1, then by the end of the following phase all processes receive this value. We exploit the s parameter in our resilience definition to bound the number of values held by f + 1 correct processes. We show that this number is linear in n and hence with a constant positive probability, by the end of the second phase, all correct processes receive the global minimum among the VRF outputs and therefore produce the same output. Algorithm 1 Protocol shared_coin(r): code for process pi 1: Initially first-set, second-set = ∅ 2: vi ← VRFi(r) 3: send (first, vi) to all processes

Related to Shared Coin

  • Shared Costs (i) If the Parties elect to establish two-way Local Interconnection Trunks for reciprocal exchange of traffic, the cost of the two-way Local Interconnection Entrance Facility and DTT shall be shared among the Parties. CenturyLink will ▇▇▇▇ ▇▇▇▇ for the entire DTT and Local Interconnection Entrance Facility provided by CenturyLink at the rates in Table 1. CLEC will bill CenturyLink for CenturyLink’s portion of the same DTT and Local Interconnection Entrance Facility at the same recurring rates in Table 1 charged by CenturyLink based on the portion defined in (ii) below. (ii) CenturyLink’s portion of the DTT and Local Interconnection Entrance Facility will be based on the factor determined by CenturyLink using the following to assign the minutes for which CenturyLink is responsible: • All Local Traffic MOU that CenturyLink originates and sends to CLEC. • All CenturyLink originated IntraLATA LEC Toll MOU that CenturyLink sends to CLEC. • All other minutes are CLEC’s responsibility for purposes of allocating the shared costs.

  • Shared Contracts (a) With respect to Shared Contractual Liabilities pursuant to, under or relating to a given Shared Contract, such Shared Contractual Liabilities shall be allocated, unless otherwise allocated pursuant to this Agreement or an Ancillary Agreement, between the Parties as follows: (i) first, if a Liability is incurred exclusively in respect of a benefit received by one Party or its Group, the Party or Group receiving such benefit shall be responsible for such Liability; (ii) second, if a Liability cannot be exclusively allocated to one Party or its Group under clause (i) above, such Liability shall be allocated among both Parties and their respective Groups based on the relative proportions of total benefit received (over the term of the Shared Contract, measured as of the date of allocation) under the relevant Shared Contract. Notwithstanding the foregoing, each Party and its Group shall be responsible for any or all Liabilities arising out of or resulting from such Party’s or Group’s breach of the relevant Shared Contract. (b) Except as otherwise expressly contemplated in this Agreement or an Ancillary Agreement, if Dover or any member of the Dover Group, on the one hand, or Apergy or any member of the Apergy Group, on the other hand, receives any benefit or payment under any Shared Contract which was intended for the other Party or its Group, Dover, on the one hand, or Apergy, on the other hand, will use its respective commercially reasonable efforts, or will cause any member of its Group to use its commercially reasonable efforts, to deliver, transfer or otherwise afford such benefit or payment to the other Party. (c) Notwithstanding anything to the contrary herein, the Parties have determined that it is advisable that certain Shared Contracts, or portions thereof, will be separated or assigned to a member of the Dover Group or Apergy Group, as applicable. The Parties shall use their commercially reasonable efforts to separate the Shared Contracts which are identified on Schedule 2.9(c)(i) into separate Contracts between the appropriate Third Party and either Apergy or a member of the Apergy Group or Dover or a member of the Dover Group. Dover or a member of the Dover Group will use commercially reasonable efforts to assign the rights and obligations, but only to the extent relating to the Apergy Business, under the Shared Contracts which are identified on Schedule 2.9(c)(ii) to Apergy or a member of the Apergy Group. The Parties agree to cooperate and provide reasonable assistance prior to the Effective Time and for a period of six months following the Effective Time (with no obligation on the part of either Party to pay any costs or fees with respect to such assistance) in effecting the separation or assignment of such Shared Contracts as described above.

  • Treatment of Shared Contracts (a) Subject to applicable Law and without limiting the generality of the obligations set forth in Section 2.1, unless the Parties otherwise agree or the benefits of any contract, agreement, arrangement, commitment or understanding described in this Section 2.8 are expressly conveyed to the applicable Party pursuant to this Agreement or an Ancillary Agreement, any contract or agreement, a portion of which is a Varex Contract, but the remainder of which is a Parent Asset (any such contract or agreement, a “Shared Contract”), shall be assigned in relevant part to the applicable member(s) of the applicable Group, if so assignable, or appropriately amended prior to, on or after the Effective Time, so that each Party or the member of its Group shall, as of the Effective Time, be entitled to the rights and benefits, and shall assume the related portion of any Liabilities, inuring to its respective businesses; provided, however, that (i) in no event shall any member of any Group be required to assign (or amend) any Shared Contract in its entirety or to assign a portion of any Shared Contract which is not assignable (or cannot be amended) by its terms (including any terms imposing consents or conditions on an assignment where such consents or conditions have not been obtained or fulfilled) and (ii) if any Shared Contract cannot be so partially assigned by its terms or otherwise, or cannot be amended or if such assignment or amendment would impair the benefit the parties thereto derive from such Shared Contract, then the Parties shall, and shall cause each of the members of their respective Groups to, take such other reasonable and permissible actions (including by providing prompt notice to the other Party with respect to any relevant claim of Liability or other relevant matters arising in connection with a Shared Contract so as to allow such other Party the ability to exercise any applicable rights under such Shared Contract) to cause a member of the Varex Group or the Parent Group, as the case may be, to receive the rights and benefits of that portion of each Shared Contract that relates to the Varex Business or the Parent Business, as the case may be (in each case, to the extent so related), as if such Shared Contract had been assigned to a member of the applicable Group (or amended to allow a member of the applicable Group to exercise applicable rights under such Shared Contract) pursuant to this Section 2.8, and to bear the burden of the corresponding Liabilities (including any Liabilities that may arise by reason of such arrangement), as if such Liabilities had been assumed by a member of the applicable Group pursuant to this Section 2.8. (b) Each of Parent and Varex shall, and shall cause the members of its Group to, (i) treat for all Tax purposes the portion of each Shared Contract inuring to its respective businesses as an Asset owned by, and/or a Liability of, as applicable, such Party, or the members of its Group, as applicable, not later than the Effective Time, and (ii) neither report nor take any Tax position (on a Tax Return or otherwise) inconsistent with such treatment (unless required by applicable Law). (c) Nothing in this Section 2.8 shall require any member of any Group to make any non-de minimis payment (except to the extent advanced, assumed or agreed in advance to be reimbursed by any member of the other Group), incur any non-de minimis obligation or grant any non-de minimis concession for the benefit of any member of any other Group in order to effect any transaction contemplated by this Section 2.8.

  • Shared roles The Parties will meet the requirements of Schedule E, Clause 26 of the IGA FFR, by ensuring that prior agreement is reached on the nature and content of any events, announcements, promotional material or publicity relating to activities under this Agreement, and that the roles of both Parties will be acknowledged and recognised appropriately.

  • Shared Transport The Shared Transport Network Element (“Shared Transport”) provides the collective interoffice transmission facilities shared by various Carriers (including Qwest) between end-office switches and between end-office switches and local tandem switches within the Local Calling Area. Shared Transport uses the existing routing tables resident in Qwest switches to carry the End User Customer’s originating and terminating local/extended area service interoffice Local traffic on the Qwest interoffice message trunk network. CLEC traffic will be carried on the same transmission facilities between end- office switches, between end-office switches and tandem switches and between tandem switches on the same network facilities that Qwest uses for its own traffic. Shared Transport does not include use of tandem switches or transport between tandem switches and end-office switches for Local Calls that originate from end users served by non- Qwest Telecommunications Carriers (“Carrier(s)”) which terminate to QLSP End Users.