Skip to content

feat: Add verified committee cache#317

Merged
itsyaasir merged 4 commits into
feat/poi-implementationfrom
feat/296-poi-committee-cache
Jul 13, 2026
Merged

feat: Add verified committee cache#317
itsyaasir merged 4 commits into
feat/poi-implementationfrom
feat/296-poi-committee-cache

Conversation

@itsyaasir

Copy link
Copy Markdown
Contributor

Summary

  • add an async CommitteeCache contract for trusted custom backends
  • provide an idempotent in-memory cache that rejects conflicting committees
  • let anchored committee resolution use a default or caller-provided cache
  • resume from authenticated cached committees and cache new committees only after checkpoint verification
  • keep trusted-node resolution separate from the anchored cache

Checkpoint summaries remain temporary verification material and are not retained. Persistent implementations can choose their own internal representation while preserving committee integrity and network separation.

Impact

Repeated anchored resolutions can avoid replaying committee lineage from the trust anchor. Applications may supply database, filesystem, browser, or other cache backends without moving network access into ProofVerifier.

Validation

  • cargo test -p poi-rs -- --test-threads=1
  • cargo check -p poi-rs
  • cargo clippy -p poi-rs --all-targets -- -D warnings
  • cargo doc -p poi-rs --no-deps
  • cargo fmt -p poi-rs -- --check
  • git diff --check

Closes #296

@itsyaasir itsyaasir marked this pull request as ready for review July 13, 2026 12:25
@itsyaasir itsyaasir merged commit 5176c43 into feat/poi-implementation Jul 13, 2026
12 of 13 checks passed
@itsyaasir itsyaasir deleted the feat/296-poi-committee-cache branch July 13, 2026 12:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant