Turn aries-vcx into consumable crate about aries-vcx HOT 4 CLOSED

Updated architecture

This splits Rust portion of AriesVCX repo in 3 layers, 4 crates.

1. C-Bindings crate

• Rust project depending on the main AriesVCX crate, providing C ABI interface and memory management (providing references to in-memory vcx objects via u32 handles)

2. AriesVCX crate

• This is the definition "what AriesVCX" is. This will be our main artifact, directly consumable as crate in 3rd party Rust projects. This is layer where we glue up runtime dependencies (libindy), agency (downloading and updating agency-stored messages), networking (what client to use for network comm, dealing with SSL) and use AriesFSM Crate to deal with Aries protocols.

3. AriesFSM Crate

• Essentially codification of Aries RFCs, should be with almost no dependencies. It should be very simple, only reflect Aries protocol state machines, message types, transitions and transition inputs. Given the simplicity, this crate should be compilable to WASM and should serve as cornerstone of differently opinionated Aries implementations.

from aries-vcx.

Generally implemented, but before we close we should:

• improve APIs exposed by the crate #325
• publish on crates.io #309

from aries-vcx.

Updated architecture diagram

from aries-vcx.

aries-vcx can now be considered consumable stateless aries crate which can simultaneously manage multiple wallets and multiple pool connections.

• Example how aries-vcx can be consumed: https://github.com/hyperledger/aries-vcx/tree/main/agents/rust/aries-vcx-agent

from aries-vcx.