After months of hard work by 22 contributors, more than 130 PRs, and 1000+ file changes, we are thrilled to announce that Aries Framework JavaScript (AFJ) version 0.4.0 has been released! This update contains various feature additions, as well as improvements in terms of modularity. In this post, we will go over the most notable changes of this release and the possibilities they offer.

## Replacing the Indy SDK
In previous versions of Aries Framework JavaScript, the framework was closely tied to the Indy SDK Rust library. In addition to communicating with the Indy ledger, this dependency was also used for operations specific to the AnonCreds credential format and secure storage. Because the framework relied on this dependency for storage, users of the framework were forced to include this dependency into their application bundles, even if they did not interact with the Indy ledger or use the AnonCreds credential format. This caused unnecessarily big package sizes, hindering usability.

To solve this, new AFJ modules were introduced, each taking over a part of the responsibility previously carried by te Indy Rust library. The benefit of splitting up the three uses (ledger communication, AnonCreds operation, and secure storage) into separate components is that developers don't need to include more into their app bundles than absolutely necessary. These modules enable AFJ to use three seperate Rust libraries:
- [Indy VDR](https://github.com/hyperledger/indy-vdr) -- Used for communication with Indy ledgers;
- [Aries Askar](https://github.com/hyperledger/aries-askar) -- Used for secure storage;
- [AnonCreds](https://github.com/hyperledger/anoncreds-rs) -- Used for handeling the AnonCreds credential format.

The Indy SDK Rust is currently optional in AFJ and mostly used for (temporary) migration purposes. It has been separated from the core of the framework and was moved to its own separate module called `@aries-framework/indy-sdk`. Moving from using the Indy SDK Rust library to using the libraries mentioned above not only benefits package size but also enables more modular use of the framework.

## Ledger-agnostic AnonCreds

Another noteworthy enhancement in version 0.4.0 is that AnonCreds can now be used independently of any Indy-specific logic. This has been achieved though the addition of two new modules: `anoncreds` and `anoncreds-rs` that are fully compliant with [AnonCreds Specification 1.0](https://hyperledger.github.io/anoncreds-spec). As a result, developers can now employ the AnonCreds format in combination with other ledgers or verifiable data registries supported within Aries Framework JavaScript. This improvement allows for greater flexibility.

There are already some integrations under development. For example [Cardano](https://github.com/roots-id/cardano-anoncreds/tree/main/reference-implementations/afj) has created a reference implementation for using AnonCreds with their ledger and [2060.io](www.2060.io) is working on a [did:web module](https://github.com/2060-io/aries-javascript-didweb-anoncreds) for using AnonCreds.

Another result of this development is the `cheqd` module. By integrating the cheqd module, developers can read and write AnonCreds-related objects to the cheqd network. The module contains components such as a DID resolver, a DID registrar, and other needed operations. This integration underscores the ledger-agnostic nature of the framework, showcasing its potential to work across diverse ledger technologies.

## OpenID for Verifiable Credential Issuance

A major highlight in bridging ecosystems, is the introduction of support for the OpenID for Verifiable Credential Issuance (OID4VCI) protocol. The OpenID4VC procols have been gaining popularity because of their simplicity and its foundation in proven technology OAuth2. This addition enables developers to issue and receive credentials using the OpenID4VC stack in their AFJ-based solutions. As we strive to enhance the framework's compatibility and align with industry standards, we are also working on adding support for OpenID for Verifiable Presentations (OID4VP) and Self-Issued OpenID Provider v2 (SIOPv2). These are currently in development and will be introduced in forthcoming releases. Supporting this stack makes Aries Framework JavaScript usable in a variety of decentralized identity ecosystems.

## JWT Verifiable Credentials

Last but not least. Aries Framework JavaScript previously supported JSON-LD credentials, in version 0.4.0 AFJ has been updated to include support for JWT credentials as well. While the data model remains unchanged, the inclusion of JWT credentials enables developers to interact with others who use this popular format.

## Want to know more about Aries Framework JavaScript?

[Join us on July 11th](https://zoom.us/meeting/register/tJAqf-GgqD0tG9ZEblzG73MeWXS1yyLgv1kA#/registration) for a workshop on the 0.4.0 release! Presented by Ariel Gentile, Karim Stekelenburg, and Berend Sliedrecht, this workshop will be an in-depth breakdown of what's new in Aries Framework Javascript 0.4.0 as well as a practical demonstration of how it can be used.

Check out the 0.4.0 release [here](https://github.com/hyperledger/aries-framework-javascript/releases/tag/v0.2.0) and the update instructions [here](https://aries.js.org/guides/0.4/updating/versions/0.3-to-0.4). For general documentation, see [aries.js.org](https://aries.js.org/).

If you’re interested in Hyperledger Aries Framework JavaScript and its developments, we recommend you join the working group call (07:00 MT / 13:00 UTC on [Zoom](https://zoom.us/j/99751084865?pwd=TW1rU0FDVTBqUlhnWnY2NERkd1diZz09)) and check out the [GitHub repo](https://github.com/hyperledger/aries-framework-javascript). If you want to discuss building a solution with the framework, feel free to reach out to me at [e-mail].