# VCX Mission Statement
-adjusted the ordering of elements to emphasize the development of wallets as the end goal.
- added privacy note
- added testing and documentation target
- added community support and environment
- other?

The mission of the VCX Project is to enable and accelerate the development and adoption of digital wallets and related infrastructure. VCX will do so by providing components and libraries through useful, self-contained packages written in Rust that are accessible by a variety of platforms.

VCX is designed to fulfill multiple requirements of digital wallets and related infrastructure, including: DID handling, verifiable credential management, encrypted peer to peer communication, Verifiable Data Registry (VDR) support, and wallet communication protocols. VCX strives to provide solutions that prioritize privacy for individuals.

The VCX Project aims for its packages to be performant, secure, reliable, interoperable, scalable, and easy to use. VCX is written in Rust, but is ultimately designed to be widely usable with other platforms or languages through wrappers. VCX is designed to provide both modular self-contained packages, and a ready-to-go framework depending on developer needs.

VCX targets the creation and maintenance of rigorous tests and clear documentation for project reliability and ease of use.

VCX is dedicated to providing a welcome and open community for both contributors and consumers of the project.

3-4-25
The mission of the VCX Project is to provide the components and libraries for the development of digital wallets and related infrastructure by providing useful, self-contained packages written in Rust that are accessible by a variety of platforms.

VCX is designed to fulfill multiple requirements of digital wallets and the related infrastructure, including DID handling, verifiable credential management, encrypted peer to peer communication, Verifiable Data Registry (VDR) support, and wallet communication protocols. VCX strives to provide solutions for decentralization.

The VCX Project aims for its packages to be performant, secure, reliable, interoperable, scalable, and easy to use. VCX is written in Rust, but is ultimately designed to be widely usable with other platforms or languages through wrappers. VCX is designed to provide both modular self-contained packages, and a ready-to-go framework depending on developer needs.

VCX is designed to fulfill multiple requirements of digital wallets, which include:
- DID handling, with broad DID method support
- Support for a variety of credential formats
- Support for a variety of communication formats, such as DIDComm or OID4VC

can be combined for a variety of use cases, including credential exchange, proof exchanges, encrypted peer to peer communication,

Core things:
-
- Rust features
- Security
- Performance
- Ease of use
- Flexible
- Useful, self contained packages that can be combined for a variety of use cases, including credential exchange, proof exchanges, encrypted peer to peer communication,

- Rust first, but platform independent
- provide functionality for DIDs and DID documents, DIDComm,

## Current VCX Description
VCX is set of crates to work with DIDs, DID Documents, DIDComm, Verifiable Credentials and Hyperledger Aries.

## Aries Mission Statement
The mission of the Aries Project is to create shared, reusable, interoperable, and scalable agents for developing critical decentralized trust solutions, including verifiable credentials and communication technologies. It is designed to be agnostic regarding DID methods, credential types, and communication protocols, with ledgers being optional. These agents represent organizations, people, and things, capable of taking actions through direct interaction or subject-approved automation, fostering robust and flexible decentralized trust solutions.

## OWF Mission Statement
The purpose of the OpenWallet Foundation (the “OWF”) is to support various open source, open data and/or other open projects relating to or supporting development of digital wallets, including infrastructure and support initiatives related thereto (each such project, a “Technical Project”) , in accordance with the provisions of this Charter. The governance of each Technical Project is as set forth in the charter for that Technical Project.

The OWF aims to enable entities to transact securely, and in a privacy enhancing fashion, in- person and on-line where attributes stored in, and managed by, the wallet. The OWF will:

develop and maintain open source code for wallets to enable and ensure wallet interoperability,
advocate for the adoption of the interoperable digital wallet technology, and
collaborate with Standards Development Organizations (SDOs) in the development and proliferation of open standards related to digital wallets

The OWF will not publish a publicly available wallet (including into any application stores).

The OWF supports the Technical Projects. The OWF operates under the guidance of the Governing Board of the OWF (the “Governing Board”) and Linux Foundation Europe (the “LFEU”) as may be consistent with Linux Foundation Europe’s tax-exempt status.

The Governing Board manages the OWF. The Governing Board may establish other committees and other working groups (collectively, and including the Technical Advisory Council, “Committees”) which will report to the Governing Board.

from: https://tac.openwallet.foundation/governance/charter/