-
Notifications
You must be signed in to change notification settings - Fork 985
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
Testnet Requirements Call #233
Comments
What is whiteblock actually providing? Is it authority round? https://github.com/Whiteblock/poa-test-setup Could the Görli initiative help? https://github.com/goerli/ |
Works for me. I'll be there. Thanks for scheduling this! @zscole |
Is this already captured in the test plan? If not, will it be? |
No, that's just our fork of POA Network that we were using to test their client within our environment. What the Whiteblock framework will provide is infrastructure and management. We can quickly configure and deploy an entire testnet, including the process of configuring nodes, generating accounts, funding these accounts, automating transactions, and all the other stuff that's required to replicate real-world performance in a controlled testing environment. The "dummy" nodes are provisioned to ensure a minimum baseline of activity in a network to reduce dependency on third-party cooperation, among other things. We covered a lot of this on last week's call, but we'll go over it in more detail on Thursday. Users who wish to participate and test within this network can provision their own node and join the network if they so choose and since it's all managed, it can be controlled in a manner that ensures deterministic results. Since it's permissioned and controlled, we don't need to worry about alternative consensus mechanisms and since the network itself is ephemeral, we can tear one down and start a new one that's equally populated within a few minutes. Like I said, we'll go over all this on the call. |
Reference this test plan we wrote. This document covers the testing methodology and process we've employed for the sharding-p2p-poc tests we've been running. Once we identify the requirements for this testnet, we'll draft a similar one, though I imagine the scale of this one will be larger than that one and will require a bit of coordination between parties. Either way, it's the same essential process. |
We'll likely have to push this meeting to Friday so @shahankhatch can join. |
Have whiteblock.io been engaged to provide this testnet service or are they acting independently? |
Will have call today at 8AM PST. |
Would love to join but absent. Will this too be recorded for later viewing? I should maybe mention that we're launching a goerli testnet in Croatia early next year, announcing specifics at Bločk. I'll try and get a colleague who's involved with this effort to join the call. |
@Swader |
Call happened! closing |
We need to schedule a follow-up meeting to expand on last week's discussion regarding the simulation working group and setting up a testnet for 1.x/2.0 development.
For the sake of time, we can quickly provision a testnet using the current Whiteblock framework. This can be a permissioned testnet which anyone can join. The network parameters and additional environmental configurations can be changed based on the needs of the participants. In order to get this testnet up and running, we first need to identify the network specifications and initial testing plan. An example test plan can be referenced here. This testnet can be used for both 1.x and 2.0 purposes or separate networks can be provisioned.
Further details for the setup and required specifications would be best covered during the call. I would like to schedule this call before Friday's meeting so we're not taking occupying too much time on the subject. Please respond if you would like to join this call and feel free to share your immediate thoughts on the matter, if appropriate.
I am proposing to schedule this call for Thursday (December 6) at 3:30PM (UTC), which is 7:30AM PST.
Thanks!
The text was updated successfully, but these errors were encountered: