The audit trail never rotates and verification is linear in its length

未关闭
  • 哪里不对？
#359 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
活跃
技术栈
go
领域
documentation

调研方向

Start by locating the audit trail documentation and verification entry points; the issue does not name specific files or tests. Document a verifiable way to close one segment and begin another, including how the chain connects across segments and the expected verification cost at large sizes. Done when users can follow the rotation practice and understand its verification cost.

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

描述

enhancement

Observed. The trail is one file that only grows. Verifying 18,401 records took 1.9 s; the cost grows with the file. There is no documented practice for closing a segment and starting the next while keeping the chain verifiable across segments.

Ask. A documented, verifiable rotation or segment practice for a long-lived trail, and a statement of the expected verify cost at large sizes.

Found in an end-to-end trial of the released binaries (Runtime v0.40.0). Verified by running.

主要语言
Go
星标
2
派生
6
平均合并
2 小时 11 分钟
30 天内合并 PR
63

环境准备

从这里开始

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

Judgment-Pack/judgment-pack-runtime 的其他 Issue

查看 Judgment-Pack/judgment-pack-runtime 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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