Migration of Ripple Trade/Ripple Wallet to Registered MSB Sample Clauses

Migration of Ripple Trade/Ripple Wallet to Registered MSB. Within 30 days of the date of this agreement, Ripple Labs and XRP II will move its service known as Ripple Trade (formerly known as Ripple Wallet, which allows end users to interact with the Ripple protocol to view and manage their XRP and fiat currency balances), and any such functional equivalent, to a money services business that is registered with FinCEN (the “Ripple Trade MSB”).
AutoNDA by SimpleDocs

Related to Migration of Ripple Trade/Ripple Wallet to Registered MSB

  • Designation of Key Personnel The Contractor’s Contract Manager for this engagement shall be Xxxxxxx Xxxxxxx, Phone: (000) 000-0000, Email Address: xxxxxxx@xxxxxxxxxx.xxx. The City’s Contract Manager for the engagement shall be Xxx Xxxxx, Phone: ( 512 ) 974 - 8211 , Email Address: Xxx.Xxxxx@xxxxxxxxxxx.xxx. The City and the Contractor resolve to keep the same key personnel assigned to this engagement throughout its term. In the event that it becomes necessary for the Contractor to replace any key personnel, the replacement will be an individual having equivalent experience and competence in executing projects such as the one described herein. Additionally, the Contractor will promptly notify the City Contract Manager and obtain approval for the replacement. Such approval shall not be unreasonably withheld.

  • COMMERCIAL REUSE OF SERVICES The member or user herein agrees not to replicate, duplicate, copy, trade, sell, resell nor exploit for any commercial reason any part, use of, or access to 's sites.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

  • Distribution of Union Literature (a) The Employer will provide space to the Union during Employee orientation to allow the Union to distribute Union literature related to the orientation of new Union members.

  • Service Jointly Provisioned with an Independent Company or Competitive Local Exchange Company Areas 4.5.1 BellSouth will in some instances provision resold services in accordance with the General Subscriber Services Tariff and Private Line Tariffs jointly with an Independent Company or other Competitive Local Exchange Carrier.

  • INFORMATION OF LOCKHEED XXXXXX (a) Information provided by LOCKHEED XXXXXX to SELLER remains the property of LOCKHEED XXXXXX. XXXXXX agrees to comply with the terms of any proprietary information agreement with LOCKHEED XXXXXX and to comply with all proprietary information markings and restrictive legends applied by LOCKHEED XXXXXX to anything provided hereunder to SELLER. XXXXXX agrees not to use any LOCKHEED XXXXXX provided information for any purpose except to perform this Contract and agrees not to disclose such information to third parties without the prior written consent of LOCKHEED XXXXXX. SELLER shall maintain data protection processes and systems sufficient to adequately protect LOCKHEED XXXXXX provided information and comply with any law or regulation applicable to such information.

  • Distribution of UDP and TCP queries DNS probes will send UDP or TCP “DNS test” approximating the distribution of these queries.

  • Use of University Facilities Members may use the office assigned to them in connection with such professionally-related activities as preparation of professional manuscripts and materials, scholarly endeavors, approved consultancies, and service to professional associations, schools, or other groups or agencies for whom such service is appropriate. Upon request, faculty may use laboratories and studios for non-sponsored research and other scholarly activity. Upon request, faculty may use meeting rooms and other physical facilities for professionally-related groups subject to availability and prevailing policies of the University governing use of facilities. The facilities of the TRC, Print Shop, computer labs and the use of University equipment are available to the faculty in connection with professional writing, research, or approved service projects subject to availability and to reimbursement at prevailing rates charged by the University.

  • Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).

  • Red Hat Enterprise Linux Developer Suite Red Hat Enterprise Linux Developer Suite provides an open source development environment that consists of Red Hat Enterprise Linux with built-in development tools, certain Red Hat Enterprise Linux Add-Ons, Red Hat Enterprise Linux for Real Time, Smart Management and access to Software Maintenance, but no Development or Production Support. If you use any of the Subscription Services or Software associated with Red Hat Enterprise Linux Developer Suite for Production Purposes, or use the Red Hat Enterprise Linux Software Subscription entitlement independently, you agree to purchase the applicable number of Units of the applicable Software Subscription. Red Hat does not provide Production Support or Development Support for Red Hat Enterprise Developer Suite.

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