You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Project

Hyperledger Aries


 11/17

Project Health

Project health continues to improve. A minor difficulty arose as members of the Sovrin Foundation paid staff were laid off. As members of that paid staff contributed to several code projects and community coordination within the Aries project some of those efforts briefly struggled as other community sponsors were found to help support that work. That disruption unfortunately includes the timely generation of this quarterly report. Overall, the Aries project was only very lightly affected; meetings were held, major code projects continued work without interruption, and releases continued. The lack of major disruption is a credit to the health and diversity of the project and broad support of active community members.

    
 BEST PRACTICE BADGE

White Paper

Graphic Set:

Webinars

Self Paced Training

Instructor Led Training

Code on

Github 

MOOC

Section

Presentations:

Technical /
Non-technical

Use Cases

INCUBATION


·         

·         

·         


https://github.com/hyperledger/aries

Hyperledger Aries is infrastructure for blockchain-rooted, peer-to-peer interactions. It includes a shared cryptographic wallet (the secure storage tech, not a UI) for blockchain clients as well as a communications protocol for allowing off-ledger interaction between those clients.  This project consumes the cryptographic support provided by Hyperledger Ursa, to provide secure secret management and decentralized key management functionality.

  • Aries provides client tools for blockchains
    • Wallets and Secrets Management
    • Encrypted Messaging
    • Signing and Submitting Transactions
    • Edge Protocol Support
  • 1.0 Interop Profile Work
    • Aries RFCs
    • Standardization across blockchains needing identity-related solutions
    • Use cases for Aries
      • BCGov's work
      • Sovrin Network use cases

Key Characteristics

  • A blockchain interface layer (known as a resolver) for creating and signing blockchain transactions
  • A cryptographic wallet that can be used for secure storage of cryptographic secrets and other information (the secure storage tech, not a UI) used to build blockchain clients
  • An encrypted messaging system for allowing off-ledger interaction between those clients using multiple transport protocols.
  • An implementation of ZKP-capable W3C verifiable credentials using the ZKP primitives found in Ursa.
  • An implementation of the Decentralized Key Management System (DKMS) specification currently being incubated in Hyperledger Indy.
  • A mechanism to build higher-level protocols and API-like use cases based on the secure messaging functionality described earlier.
  • Hyperledger Aries is infrastructure for blockchain-rooted, peer-to-peer interactions. It includes a shared cryptographic wallet (the secure storage tech, not a UI) for blockchain clients as well as a communications protocol for allowing off-ledger interaction between those clients.  This project consumes the cryptographic support provided by Hyperledger Ursa, to provide secure secret management and decentralized key management functionality.


    Documentation


    Project Management

    JIRA issues:

    Repositories

    https://github.com/hyperledger/aries

    https://github.com/hyperledger/aries-rfcs

    https://github.com/hyperledger/aries-cloudagent-python

    https://github.com/hyperledger/aries-staticagent-python

    https://github.com/hyperledger/aries-framework-go

    All Aries repositories - https://github.com/hyperledger?utf8=%E2%9C%93&q=aries&type=&language=

    Communication

    Mailing List

    Chat (for questions and ephemeral discussions)

    Meetings

    Aries Working Group

    People who want to learn about or contribute to Aries should join this call. This does not replace our asynchronous collaboration, but should help us keep everyone up-to-date and moving together.

    Discussion items: upcoming releases, current PRs, work that will generate future PRs, architecture changes that will impact downstream teams, project standards, best practices, design, etc.

    For call details and agendas, see: Aries Working Group

    Calendars

    History

  • No labels