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

[FEATURE] Sequencer admin contract to encapsulate keys (and namespace) within execution client state root

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
rust
领域
blockchain

调研方向

该 issue 中没有指出任何文件、测试或入口点。首先检查 execution client state root 当前如何与 sequencer namespace 和 public key 相关联,然后考察现有的 staking contracts 是否能够表示这些字段;完成意味着达成一项约定的实现,使 state root 能够提供这两个值,并支持所提出的验证变更。

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

描述

enhancement

Is your feature request related to a problem? Please describe.

Yes, we would like to encapsulate the public key of the sequencer within the state root of the execution client to avoid having to validate it independently for proving state transition and data availability.

Furthermore, this design lends itself to support key rotation for the sequencer software. Which is an issue independent of this, but it would be great to kill two birds with one stone.

Describe the solution you'd like

Spoke with @tac0turtle about requesting the state root to include the sequencer's public key as well as the namespace it posts data to.

He mentioned that it could be possible to use existing staking contracts.

Describe alternatives you've considered

Currently we verify the namespace and public key of the sequencer independently of the execution client state root. But ideally we can reduce it to only the state root if those fields are encapsulated within it.

Additional context

n/a

主要语言
Rust
星标
8
派生
9
平均合并
7 小时 25 分钟
30 天内合并 PR
2

环境准备

从这里开始

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

evstack/ev-reth 的其他 Issue

查看 evstack/ev-reth 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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