| Who | Notes |
|---|
| - We are trying to set up Jira and GitHub integration, probably just using the Jira issue ID will work
- Proceeding with permissions and event listeners, made a PR
- Prepared slides and demo session
- Have many discussion about the functionality of the bridge for the internal project
- We are waiting for a review of the domain model from Makoto, I will find the question
- Updated contribution guide and readme about the building and deployment
- Will proceed with the genesis block issue, will extract the configuration from different modules
- Requested DevOps team for help with CI, we need them to configure
|
| - Helped with preparation for the demo session, it took 1-2 hours
- Fixed a bug in the Docker configuration
- Now I am started with Sumeragi refactoring, according to suggestion from Nikita. We have discussed it in the chat.
- Then I will proceed with the timeout of blocks.
|
| - Iurii requested the order of transactions, I am currently clarifying the use case. The current approach may not work. Will resolve the issue and provide suggestions to RFC.
- Also reviewing the state to be in sync.
- There is a question regarding the transaction forwarding: currently peers broadcasts transactions to the leader only. We can broadcast transactions for everybody, to avoid malicious leader related issues.
- 武宮誠 > If the block is finalized and the leader does not want to add it to the chain, we need to find a way how to avoid it.
- I got the idea, will describe it in the RFC for the Sumeragi.
|
| - We need to create a roadmap and expose the date of running test network. Then the community can join, become validators and try the things.
|