DIDComm in Hyperledger Aries Sample Clauses

DIDComm in Hyperledger Aries. Hyperledger Aries [24] builds on top of Hyperledger Indy, and uses Indy ledger as just one of the possible underlying Decentralized Ledgers (in fact, as of today, interfacing non-Indy ledgers is ongoing in the Aries community). The Aries community [25] itself declares that “Xxxxx grew out of the work in Hyperledger Indy to create technologies for managing decentralized identity. Indy provides a specific blockchain purpose-built for identity. The tools created in Indy for building agents are being migrated to Aries and extended to be blockchain-agnostic. Functionality related to the Indy ledger will remain in Indy.” In fact, Aries is a large initiative which includes several working groups and produced more implementations of the same functional component, including: ● aries-cloudagent-python (Aca-py) [27]: the Python implementation is based on DIDComm-V1 and uses Indy as a Ledger through Indy SDK. The agent is suitable for all non-mobile agent applications and has production deployments. Many SSI implementations are already in place based on this component, including [28] and [29]. ● aries-staticagent-python: a configurable server-side agent that does not use persistent storage. To use it, keys are pre-configured and loaded into the agent at initialization time. ● aries-framework-dotnet: it can be used for building mobile (via Xamarin) and server-side agents and has production deployments. The framework uses Indy through the indy-sdk ● aries-framework-go: An innovative and technically interesting pure go language (golang) framework that does not currently embed the Indy SDK and works on supporting a golang-based verifiable credentials implementation. The development is in progress and some features are based on still “experimental projects” like go-mobile. The most recent version of the framework [26] provides 3 different implementations on the same common communication libraries: o aries-agent-rest: a Command Line Interface (CLI) implementation of a server-side framework. Following the framework-controller paradigm, it exposes an HTTP interface for its companion controller. Differently from other frameworks, it does not rely on Indy SDK. A golang-based verifiable credentials implementation is in progress. o aries-agent-mobile: uses the experimental go-mobile tool [30] to produce SW libraries used for Android and Ios. o aries-js-worker: a javascript interface to Aries Framework Go, for use in node.js or directly in the browser.
AutoNDA by SimpleDocs

Related to DIDComm in Hyperledger Aries

  • Interstate Educational Personnel Contracts 1. The designated state official of a party state may make 1 or more contracts on behalf of his state with 1 or more other party states providing for the acceptance of educational personnel. Any such contract for the period of its duration shall be applicable to and binding on the states whose designated state officials enter into it, and the subdivisions of those states, with the same force and effect as if incorporated in this agreement. A designated state official may enter into a contract pursuant to this article only with states in which he finds that there are programs of education, certification standards or other acceptable qualifications that assure preparation or qualification of educational personnel on a basis sufficiently comparable, even though not identical to that prevailing in his own state.

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

  • Clinical Management for Behavioral Health Services (CMBHS) System The CMBHS is the official record of documentation by System Agency. Grantee shall:

  • Indiana Veteran Owned Small Business Enterprise Compliance Award of this Contract was based, in part, on the Indiana Veteran Owned Small Business Enterprise (“IVOSB”) participation plan, as detailed in the IVOSB Subcontractor Commitment Form, commonly referred to as “Attachment A-1” in the procurement documentation and incorporated by reference herein. Therefore, any changes to this information during the Contract term must be approved by IDOA’s IVOSB Division (“IVOSB Division”) and may require an amendment. It is the State’s expectation that the Contractor will meet the subcontractor commitments during the Contract term. The following certified IVOSB subcontractor(s) will be participating in this Contract: [Add additional IVOSBs using the same format.] IVOSB COMPANY NAME PHONE EMAIL OF CONTACT PERSON PERCENT Briefly describe the IVOSB service(s)/product(s) to be provided under this Contract and include the estimated date(s) for utilization during the Contract term: A copy of each subcontractor agreement must be submitted to the IVOSB Division within thirty (30) days of the effective date of this Contract. The subcontractor agreements may be uploaded into Pay Audit (Indiana’s subcontractor payment auditing system), emailed to XxxxxxxXxxxxxxxXxxxxxxxxx@xxxx.XX.xxx, or mailed to IDOA, 000 X. Xxxxxxxxxx Street, Room W-478, Indianapolis, IN 46204. Failure to provide a copy of any subcontractor agreement may be deemed a violation of the rules governing IVOSB procurement and may result in sanctions allowable under 25 IAC 9-5-2. Requests for changes must be submitted to XxxxxxxXxxxxxxxXxxxxxxxxx@xxxx.XX.xxx for review and approval before changing the participation plan submitted in connection with this Contract. The Contractor shall report payments made to certified IVOSB subcontractors under this Contract on a monthly basis using Pay Audit. The Contractor shall notify subcontractors that they must confirm payments received from the Contractor in Pay Audit. The Pay Audit system can be accessed on the IDOA webpage at: xxx.xx.xxx/xxxx/xxxx/xxxxxxxx.xxx. The Contractor may also be required to report IVOSB certified subcontractor payments directly to the IVOSB Division, as reasonably requested and in the format required by the IVOSB Division. The Contractor’s failure to comply with the provisions in this clause may be considered a material breach of the Contract.

  • Local Health Integration Networks and Restructuring In the event of a health service integration with another service provider the Employer and the Union agree to meet.

  • Sugar-Sweetened Beverage Prohibition Contractor agrees that it shall not sell, provide, or otherwise distribute Sugar-Sweetened Beverages, as defined by San Francisco Administrative Code Chapter 101, as part of its performance of this Agreement.

  • TOOL STORAGE 1. A company shall provide on all construction jobs in towns and cities, and elsewhere where reasonably necessary and practicable (or if requested buy the employee), a suitable and secure waterproof lock-up solely for the purpose of storing employees’ tools, and on multi-storey and major projects the company shall provide, where possible, a suitable lock-up for employees’ tools within a reasonable distance of the work area of large groups of employees.

  • Financial Management System Subrecipient shall establish and maintain a sound financial management system, based upon generally accepted accounting principles. Contractor’s system shall provide fiscal control and accounting procedures that will include the following:

  • Small and medium-sized enterprises 1. The Parties will promote a favourable environment for the development of the small and medium enterprises (SME) on the basis of strengthening of the relevant private and governmental bodies, as well as the exchange of experiences and good practices with the SME. 2. Cooperation shall include, among other subjects: (a) the designing and development of mechanisms to encourage partnership and productive chain linkage development; (b) development of human resources and management skills to increase the knowledge of the Chinese and Peruvian markets; (c) defining and developing methods and strategies for clusters development; (d) increasing access to information regarding mandatory procedures and any other relevant information for an SME exporter; (e) defining technological transference: programs oriented to transfer technological innovation to SME and to improve their productivity; (f) increasing access to information on technological promotion programs for SME and financial support and encouragement programs for SME; (g) supporting new exporting SME (sponsorship, credits and guarantees, seed capital); and (h) encouraging partnership and information exchange for SME financing institutions (credits, banks, guarantee organizations, seed capital firms). 3. Cooperation shall be developed, among other activities, through: (a) information exchange; (b) conferences, seminars, experts dialogue and training programs with experts; and (c) promoting contacts between economic operators, encouraging opportunities for industrial and technical prospecting.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!