| Who | Notes |
|---|
| - I have updated the release description, added all merged PRs
- Will add Burrow integration PR link to the release information
|
| - Prepared the 1.2rc1 tag and merged all PRs which was left
- Will proceed with the support of interns
|
| - Continuing rebasing of HSM integration branch
- Want to test the issue from the community chat
- Andrei Lebedev > We need to test all endpoints, there is a risk that they would not work
|
| Stepan Lavrentev | - I have faced the issue with the Ursa integration testing using current Python lib. I am using the SHA-2 (512) crypto and NACL library
- Mikhail Boldyrev > I have performed the investigation. Probably there is an incompatibility between crypto libraries
- I have also tried the Python implementation of DCA
- Andrei Lebedev > There is an open PR in Iroha-python lib from Kamill. It uses the correct library.
- Regarding Burrow integration testing: there is information about the smart contract for testing in the documentation.
- Andrei Lebedev > Open engineCallTest file and get the list of test-smart-contracts. They are used for integration testing.
- Seems like that there is an issue with the documentation about Burrow. Address of singleService contract
- Started checking P2P TLS encryption. There is a question – how can I add a new node to the network with enabled P2P TLS?
- Andrei Lebedev > There is no such feature in the current release.
- Mikhail Boldyrev > We should fix the documentation, there is no TLS for P2P currently, TLS is working only for Torii
- Regarding Ursa integration: probably we need to add details, that currently, we are working on with the Ed25519 and SHA-2 only
- Regarding TLS configuration for Torii: how to enable it?
- Andrei Lebedev > This should be configured by the user, the certificate should be provided by the user, too
|