docs(validator): close remaining operator-truth gaps - #158
Conversation
The operator guide said the validator accepted every signed vector shape by default, but the shipped CLI pins validated_supply_v1. Correct the guidance so confidential-primary operators know they must opt into that policy explicitly.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_1b59a9db-a7d3-455c-9baf-2b418f98db1c) |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b923b66a27
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| # CLI flag or env. The default pins validated_supply_v1, which rejects a plain | ||
| # confidential_primary or v3 vector. Set this explicitly to accept confidential_primary. |
There was a problem hiding this comment.
Update the paragraph immediately below this example as part of the default-pin correction. It still says that validators which do not set the pin accept all signed shapes, but scaffold/cli.py supplies validated_supply_v1 by default and rejects an empty policy, so omitting the option actually rejects plain confidential-primary and v3 vectors as these new lines state. This contradiction can lead operators to omit the explicit confidential_primary_v1 opt-in and have their vectors rejected.
Useful? React with 👍 / 👎.
Date the last reproduced verifier mismatch, require a fresh live reproduction before broadcast, remove the last operator-facing authority-gate reference, and state the exact confidential-primary policy and Finney broadcast boundary.
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_4a2d7621-2ec3-495c-bb9a-2dc62ac8c97c) |
wallscaler
changed the title
The earlier FAIL and later AGREE records describe different deployments, and the live endpoint did not answer this review. Report NOT PROVEN and keep broadcast gated on a fresh reproduction.
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_2d21d10a-f9b4-4559-ba80-d4dee8ed798b) |
Avoid implying that a mismatch is presently observed while the live agreement status remains NOT PROVEN.
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_d7efe15b-0a0e-4e32-88fc-e0811d404b89) |
1 participant
Outcome targets
validated_supply_v1.confidential_primary_v1is described as an explicit validation pin, not a Finney SN39 broadcast profile.NOT PROVEN, with broadcast blocked until a fresh live reproduction passes.What changed
validated_supply_v1orvalidated_supply_v3.FAILclaim withNOT PROVEN. A priorFAILand laterAGREEdescribe different deployments, while no fresh live reproduction passed in this review.Evidence
scaffold/cli.pydefaultsrequire_policytovalidated_supply_v1.validated_supply_v1orvalidated_supply_v3.git diff --check: passed.scalecodecandcyscalenamespace conflict. GitHub Linux CI is the test gate.Merge gate
Merge only if required GitHub tests pass, the reviewed head remains unchanged, and no P0, P1, or P2 review finding appears.
Supersession
This preserves the valid facts from PR #145 without restoring deleted
MINER_VALIDATOR.md, reintroducing authority guidance, or weakening the broadcast block.