Distributed Ledger Technology Risks Sample Clauses

Distributed Ledger Technology Risks. Distributed ledger technology (also referred to throughout the Terms as “blockchain”) may be an independent public peer-to peer network and not controlled in any way or manner by us and, as such, we shall not be responsible for any failure, mistake, error or breach which shall occur on the blockchain or in any other networks on which the Virtual Assets are being issued or otherwise traded. You will be bound and subject to any change or amendments in the blockchain system and subject to any applicable law which may apply to the blockchain. We make no representation or warranty of any kind, express or implied, statutory or otherwise, regarding the blockchain functionality nor for any breach of security in the blockchain.
AutoNDA by SimpleDocs

Related to Distributed Ledger Technology Risks

  • Joint Intellectual Property 9.1 University agrees to not Implement any Joint Intellectual Property for any purpose other than educational, experimental or research purposes. In consideration of University not Implementing the Joint Intellectual Property except for the limited purposes set forth in this paragraph, Company agrees to Implement any Joint Intellectual Property only in accordance with a license agreement to be entered into by Company and University with respect to the Implementation of such Joint Intellectual Property. Company shall pay to University, in connection with such Implementation, a compensatory royalty in accordance with such license agreement to be agreed by the Parties.

  • Licensed Technology The term “Licensed Technology” shall mean the Licensed Patent Rights, Licensed Know-How and Licensed Biological Materials.

  • SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.

  • Third Party Technology Customer is hereby notified that third parties have licensed certain technology to Company, which is contained in the Software. Notwithstanding anything herein to the contrary, Customer hereby consents to the disclosure of Customer’s identity, and such other terms of this Agreement as necessary, to such third party licensors for the purpose of enabling Company to comply with the terms and conditions of such third party licenses. Any such Customer information will be provided pursuant to an obligation of confidentiality and nondisclosure at least as stringent as that imposed by this Agreement.

  • Background Technology List here prior contracts to assign Inventions that are now in existence between any other person or entity and you. [ ] List here previous Inventions which you desire to have specifically excluded from the operation of this Agreement. Continue on reverse side if necessary.

  • Licensed Products Lessee will obtain no title to Licensed Products which will at all times remain the property of the owner of the Licensed Products. A license from the owner may be required and it is Lessee's responsibility to obtain any required license before the use of the Licensed Products. Lessee agrees to treat the Licensed Products as confidential information of the owner, to observe all copyright restrictions, and not to reproduce or sell the Licensed Products.

  • New Technology When new or updated technology is introduced into a workplace, it will be the responsibility of the employer to provide appropriate and, if necessary, ongoing training to the employees directly affected. Such training will include any health and safety implications or information that will enable employees to operate the equipment without discomfort and will help maintain their general well-being.

  • Specially Created Intellectual Property Rights 27.1. All Intellectual Property Rights in Deliverables and and any reports, guidance, specification, instructions, toolkits, plans, data, drawings, databases, patents, patterns, models, designs or other material prepared by or for the Contractor on behalf of the Authority for use, or intended use, in relation to the performance by the Contractor of its obligations under the Framework Agreement belong to the Authority.

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

  • Unbundled Copper Loop – Designed (UCL-D) 2.4.2.1 The UCL-D will be provisioned as a dry copper twisted pair (2- or 4-wire) Loop that is unencumbered by any intervening equipment (e.g., filters, load coils, range extenders, digital loop carrier, or repeaters).

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