The conversation revolves around the planning and execution of a development network (devnet) for a project, possibly a blockchain-based project given the references to "blocks" and "validator clients". The devnet, referred to as "devnet9", is a test environment used to simulate the real network before deploying it. The team is discussing various aspects of the devnet, including its timeline, potential issues, and solutions.
The team is considering whether to use the existing "whole ski" network for the first test net or to use another network like "gordy" or "sepolia". The decision is influenced by the fact that "whole ski" had issues during its launch, and the team wants to avoid similar problems. The team also discusses the possibility of running test net deployments on smaller networks with more nodes, which could provide more data on peer-to-peer related timing issues.
The conversation also touches on the topic of configuration changes, particularly in relation to adjusting the attestation timing window. The team has experienced issues when the validator client (VC) gets out of sync with the configuration changes in the beacon node. The team is exploring a better practice of pulling down configuration values from the beacon node instead of strictly respecting what's local to the VC.
Finally, there's a mention of a request to add a "blobside current event" in the beacon API, and the team is discussing whether this should be done sooner rather than later. Overall, the conversation is focused on ensuring the smooth execution of the devnet and addressing potential issues to ensure a successful deployment.
1. The text mentions a foreign language being spoken at certain time intervals.
2. There is a mention of a music track playing at various time intervals.
3. The speaker expresses frustration about opening OBS (Open Broadcaster Software) from the last session on the computer.
4. The speaker believes they may have caused an issue with streaming due to this.
5. The speaker thanks Tim for resolving the sound issue.
6. The speaker mentions that they had a configuration issue.
7. The speaker and other team members discuss a spec release for the neb Omega Sims player.
8. The team discusses a hotfix for broken tests in the consensus spec test repo.
9. The speaker and team discuss the timeline for devnet9, with the consensus being to start it the following week.
10. The speaker and team discuss potential issues with the contract deployment method.
11. The team discusses the need for lead time between Genesis and the fork for contract deployment.
12. The team discusses the potential need for scripts and processes to be updated for contract deployment.
13. The team discusses the need for clients to agree on the address for the system contract.
14. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
15. The team discusses the possibility of running through a manual process for contract deployment.
16. The team discusses the potential implications of deploying the contract at Genesis.
17. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
18. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
19. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
20. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
21. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
22. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
23. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
24. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
25. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
26. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
27. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
28. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
29. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
30. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
31. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
32. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
33. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
34. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
35. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
36. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
37. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
38. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
39. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
40. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
41. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
42. The team discusses the potential for a delay in updating the address in the latest release of the test suite.
43. The team discusses the potential for a delay in updating the address in the