List view
- Due by March 27, 2024•13/13 issues closed
- Due by February 7, 2024•6/6 issues closed
- No due date•130/130 issues closed
Features that should be part of the 1.0 release.
No due date•9/9 issues closedFeatures that have no priority to be added to v0.5. Should be non-breaking. If time allows it, can still be added to v0.5. v0.6 also targets to be published on crates.io.
No due date•39/39 issues closedDocument the repository fully on all the different levels: 1. Put comments on all functions for both Rust and the bindings. 2. Add rust crate description and readmes per crate and binding. 3. Add conceptual documentation to the mdbook to explain high-level concepts. 4. Add getting started sections per language to the mdbook. 5. Write out specifications for parts where we go beyond the standards.
No due date•21/21 issues closedImplement an IOTA Identity actor that is able to interpret and respond to stronghold, DID Comm and data sharing messages. In addition, should be transportation layer agnostic, but provide an interface to connect with a method of transportation. Should use the Stronghold-based peer-to-peer Messagebox system. The agent should also allow hooks to allow user-prompts.
No due dateImplement the DID Communication standard from the Decentralized Identity Foundation (DIF) found [here](https://github.com/decentralized-identity/didcomm-messaging/blob/master/spec.md).
No due date•11/11 issues closedAny features or bug fixes that are part of the scope for the next v0.5 release.
No due date•52/52 issues closed