Non-Malleable Sample Clauses

Non-Malleable. Compact, Multi-Party Range Proofs from Bulletproofs‌ We propose a Logarithmic-sized, Non-Malleable, Non-Interactive, Multi-Party Bulletproof Range Proof scheme with an updated version of improved inner product argument. The improved inner product argument [38, 50] can securely convince a verifer given (h, g, P = hl · gr, πIP) that the prover knows (l, r). The fascinating property of IP is it compresses 2|l| elements of (l, r) to πIP which only has two Zp components and 2 log2 |l| G components (prefer [72] for additional details). The proposed Non-Malleable MBP only uses strong Fiat Shamir challenges derived from a hash function giving the commitment as an input. The strong Fiat Shamir challenges guarantee non-malleability of RP and IP, making unique challenges for the particular commitment. Here, ki is the partial key belong the ith party and v is the coin amount of asset Cv,Σ k. MBP allows n parties to generate range proofs for coin amounts in range [0, 2l − 1] without sharing their partial keys with the combiner (prefer [50] for notations. However, we interchange variable symbols g with h and h with g). RP.Set(λ): return pp = (G, g, h, g, h, u, p) // when a group G = ⟨g⟩, ⟨h⟩, ⟨u⟩ of prime order p ∈ {0, 1}λ and g, h, and u are DL problem hard (NUMS points). g and h are generator vectors of G where |g| = |h| = l and Vpp = [0, 2l − 1]. RP.Prv(pp, C = Cv,Σ k, v, k, n): if n = empty : n := |k| // The combiner (the dealer) starts the function. aL ∈ {0, 1}l : ⟨aL, 2l⟩ = v, aR := aL − 1l $ $ sL, sR ←− Zl , (α, ρ) ←− Zp, A ← gαhaL gaR , S ← gρhsL gsR y ← H(C, A, S), z ← H(C, A, S, y) L(X) := (aL − z · 1l) + sL · X, R(X) := yl · (aR + z · 1l + sR · X) + z2 · 2l t(X) := ⟨L(X), R(X)⟩ = t0 + t1 · X + t2 · X2 gt1 = {}, gt2 = {} for i ∈ [1, n] do // The combiner requests gτ1,i, gτ2,i from each co-prover i. τ1,i , τ2,i ←− Z2 // Each co-prover i shares gτ1,i, gτ2,i with the combiner j. $

Related to Non-Malleable

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

  • NON-SMOKING UNIT ENTRY BY OWNER

  • Tandem Transit Traffic ‌ 12.1 As used in this Section, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on Onvoy's network, and is transported through Frontier’s Tandem to the subtending End Office or its equivalent of another carrier (CLEC, ILEC other than Frontier, Commercial Mobile Radio Service (CMRS) carrier, or other LEC (“Other Carrier”). Neither the originating nor terminating customer is a Customer of Frontier. Subtending End Offices shall be determined in accordance with and as identified in the Local Exchange Routing Guide (LERG). For the avoidance of any doubt, under no circumstances shall Frontier be required to transit traffic through a Frontier Tandem to a Central Office that the LERG does not identify as subtending that particular Frontier Tandem. Switched Exchange Access Service traffic is not Tandem Transit Traffic. 12.2 Tandem Transit Traffic Service provides Onvoy with the transport of Tandem Transit Traffic as provided below. 12.3 Tandem Transit Traffic may be routed over the Interconnection Trunks described in Sections 2 through 6 of this Attachment. Onvoy shall deliver each Tandem Transit Traffic call to Frontier’s Tandem with CCS and the appropriate Transactional Capabilities Application Part (“TCAP”) message to facilitate full interoperability of CLASS Features and billing functions. 12.4 Onvoy may use Tandem Transit Traffic Service only for traffic that originates on Onvoy’s network and only to send traffic to an Other Carrier with whom Onvoy has a reciprocal traffic exchange arrangement (either via written agreement or mutual tariffs) that provides for the Other Carrier, to terminate or complete traffic originated by Onvoy and to bill Onvoy, and not to bill Frontier, for such traffic. Onvoy agrees not to use Frontier’s Tandem Transit Traffic Service to send traffic to an Other Carrier with whom Onvoy does not have such a reciprocal traffic exchange arrangement or to send traffic that does not originate on Onvoy’s network. 12.5 Onvoy shall pay Frontier for Tandem Transit Traffic Service at the rates specified in the Pricing Attachment. Frontier will not be liable for compensation to any Other Carrier for any traffic that is transported through Frontier’s Tandem and Frontier reserves the right to assess to Onvoy any additional charges or costs any Other Carrier imposes or levies on Frontier for the delivery or termination of such traffic, including any Switched Exchange Access Service charges. If Frontier is billed by any Other Carrier for any traffic originated by Onvoy, Frontier may provide notice to Onvoy of such billing. Upon receipt of such notice, Onvoy shall immediately stop using Frontier’s Tandem Transit Traffic Service to send any traffic to such Other Carrier until it has provided to Frontier certification that the Other Carrier has removed such billed charges from its bill to Frontier and that the Other Carrier will not bill Frontier for any traffic originated by Onvoy. Such certification must be signed by an authorized officer or agent of the Other Carrier and must be in a form acceptable to Frontier. 12.6 If Onvoy uses Tandem Transit Traffic Service for traffic volumes that exceed the Centum Call Seconds (Hundred Call Seconds) busy hour equivalent of 200,000 combined minutes of use per month (a DS1 equivalent) to the subtending End Office of a particular Other Carrier for any month (the “Threshold Level”). Onvoy shall use good faith efforts to establish direct interconnection with such Other Carrier and reduce such traffic volumes below the Threshold Level. If Frontier believes that Xxxxx has not exercised good faith efforts promptly to obtain such direct interconnection, either Party may use the Dispute Resolution processes of this Agreement. 12.7 If Onvoy fails to comply with Section 12 of this Attachment, such failure shall be a material breach of a material provision of this Agreement and Frontier may exercise any and all remedies under this Agreement and Applicable Law for such breach. 12.8 If or when a third party carrier plans to subtend an Onvoy switch, then Onvoy shall provide written notice to Frontier at least ninety (90) days before such subtending service arrangement becomes effective so that Frontier may negotiate and establish direct interconnection with such third party carrier. Upon written request from Frontier, Onvoy shall offer to Frontier a service arrangement equivalent to or the same as Tandem Transit Traffic Service provided by Frontier to Onvoy as defined in this Section such that Frontier may terminate calls to a Central Office or its equivalent of a CLEC, ILEC other than Frontier, CMRS carrier, or other LEC, that subtends an Onvoy Central Office or its equivalent (“Reciprocal Tandem Transit Service”). Onvoy shall offer such Reciprocal Transit Service arrangements under terms and conditions of an amendment to this Agreement or a separate agreement no less favorable than those provided in this Section. 12.9 Neither Party shall take any actions to prevent the other Party from entering into a direct and reciprocal traffic exchange arrangement with any carrier to which it originates, or from which it terminates, traffic.

  • DATABASE OF RESTRICTED SUPPLIER The process of restriction is used to exclude a company/person from conducting future business with Transnet and other organs of state for a specified period. No Bid shall be awarded to a Bidder whose name (or any of its members, directors, partners or trustees) appear on the Register of Tender Defaulters kept by National Treasury, or who have been placed on National Treasury’s List of Restricted Suppliers. Transnet reserves the right to withdraw an award, or cancel a contract concluded with a Bidder should it be established, at any time, that a bidder has been restricted with National Treasury by another government institution.

  • SPECIALIZED JOB CLASSES Where there is a particular specialized job class in which the pay rate is below the local market value assessment of that job class, the parties may use existing means under the collective agreement to adjust compensation for that job class.

  • Limitation on Preferred Stock of Restricted Subsidiaries The Company will not permit any of its Restricted Subsidiaries to issue any Preferred Stock (other than to the Company or to a Wholly Owned Restricted Subsidiary of the Company) or permit any Person (other than the Company or a Wholly Owned Restricted Subsidiary of the Company) to own any Preferred Stock of any Restricted Subsidiary of the Company.

  • Wire Unbundled DS1 Digital Loop This is a designed 4-wire Loop that is provisioned according to industry standards for DS1 or Primary Rate ISDN services and will come standard with a test point, OC, and a DLR. A DS1 Loop may be provisioned over a variety of loop transmission technologies including copper, HDSL-based technology or fiber optic transport systems. It will include a 4-Wire DS1 Network Interface at the End User’s location.

  • Interest Unpaid Class Accrued Certificate Interest Shortfalls Interest Class Interest Payable Pay-out Rate ----- -------- ------------------- ------- ------------ R $ 0.00 $ 0.00 $ 0.00 %0.000000000 PO $ 0.00 $ 0.00 $ 0.00 %0.000000000 A1 $ 153,408.89 $ 0.00 $ 153,408.89 %5.950000013 A2 $ 228,536.00 $ 0.00 $ 228,536.00 %6.000000000 A3 $ 892,574.07 $ 0.00 $ 892,574.07 %6.249999980 A4 $ 188,303.45 $ 0.00 $ 188,303.45 %5.463749883 A5 $ 104,641.75 $ 0.00 $ 104,641.75 %3.036249996 A6 $ 1,265,469.75 $ 0.00 $ 1,265,469.75 %6.500000012 A7 $ 807,304.70 $ 0.00 $ 807,304.70 %6.500000035 A8 $ 288,597.53 $ 0.00 $ 288,597.53 %6.500000029 A9 $ 5,475.51 $ 0.00 $ 0.00 %6.500004595 A10 $ 102,533.15 $ 0.00 $ 102,533.15 %6.500000317 A11 $ 36,259.17 $ 0.00 $ 36,259.17 %6.500000598 A12 $ 8,706.67 $ 0.00 $ 8,706.67 %8.000003063 A13 $ 97,830.41 $ 0.00 $ 97,830.41 %5.663749756 A14 $ 48,990.77 $ 0.00 $ 48,990.77 %9.217811872 A15 $ 0.00 $ 0.00 $ 0.00 %0.000000000 A16 $ 8,205.08 $ 0.00 $ 0.00 %6.499997726 A17 $ 27,377.53 $ 0.00 $ 0.00 %6.499999821 A18 $ 31,669.04 $ 0.00 $ 31,669.04 %6.749999467 A19 $ 32,841.97 $ 0.00 $ 32,841.97 %7.000000000 A20 $ 0.00 $ 0.00 $ 0.00 %0.000000000 A21 $ 11,860.87 $ 0.00 $ 0.00 %6.499999338 A22 $ 515,883.47 $ 0.00 $ 515,883.47 %6.500000016 S $ 336,620.40 $ 0.00 $ 336,620.40 %0.454839554 RL $ 0.00 $ 0.00 $ 0.00 %0.000000000 M $ 95,282.60 $ 0.00 $ 95,282.60 %6.500000161 B1 $ 38,626.76 $ 0.00 $ 38,626.76 %6.499999201 B2 $ 23,177.14 $ 0.00 $ 23,177.14 %6.499999887 B3 $ 25,751.18 $ 0.00 $ 25,751.18 %6.500000875 B4 $ 10,301.55 $ 0.00 $ 10,301.55 %6.499998651 B5 $ 12,875.59 $ 0.00 $ 12,875.59 %6.499998605

  • Abnormally High Tenders 36.4 An abnormally high price is one where the tender price, in combination with other constituent elements of the Tender, appears unreasonably too high to the extent that the Procuring Entity is concerned that it (the Procuring Entity) may not be getting value for money or it may be paying too high a price for the contract compared with market prices or that genuine competition between Tenderers is compromised. 36.5 In case of an abnormally high tender price, the Procuring Entity shall make a survey of the market prices, check if the estimated cost of the contract is correct and review the Tender Documents to check if the specifications, scope of work and conditions of contract are contributory to the abnormally high tenders. The Procuring Entity may also seek written clarification from the tenderer on the reason for the high tender price. The Procuring Entity shall proceed as follows: i) If the tender price is abnormally high based on wrong estimated cost of the contract, the Procuring Entity may accept or not accept the tender depending on the Procuring Entity's budget considerations. ii) If specifications, scope of work and/or conditions of contract are contributory to the abnormally high tender prices, the Procuring Entity shall reject all tenders and may retender for the contract based on revised estimates, specifications, scope of work and conditions of contract, as the case may be. 36.6 If the Procuring Entity determines that the Tender Price is abnormally too high because genuine competition between tenderers is compromised (often due to collusion, corruption or other manipulations), the Procuring Entity shall reject all Tenders and shall institute or cause relevant Government Agencies to institute an investigation on the cause of the compromise, before retendering.

  • Permitted License Uses and Restrictions (a) This Order Form Supplement allows you, as an authorized User under the Master Subscription Agreement, to use the Software on any Supported Device and on no other devices. (b) You may not distribute or make the Software available over a network where it could be used by multiple devices at the same time. (c) With respect to updates to the Software that xxxxxxxxxx.xxx may make available for download, this Order Form Supplement allows you to download such Software updates to update or restore the Software on any Supported Device. (d) Except as and only to the extent permitted by applicable law, or by licensing terms governing use of open-sourced components included with the Software, neither you nor any other Customer personnel may copy, decompile, reverse engineer, disassemble, attempt to derive the source code of, decrypt, modify, or create derivative works of the Software or Software updates, or any part thereof. Any attempt to do so is a violation of the rights of xxxxxxxxxx.xxx and its licensors. If you or any other Customer personnel violate this restriction, you or they, and the Customer, may be subject to prosecution and damages. (e) Neither you nor the Customer may rent, lease, lend, redistribute or sublicense the Software. The Customer may, however, allow other authorized Users under the Master Subscription Agreement to use the Software in connection with a re-assignment of the Supported Device to another authorized User under the Master Subscription Agreement. (f) The Software is available only for Supported Devices, and is not available for all devices. Please check xxx.xxxxxxxxxx.xxx or contact your xxxxxxxxxx.xxx representative to determine whether a specific device-iOS software combination is supported by the Software. (g) In addition to mobile applications offered by xxxxxxxxxx.xxx (and for purposes of this section 5(g), “xxxxxxxxxx.xxx” shall include any Affiliates of xxxxxxxxxx.xxx), xxxxxxxxxx.xxx may offer platforms for the creation of third-party mobile applications, including but not limited to the Salesforce1 platform. Third parties may obtain information from, or access data stored on, Users’ mobile devices to provide services associated with any third-party mobile applications that Users download, install, use, or otherwise interact with over a xxxxxxxxxx.xxx platform. Xxxxxxxxxx.xxx’s mobile applications may also contain links or integrations to other mobile applications provided by third parties. Xxxxxxxxxx.xxx is not responsible for the security and privacy of data collected through third-party mobile applications or the privacy and security practices of the foregoing third parties. (h) Without limiting the generality of anything herein, you acknowledge and agree that the Software may collect user or device data for the purposes of providing services or functions that are relevant to use of the Software.