Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting up test frameworks for xBFT variants #62

Open
kubasiemion opened this issue Mar 4, 2020 · 1 comment
Open

Setting up test frameworks for xBFT variants #62

kubasiemion opened this issue Mar 4, 2020 · 1 comment
Labels
TODO after implementation Issue deemed relevant, but to be taken care of after the interop bft protocol

Comments

@kubasiemion
Copy link
Contributor

At the face-to-face meeting in London we have agreed that the way forward requires us to get down to the running code and demonstrate weaknesses/robustness of different proposals. Namely:

Resolution:. Kaleido to provide the test cases they use with Quorum to create a foundation for testing consensus mechanisms. This will be enhanced by the BFT working group. The expectation is within two to three months this will be done. The work of ConsenSys and JP Morgan will provide variation of IBFT then an agreement will be made. The hope is that specification will be available in a few months and then implementation a few months after that.

There is a number of specific questions that need to be answered to make this happen, and let me begin the list with:

  1. The basic topology: how many nodes?, on how many machines?, dockerized? how many validators and how many observers?
  2. Hosting machines specs CPUs/RAM/HDD/SSD/...
  3. Any TLS?
    And of course test cases - we need to create a vetted list
@saltiniroberto saltiniroberto added the TODO after implementation Issue deemed relevant, but to be taken care of after the interop bft protocol label Jun 10, 2020
@saltiniroberto
Copy link
Contributor

On 27 May 2020 the *BFT Task Force reached the following decisions on this issue:

  • While no immediate action is expected on this issue, keep it open as a reminder that a test framework must eventually be developed;
  • Re-asses and possibly rephrase the issue once a preliminary implementation of an agreed BFT protocol is available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TODO after implementation Issue deemed relevant, but to be taken care of after the interop bft protocol
Projects
None yet
Development

No branches or pull requests

2 participants