Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Review version variance across clients

未关闭
#211 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
28/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
go
领域
backend

调研方向

首先检查 crawler 当前的客户端和 User-Agent 检测行为,然后阅读与 Lodestar 更新相关的、已链接的 eth2-crawler 和 Lodestar issue。当 Prysm 和 Nimbus 节点得到更准确的分类、检测到使用更新后 User-Agent 的 Lodestar,并且 unknown 或 others 分组减少为有意义的结果时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

Expected Behavior

Currently the crawler is pulling a count for the version variaance across clients seems to be scraping well. However, there are some improvements that can be made. Ideally, we should be able to categorize as many nodes into their proper {client}{version} categories.

Current Behavior

For example, in Prysm there is a group of prysm unknown and prysm others which is generally meaningless and we should figure out why.

Nimbus is also not being properly detected as they are all grouped under unknown. We can liaise with them to figure out how to best detect them.

Lodestar's UserAgent needs to be updated. See https://github.com/ChainSafe/eth2-crawler/issues/200 and https://github.com/ChainSafe/lodestar/issues/4465

Possible Solution

Let's implement the UserAgent update for detecting Lodestar and figure out how we can more accurately represent the other clients to the most accurate numbers as possible.

主要语言
Go
星标
60
派生
31
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ChainSafe/nodewatch-api 的其他 Issue

查看 ChainSafe/nodewatch-api 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。