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

[Milestone] Testnet #26

Open
Cofson opened this issue Apr 4, 2024 · 0 comments
Open

[Milestone] Testnet #26

Cofson opened this issue Apr 4, 2024 · 0 comments

Comments

@Cofson
Copy link
Collaborator

Cofson commented Apr 4, 2024

Testnet

The testnet does not need much explanation. It is intended to establish a continuous development process by which each iteration will be released to the testnet, and available to use. Initially this will remain internal, and at some point it will be made public. This can best be done when all the subprojects in this document have been developed far enough that they provide a cohesive functionality.

When the Testnet is made publicly available, we expect an increased time dedication to handle issues, fixes and community.

Estimated Delivery Date

This is a continuous project. It is already live and it will see consistent improvement.

Resources Required

Currently we have two developers contributing to it most actively:

  • DevOps: Gusto.
  • Peripheral functionality to make the testnet usable: Al.

Servers for testnet:

  • 500€/m (currently at 40€/m)
    • Used for deploying the Nomos Base Layer Testnet. Currently this is not public. For now the main functionality is to establish CI/CD processes and test the setup internally.
    • End of the year / Early 2025, we plan to turn this Testnet public.

Deliverables

The testnet itself, which serves as a backbone for other deliverables, is the deliverable itself.

  • Intended audience: both internal and external. Externally it serves as a way to show progress and for the community to test it.

Tracking Metrics

In progress:

  • Github commits (node implementation)
  • Weekly progress reports
  • Functioning Testnet that integrates the latest iteration's code changes.

Work Breakdown

This is pretty much ad-hoc, as it reflects the last mile of development. When base functionality is ready to be deployed to the Testnet, it is likely that some interface needs to be added to interact with it. I consider this work part of the Testnet subproject, and it is always defined after the functionality is ready. An example of this is the chat application, which serves to showcase a trimmed-down data availability layer (ie no cryptography or sharding involved).

Perceived Risks

Nothing worth noting here.

@Cofson Cofson changed the title Testnet [Milestone] Testnet Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant