roots-id / rootswallet Goto Github PK

If we root every interaction to the relationships the interface becomes more intuitive. for now, one person one relationship one chat. that will be acceptable for alpha prototype.

We need to decide which license best apply to our project: MIT, Apache, etc

https://github.com/roots-id/rootswallet/wiki/Roots-Wallet-Implementation-Proposal#layer-2-didcomm-peer-to-peer-protocol

Key generations were embedded as part of did:peer and Prism libraries. We need to move out from the native modules so they can be available by javascript, enabling the integration with the storage module.

feedback from several people about the demos.

I open this issue to create a list of coding best practices that we can discuss and publish afterwards:

1. all UI texts must be localized i18n
2. avoid dependency to non-mature and/or non well adopted external libraries

Present QR code for DID JSON and Credential JSON.
This is mostly an exercise for displaying a QR code. we'll work out the actual details of what data to present in a future ticket.

Adding https://github.com/sicpa-dlab/didcomm-jvm
and
https://github.com/sicpa-dlab/peer-did-jvm

The technology stack and specifications for Decentralized Identity are not mature, I expect a lot of rework on the near future. To avoid doing much rework on the QC procedures I think the best is to do a QA strategy focused on the lower levels (unit test)

All expo based testing is done. Now we need to get the app working via an APK file installation (like Play Store does).

For instance if a credential is unverified and your phone does not have connectivity to check revocation status or is still processing the verification steps.

https://github.com/roots-id/rootswallet/wiki/Roots-Wallet-Implementation-Proposal#layer-4-uiux
https://cardano.ideascale.com/c/idea/396593

https://github.com/roots-id/rootswallet/wiki/Roots-Wallet-Implementation-Proposal#layer-2-didcomm-peer-to-peer-protocol

The user will receive actionable wallet messages
and receive system messages indicating status of actions
and be able to get detail messages to understand what is technically occurring during each action as well as current state.
we will prototype a separation of these messages in a chat view and then discuss.

https://github.com/roots-id/rootswallet/wiki/Roots-Wallet-Implementation-Proposal#layer-2-didcomm-peer-to-peer-protocol

See https://github.com/roots-id/rootswallet/wiki/Roots-Wallet-Implementation-Proposal#layer-1-utilities-and-ledger-interface

I tried a quick hermes/drawer upgrade to rootschat and it digressed quickly. i'll start with a clean project to see what progress will take.

We will need several graphics, layout, and color bits to make a consistent looking app. These elements include:

#Components Needed
For guidance, refer to this issue:

• #10
• [x ] #10
• favicon 🎉
• background default color
• highlight color
• Font style
• Font color - default / highlighted / greyed out
• splash screen image
• background image
• etc

This issue is created to list reasons, pros and cons, for selecting React Native as the initial framework:

• we plan to build a mobile wallet that can run in Android and iOS devices
• current Prism SDK was provided in Kotlin. There's a plan to release it in other languages but not delivery date was given. An old SDK in javascript exists but IOG team said it is incomplete
• Kotlin Multiplatform Mobile was an option. It's a good framework but it is in alpha stage. We were able to build Prism SDK to work in Android, but building for iOS was impossible (it looks like the SDK needs to be built as multiplatform)
• React Native allows us to embed Kotlin SDK as a native module and build for Android only
• In the future, if we receive Prism SDK in swift/objective-C or Javascript we can easily add and build for iOS
• React Native views and common code can be shared and deployed on both OS.
• React Native is a matured and well adopted multiplatform framework with a huge community. There's a large library of components both provided by Facebook and the community

Should we use something similar as Discord app?

From https://youtu.be/d-5MmLLd3xY
Register
Route
Authcrypt
Plaintext
Oblige
Key_admin
Se_admin
Rule_admin

https://github.com/roots-id/rootschat

https://github.com/roots-id/rootswallet/wiki/Roots-Wallet-Implementation-Proposal#layer-1-utilities-and-ledger-interface

finish adding hooks in app for all of these credential operations

Prompt user for wallet password and store the wallet by password

For instance https://github.com/hyperledger/aries-mobile-agent-react-native/blob/504471beed7f5f5a80a6c679e78a472a1aacb1ff/App/screens/PinCreate.tsx

If we follow the Aries steps, the Aries Interop Profile (AIP) provides a clear path, for an MVP I believe these are the most basic requirements:

Stablish envelop protocol

This is the first step to establish a connection here QR, URL or JSON Invitation files are used (un-encrypted):
https://github.com/hyperledger/aries-rfcs/tree/bed4989dd6517f7a9de3696800e57e4c6ef49231/features/0434-outofband

Here a pairwise relation is created, DIDs are interchanged (DIDComm):
https://github.com/hyperledger/aries-rfcs/tree/b3a3942ef052039e73cd23d847f42947f8287da2/features/0023-did-exchange

Content protocol

Protocol for issuance
https://github.com/hyperledger/aries-rfcs/tree/b3a3942ef052039e73cd23d847f42947f8287da2/features/0453-issue-credential-v2

Protocol for credential verification
https://github.com/hyperledger/aries-rfcs/tree/b3a3942ef052039e73cd23d847f42947f8287da2/features/0454-present-proof-v2

Other notes

Error reporting related to #13
https://github.com/hyperledger/aries-rfcs/tree/b3a3942ef052039e73cd23d847f42947f8287da2/features/0035-report-problem

Full AIP v2: https://github.com/hyperledger/aries-rfcs/tree/main/concepts/0302-aries-interop-profile#aries-interop-profile-version-20

If we also implement the features below we can use https://indicio-tech.github.io/mediator/ as mediator agent so the mobile app can receive messages from other agents (need to do more research on this one):

https://github.com/hyperledger/aries-rfcs/blob/main/features/0211-route-coordination/README.md
https://github.com/hyperledger/aries-rfcs/blob/main/features/0160-connection-protocol/README.md

https://github.com/roots-id/rootswallet/wiki/Roots-Wallet-Implementation-Proposal#layer-2-didcomm-peer-to-peer-protocol

Create a transport layer and provide usage example to send didcomm messages between two devices in same network

https://github.com/roots-id/rootswallet/wiki/Roots-Wallet-Implementation-Proposal#layer-1-utilities-and-ledger-interface

make wal-lib/prism operations clickable

• We will be open source, agile, small, simple, fast, pluggable in order to serve immediate needs. Our preferred starting point is Atala Prism adoption.
• We will learn from Aires and cherry pick to shape our future.
• We will communicate constantly with our partners and as much of the ecosystem as we can.
• For Fund 7: What are the minimum requirements for any wallet?
• For the future: Which requirements for DIDs, Credentials, UI should we focus on from Indy?
• For the future: Which wallet functionalities should be interoperable first? Which can wait?
• How do we relate/communicate with the Atala Prism Wallet development team/project?
• How much of AP can we share? APPP videos/slides? Our open source code using the AP SDK?
• What is the size of the Atala Prism development team, etc.

https://github.com/roots-id/rootswallet/wiki/Roots-Wallet-Implementation-Proposal#layer-3-data-exchange-protocols

unite the work!

See https://github.com/roots-id/rootswallet/wiki/Roots-Wallet-Implementation-Proposal#layer-1-utilities-and-ledger-interface

This issue is to research and decide if we should implement DIDComm V1 or V2 (or both) and select a library.

https://github.com/roots-id/rootswallet/wiki/Roots-Wallet-Implementation-Proposal#layer-3-data-exchange-protocols

These operations are left to do, since we've successfully created/published DIDs and credentials in this demo
roots-id/rootschat@d5a7be5

The initial template was created as follows:

If first time with React Native, install expo cli:
yarn global add expo-cli

Generate blank TypeScrip template:
expo init rootswallet

Generate Android and iOS code (use com.rootswallet as Android Package and iOS Bundle Identifier):

cd rootswallet
yarn eject

Then I created PrismModule.kt, RootsWallet.java loaded in MainApplication.java. Add kotlin and prism code in build.gradle.

How to build and run:
If first time with React Native, install expo cli:
yarn global add expo-cli

Install dependencies:
yarn install

In my MAC I had to:
export ANDROID_SDK_ROOT=/Users/rodolfo/Library/Android/sdk

Export Prism SDK password:
export PRISM_SDK_PASSWORD=ghp_2CTxxxxxxxxxxx

Install Android Studio, and open Simulator from ADV Manager

Build and run:
yarn android

See app launching in simulator, click to generate DID, and see generated DID in log

See https://github.com/roots-id/rootswallet/wiki/Roots-Wallet-Implementation-Proposal#layer-1-utilities-and-ledger-interface

Instead it saves the passphrase. Need to be able to work with keys in secure store.
Note: this is mostly being done as a bug, to see how bug issues look in our system.

Update slides/website/repo w/ v2 branding

Prototype saving passphrase and did from our test page using expo secure store.

Test that a pull request closes this ticket.

https://github.com/roots-id/rootswallet/wiki/Roots-Wallet-Implementation-Proposal#layer-3-data-exchange-protocols