...
- Define the pull request review process for Indy Plenum/Node
- Review notes from 2019-11-18 Indy Contributors Call
- BC.gov team likes the process, and thinks it might be useful to use on the SDK as well.
- Consensus protocols in Indy
- Besu uses BFT:
- iBFT 2.0 (Istanbul BFT 2)
- Clique
- https://besu.hyperledger.org/en/stable/Concepts/Consensus-Protocols/Comparing-PoA/
- Tested at 8 nodes.
- Concerns with Aardvark versus RBFT
- Besu uses BFT:
- Update on LibVCX support for Aries
Future Calls
- Indy performance analysis (BC.gov)
- Migration of Indy-SDK to Aries-Core
- Requirements question: IS-1099, should we allow duplicate credentials from the same issuer?
- Non-secrets in the Indy Wallet
- Cam is working on pluggable crypto. The wallet shouldn't decide what encryption you should be using.
- Use cases where we would want to move keys between wallets
- Moving the link secret / credential data from one device to another (synchronized storage).
- Debug use cases
- Richard's hit other uses cases that were better solved with DID Doc, pre-signing, signing API.
- Work-around with the web-crypto API
...