mlabs-haskell / mlabs-haskell/congested-testnet

Milestone 4 Report

Open
#23 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Dhall
Stars
4
Forks
0
PR merge metrics
No merged PRs in 30d

Description

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This is a milestone report rather than a code task; start by reviewing the acceptance criteria, linked roadmap, Prometheus uptime query, and issue and pull request status list. Done is a complete public report with evidence for each criterion and links to the relevant project activity.

Written by the indexing model from the issue text.

Assessment

Tech stack
prometheus
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.