Certificate chain optimization

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

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
backend, database

调研方向

The issue names no files, so start from the existing epoch-based retention for stake pools, epoch settings and signer registrations, and look for how the aggregator's certificate table is read and written. Decide which signed entity types are protected, such as Cardano stake distributions, and which can be pruned after N epochs. Done means eligible certificates are removed after a configurable N, protected ones remain, and tests cover both cases.

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

描述

roadmap :compass:

Why

The Mithril certificate chain grows without bound. Every epoch produces multiple certificates ( one per signed entity type) and none are ever removed. On the aggregator side, no pruning mechanism exists for certificates, unlike stake pools, epoch settings, and signer registrations which all have epoch-based retention policies.
This means the certificate table grows permanently, increasing storage requirements and query latency over time.

Not all certificates have the same retention requirements. Some must be kept indefinitely. For example, Cardano stake distribution certificates are referenced by other systems and cannot be discarded. Others, such as Cardano database snapshot certificates or Cardano transaction certificates, are only relevant for a limited time window and can be safely removed after a configurable number of epochs.

The goal of this MVP is to deliver production-ready certificate chain pruning on the aggregator: certificates for eligible signed entity types are automatically removed after N epochs (where N is configurable), while certificates for protected entity types such as Cardano stake distributions are retained indefinitely. This bounds the aggregator's storage growth and reduces query latency.

主要语言
Rust
星标
155
派生
52
平均合并
2 天 17 小时
30 天内合并 PR
37

环境准备

从这里开始

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

IntersectMBO/mithril 的其他 Issue

查看 IntersectMBO/mithril 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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