v0.1.3 Release Notes - May 06, 2020

This release adds the following features to the Aries Framework Go.

• Support for the Out-of-Band protocols at the SDK level
• Support for Issue Credential and Present Proof protocols.
• Initial support for did:key method in the framework.
• KMS/Crypto
  • New Crypto implementation based on Tink.
  • New local KMS implementation using the new Crypto default implementation.
  • New ECDH-ES Tink key templates needed for JWE encryption/decryption.
  • New SecretLock service to protect keys in the KMS store.
  • JWE Serialize/Deserialize support.
  • JWE Encrypt/Decrypt support using ECDH-ES Tink key templates
  • Support importing private keys into the new local KMS
  • Support exporting public keys as raw [ ]byte from local KMS in both DER and IEEE-P1363 format
  • Support reading public keys raw [ ]byte as Tink key handles to be used with Crypto/KMS service
• Linked Data Signatures
  • Support for JWS proof type.
  • Support for JsonWebSignature2020 and EcdsaSecp256k1Signature2019 signature suites
    • (in addition to existing support for Ed25519Signature2018)
• VC/VP Improvements
  • Do not pass private keys directly for signing, use Signer abstraction.
  • Support JsonWebSignature2020 and EcdsaSecp256k1Signature2019 signature suites
    • (in addition to existing support for Ed25519Signature2018.)
  • Support multiple signature suites for signing and verification.
  • Support JWK in the signature suites and in DID resolution.
  • Examples of Crypto/KMS based signers and verifiers of VC linked data proofs.
  • Improved JSON-LD strict validation of VC / VP documents.

v0.1.2 Release Notes - February 26, 2020

This release adds the following features to the Aries Framework Go.

• DIDComm Router/Mediator
  • New APIs - Unregister, Get Connection ID
  • REST Controller
    • BDD tests
    • OpenAPI Demo
• Controller APIs
  • Refactored REST API to use common command controllers
  • REST API support for Register, Unregister, GetConnectionID
  • New JavaScript APIs support for all the APIs supported by REST controller
  • Support for WebSocket notification
  • Support for Authorization Bearer header
• WASM/JS Support
  • Uses common command controllers to support all controller features
• Verifiable Credentials
  • REST/JS API to validate VC

v0.1.1 Release Notes - January 29, 2020

This release adds following features to the Aries Framework Go.

• Introduce
  • RFC
  • Flow diagram
  • GoDoc
  • BDD Tests
• DIDComm Router/Mediator
  • RFCs
    • Route coordination
    • Transport Return Route
    • Forward Message
  • Flow diagram
  • Documentation
  • GoDoc
  • BDD Tests
    • DIDComm between two Edge Agent(without Inbound) through Router/Mediator
    • DIDComm between Edge Agent(without Inbound) and Router/Mediator
• External Message Handlers
  • RFC
  • GoDoc
  • REST Demo Steps
  • BDD Tests
    • Messaging between the agents using SDK
    • Messaging between the agents using REST/controller binding
• HTTP Over DIDComm (WIP)
  • RFC
  • GoDoc
  • BDD Test
• Verifiable Credentials
  • Spec
  • Support for JSON-LD 1.1
  • Support for Linked Data proofs
  • GoDoc
• Transports
  • Added support for WebSocket
• Storage
  • Added support for IndexDB in the browser/JS
• VDRI(Verifiable Data Registry Interface)
  • Added REST endpoint to create Public DID

v0.1.0 Release Notes - November 13, 2019

Aries Framework Go
The aries package provides access to clients being managed by the Framework.

1. Provides KMS (Key Management System).
2. Provides protocol provider factory interface.
3. Provides injectable storage. (LevelDB is provided in 0.1.0.)
4. Provides DID Resolver. (HTTPS binding is provided in 0.1.0.)
5. Provides inbound/outbound dispatcher service. (HTTP transport is provided in 0.1.0.)

Note: these interfaces are preliminary and we plan to update as the pluggable API interfaces become more clear across the community.

The Go framework currently supplies Go native default implementations for all pluggable interfaces, and hence, has no dependency requirements in 0.1.0.

Demonstrations

• BDD tests show the flow of DID Exchange and DID resolution (against Sidetree).
  • Run make bdd-test in the cloned repository after installing dependencies (see README).
• OpenAPI (swagger) can be used to perform DID Exchange between agents.
  • Run make run-openapi-demo in the cloned repository after installing dependencies (see README).

Aries Protocol RFC Services

1. RFC 0023: DID Exchange Protocol 1.0

• Manages messages and protocol state.
• Send events to controller logic.
• did:peer and resolvable "public" DIDs are supported.
• Not yet implemented: Problem report, Implicit invitation.

Note: RFC 0028: Introduce 1.0 code is incomplete (targeted for 0.1.1).

Controller Bindings

1. DID Exchange Protocol 1.0

• Go
• REST
• Not yet implemented: C, WASM.

Data and Document Formats

1. RFC 0019 AuthCrypt DIDComm envelope
2. Draft JWE DIDComm envelope
3. DID document parser.

Note: The verifiable credential code is incomplete but is being actively tested against the W3C test suite as it is developed. (JWT subset targeted for 0.1.1).