-
Notifications
You must be signed in to change notification settings - Fork 2
Tighten v1 security invariants and define the trusted-computer boundary #4
Copy link
Copy link
Open
Labels
area: securitySecurity invariants, hardening, and security-sensitive boundaries.Security invariants, hardening, and security-sensitive boundaries.documentationImprovements or additions to documentationImprovements or additions to documentationgate: adversarial reviewResolve, merge, or explicitly defer before the next full adversarial review.Resolve, merge, or explicitly defer before the next full adversarial review.
Description
Activity
Metadata
Metadata
Assignees
Labels
area: securitySecurity invariants, hardening, and security-sensitive boundaries.Security invariants, hardening, and security-sensitive boundaries.documentationImprovements or additions to documentationImprovements or additions to documentationgate: adversarial reviewResolve, merge, or explicitly defer before the next full adversarial review.Resolve, merge, or explicitly defer before the next full adversarial review.
The v1 security documentation needs one literal, consistent trusted-computer and secret-output contract.
Required contract:
bitcoin-cli/Bitcoin Core and relevant configuration trusted for the operation;Implemented in focused PR #59. The final refreshed head
ede98a8is mergeable, has resolved review threads, passed exact-head Python-package run 643 and Bitcoin Core wallet-fixture run 30, and has a current-head Codex release-gate ACK. The refreshed wording is reconciled with #23 and the #57/#80/#81 restore contract.Keep this issue open through human integration of #59; no automated/code-review gap remains.