Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Milestone 4 Report

Aperta
  • Qualcosa non va?
#23 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
20/100
Tipo di issue
Documentazione
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
prometheus
Ambito
documentation

Direzione di ricerca

Questo è un report di milestone, non un’attività di codice; inizia esaminando i criteri di accettazione, la roadmap collegata, la query di uptime di Prometheus e l’elenco degli stati di issue e pull request. Il lavoro è completato quando è disponibile un report pubblico completo con evidenze per ogni criterio e link alle attività pertinenti del progetto.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

This issue is meant to track progress on the acceptance criteria and evidence of milestone completion for M4.

Acceptance Criteria

The following is a breakdown of the acceptance criteria for M4, along with explanation as to how each have been satisfied.

The roadmap clearly outlines a strategy for moving from a centralized, MLabs hosted testnet, to a decentralized testnet maintained by the SPO community.

The roadmap outlines a strategy involving multiple phases, which are clearly outlined. (See link below.)

Interested SPOs will receive some marketing/promotional support on social media from us and will also benefit from community good will. That said, because SPOs are independent business operators we cannot guarantee that any number will be interested.

We have contacted numerous SPOs and provided support as outlined in the roadmap. However, no SPOs have shown interest in hosting the testnet thus far.

The roadmap is made public.

The roadmap is publically available (see link below).

SPOs and Cardano developers have been engaged and are aware of the congested testnet. We have released a series of 10 marketing posts across several channels promoting the project, following up with interested SPOs as needed.

We have engaged numerous SPOs and released 10 marketing posts (details below).

The testnet remains accessible throughout the duration of this milestone with at least 99% uptime for this 2 month period.

The average uptime over the last 60 days is greater than 99% (details below).

Evidence of Milestone completion

Link to public roadmap.

Congested Testnet Roadmap for Community Engagement and Adoption

List of any SPOs that have committed to maintaining the testnet going forward (if there are any at this point).

30 SPOs were reached out to, 9 responded in meaningful dialogue around hosting and 6 joined our Telegram support channel. But thus far none have committed to maintaining the testnet.

Links to social media posts where the community was engaged.

Twitter:

LinkedIn:

Youtube:

Telegram:

Discord:

NOTE: we also have a Telegram support channel we have been engaging SPOs
https://t.me/+3kNyHmpMwGc2ZDA1

PDF (or updated Gitbook) showing uptime for the duration of this milestone as well as progress on issues (issue names, current status, links to PRs with fixes, and reasons for any not addressed).

Due to the limited number of issues reported thus far, a separate PDF or Gitbook is unnecessary. Below are the uptime and issue details:

Uptime

Uptime for the congested testnet is being tracked using Prometheus. The following URL will show the average uptime over the 60 day period prior to 2025/04/21:

Congested Testnet 60 Day Avg. Uptime

The average uptime is 99.99521604938032%

Issue Progress

Below is a current breakdown of issues by status as of 2025/04/21.

Backlog
Completed

Relevant PRs for This Milestone

Lingua principale
Dhall
Stelle
4
Fork
0
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di mlabs-haskell/congested-testnet

Tutte le issue di mlabs-haskell/congested-testnet

Issue simili

Altre issue su Documentation

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.