We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

An MPC Protocol Sample Clauses

An MPC Protocol. Let t = κ(1 − s)/3. The protocol uses the following setup: • A randomly chosen committee C, where each party is chosen with probability κ/n. • A threshold fully-homomorphic encryption scheme TFHE = (KGen, Enc, Dec, Eval) [22] (de- fined in Appendix B.2) with threshold t. The public key is ek and the secret key dk = (dk1, . . . , dk|C|), where each party in C holds a secret key share, and all parties know ek and |C|. Each party in C also has a setup as sender for an instance of the protocol ΠRBC, whereas all other parties have a recipient-setup. • A common reference string CRS used for universally composable non-interactive zero-knowledge proofs [18]. Fix a (possibly randomized) functionality g the parties wish to compute. We assume without loss of generality that g uses exactly κ random bits (one can always use a PRG to ensure this). Very roughly, the protocol asks each party Pi to encrypt its input ci = Encek(xi) and execute the VACS protocol. The VACS allows parties to agree on a common subset of input providers. After that, parties homomorphically evaluate the function over the encrypted inputs to obtain an encrypted output. Finally, parties in C jointly decrypt the output. We deal with adaptive security by using secure-erasures: Parties will erase the relevant in- formation prior to sending the messages in each of the steps, avoiding in this way the so-called commitment problem (and also avoiding the need for an equivocal FHE scheme [16]), where the simulator needs to explain previously sent messages in a consistent manner. In the protocol, parties prove (in zero-knowledge) the correctness of values sent during the protocol execution. For this purpose we use universally composable non-interactive zero-knowledge (NIZK) proofs [18] based on a common reference string (CRS) provided by the dealer. We are interested in NIZK proofs for two relations, parameterized by a threshold FHE scheme with public encryption key ek:
Sample 1

Related to An MPC Protocol

  • Signaling protocol 4.1.3.1 SS7 Signaling is AT&T-21STATE’s preferred method for signaling. Where MF signaling is currently used, the Parties agree to use their best efforts to convert to SS7. If SS7 services are provided by AT&T-21STATE, they will be provided in accordance with the provisions of the applicable access tariffs. 4.1.3.2 Where MF signaling is currently used, the Parties agree to interconnect their networks using MF or dual tone MF (DTMF) signaling, subject to availability at the End Office Switch or Tandem Switch at which Interconnection occurs. The Parties acknowledge that the use of MF signaling may not be optimal. AT&T-21STATE will not be responsible for correcting any undesirable characteristics, service problems or performance problems that are associated with MF/SS7 inter-working or the signaling protocol required for Interconnection with CLEC employing MF signaling.

  • Protocol No action to coerce or censor or penalize any negotiation participant shall be made or implied by any other member as a result of participation in the negotiation process.

  • Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.

  • Random Drug Testing All employees covered by this Agreement shall be subject to random drug testing in accordance with Appendix D.

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Cooperative Master Contract Sales Reporting. Contractor shall report total Cooperative Master Contract sales quarterly to Enterprise Services, as set forth below. Cooperative Master Contract Sales Reporting System. Contractor shall report quarterly Cooperative Master Contract sales in Enterprise Services’ Cooperative Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized Purchasers specified herein during the term of the Cooperative Master Contract. If there are no Cooperative Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Cooperative Master Contract Sales Reporting. Quarterly Cooperative Master Contract Sales Reports must be submitted electronically by the following deadlines for all Cooperative Master Contract sales invoiced during the applicable calendar quarter: Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 1.5 percent on the purchase price for all Cooperative Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Cooperative Master Contract sales invoiced (not including sales tax) x .015. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Cooperative Master Contract sales reported by Contractor. Contractor is not to remit payment until Contractor receives an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Cooperative Master Contract number, the year and quarter for which the VMF is being remitted, and Contractor’s name as set forth in this Cooperative Master Contract, if not already included on the face of the check. Contractor’s failure to report accurate total net Cooperative Master Contract sales, to submit a timely Cooperative Master Contract sales report, or to remit timely payment of the VMF to Enterprise Services, may be cause for Enterprise Services to suspend Contractor or terminate this Cooperative Master Contract or exercise remedies provided by law. Without limiting any other available remedies, the parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums, the sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) calendar days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Cooperative Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing. Annual Cooperative Master Contract Sales Report. Contractor shall provide to Enterprise Services a detailed annual Cooperative Master Contract sales report. Such report shall include, at a minimum: the Goods/Services sold (including, as applicable, item number or other identifier), per unit quantities sold, items and volumes purchased by Purchaser, shipment/delivery locations by Purchaser, and Cooperative Master Contract price. This report must be provided in an electronic format that can be read by Microsoft (MS) Excel. Such report is due within thirty (30) calendar days of the annual anniversary of the effective date of this Cooperative Master Contract.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Prescription Drug Plan Retail and mail order prescription drug copays for bargaining unit employees shall be as follows:

  • Power Factor Design Criteria Developer shall design the Large Generating Facility to maintain an effective power delivery at demonstrated maximum net capability at the Point of Interconnection at a power factor within the range established by the Connecting Transmission Owner on a comparable basis, until NYISO has established different requirements that apply to all generators in the New York Control Area on a comparable basis. The Developer shall design and maintain the plant auxiliary systems to operate safely throughout the entire real and reactive power design range. The Connecting Transmission Owner shall not unreasonably restrict or condition the reactive power production or absorption of the Large Generating Facility in accordance with Good Utility Practice.

  • Disaster Recovery Plan Contractor agrees that upon request of System Agency, Contractor shall provide copies of its most recent business continuity and disaster recovery plans.

  • Protocols Each party hereby agrees that the inclusion of additional protocols may be required to make this Agreement specific. All such protocols shall be negotiated, determined and agreed upon by both parties hereto.

Most Referenced Clauses

Most Referenced Definitions