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
AutoNDA by SimpleDocs
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 Xxxxx 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

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 xxxx XXXX 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.

  • Shared Contracts (a) Except as set forth on Schedule VIII, the Parties shall, and shall cause the members of their respective Groups to, use their respective reasonable best efforts to work together (and, if necessary and desirable, to work with the third party to such Shared Contract) in an effort to divide, partially assign, modify or replicate (in whole or in part) the respective rights and obligations under and in respect of any Shared Contract, such that (a) a member of the SpinCo Group is the beneficiary of the rights and is responsible for the obligations related to that portion of such Shared Contract relating to the SpinCo Business (the “SpinCo Portion”), which rights shall be a SpinCo Asset and which obligations shall be a SpinCo Liability, and (b) a member of the Nuance Group is the beneficiary of the rights and is responsible for the obligations related to such Shared Contract not relating to the SpinCo Business (the “Nuance Portion”), which rights shall be a Nuance Asset and which obligations shall be a Nuance Liability. Nothing in this Agreement shall require the division, partial assignment, modification or replication of a Shared Contract unless and until any necessary Consents are obtained or made, as applicable. If the Parties, or their respective Group members, as applicable, are not able to enter into an arrangement to formally divide, partially assign, modify or replicate such Shared Contract prior to the Distribution as contemplated by the previous sentence, then the Parties shall, and shall cause their respective Group members to, cooperate in any reasonable and permissible arrangement to provide that, following the Distribution, a member of the SpinCo Group shall receive the interest in the benefits and obligations of the SpinCo Portion under such Shared Contract and a member of the Nuance Group shall receive the interest in the benefits and obligations of the Nuance Portion under such Shared Contract, it being understood that no Party shall have Liability to the other Party for the failure of any third party to perform its obligations under any such Shared Contract.

  • 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.

  • Shared Personal Data This clause sets out the framework for the sharing of personal data between the parties as data controllers. Each party acknowledges that one party (the Data Discloser) will regularly disclose to the other party (the Data Recipient) Shared Personal Data collected by the Data Discloser for the Agreed Purposes.

  • Shared Use During the time that non- expendable personal property is held for use on the project or program for which it was acquired, the Grantee shall make it avail- able for use on other projects or programs if such other use will not interfere with the work on the project or program for which the property was originally acquired. First preference for such other use shall be given to other projects or programs sponsored by FmHA or its successor agency under Public Law 103–354; second preference shall be given to projects or programs sponsored by other Federal agencies. If the property is owned by the Federal Government, use on other activi- ties not sponsored by the Federal Govern- ment shall be permissible if authorized by FmHA or its successor agency under Public Law 103–354. User charges should be consid- ered if appropriate.

  • Shared Facilities The Parties acknowledge and agree that certain of the Shared Facilities and Interconnection Facilities, and Seller’s rights and obligations under the Interconnection Agreement, may be subject to certain shared facilities or co-tenancy agreements to be entered into among Seller, the Participating Transmission Owner, Seller’s Affiliates, or third parties pursuant to which certain Interconnection Facilities may be subject to joint ownership and shared maintenance and operation arrangements; provided that such agreements (i) shall permit Seller to perform or satisfy, and shall not purport to limit, its obligations hereunder and (ii) provide for separate metering of the Facility.

  • Shared Services 5.1.1 ETFO agrees to adopt a shared services model that will allow other Trusts to join the shared services model. The shared services office of the Trust is responsible for the services to support the administration of benefits for the members, and to assist in the delivery of benefits on a sustainable, efficient and cost effective basis.

  • Shared Loss Arrangement 1 2.1 Accounting for and Management of Shared-Loss Assets 1

  • SINGLE FAMILY SHARED-LOSS AGREEMENT This agreement for the reimbursement of loss sharing on certain single family residential mortgage loans (the “Single Family Shared-Loss Agreement”) shall apply when the Assuming Institution purchases Single Family Shared-Loss Loans as that term is defined herein. The terms hereof shall modify and supplement, as necessary, the terms of the Purchase and Assumption Agreement to which this Single Family Shared-Loss Agreement is attached as Exhibit 4.15A and incorporated therein. To the extent any inconsistencies may arise between the terms of the Purchase and Assumption Agreement and this Single Family Shared-Loss Agreement with respect to the subject matter of this Single Family Shared-Loss Agreement, the terms of this Single Family Shared-Loss Agreement shall control. References in this Single Family Shared- Loss Agreement to a particular Section shall be deemed to refer to a Section in this Single Family Shared-Loss Agreement, unless the context indicates that it is intended to be a reference to a Section of the Purchase and Assumption Agreement.

Time is Money Join Law Insider Premium to draft better contracts faster.