On Recovery, the node must set the minimum TCB to the minimum of the current value in the KV and the one found in startup attestation
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 876
- Forks
- 260
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 157
Description
When a node is started in Recovery mode, as opposed to Start mode where the behaviour must remain unchanged, instead of systematically setting the minimum TCB to the value found in the new node's attestation, the logic should instead read the previously set value if there is one.
If present, then the minimum of that value and the value found on startup must be set. If no value was set, we must continue to set the value found in the attestation on startup, as we do today.
This change needs to be included in the changelog.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the node startup and recovery-mode logic that sets the minimum TCB, then trace how the value is read from and written to the KV. Compare Recovery with Start behavior and inspect existing attestation-related tests. Done means Recovery preserves the lower of the stored and startup-attested TCB, Start remains unchanged, and the changelog is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100