Skip to content

Tell the truth about CyberGym attestation and stay down on a contradiction - #144

Draft
wallscaler wants to merge 3 commits into
mainfrom
docs/honest-cybergym-and-stay-down
Draft

Tell the truth about CyberGym attestation and stay down on a contradiction#144
wallscaler wants to merge 3 commits into
mainfrom
docs/honest-cybergym-and-stay-down

Conversation

@wallscaler

Copy link
Copy Markdown
Contributor

Summary

  • Rewrite MINER_VALIDATOR.md from the shipped code. The CyberGym check is Cathedral Ed25519 over a customer receipt, not Intel DCAP. Default: record failure, pay anyway.
  • Add docs/CYBERGYM_LANE.md: what the composer does, the four off switches, and the hard rule. Do not set CATHEDRAL_ALLOCATION_CONTRACT=v3 until distill refuses public-catalog task_ids.
  • #114: PENDING_RECEIPT_CONTRADICTION now exits 3. The SN39 unit sets RestartPreventExitStatus=3 so systemd does not restart the writer against its own stay-stopped remediation.
  • #125: public status now says an aged-out tip needs docs/PROVENANCE_CATCHUP.md. The catch-up itself is still an operator action. This PR does not re-anchor production.

Distill (note, do not flip past)

v3 and CyberGym payout stay off. A v3 flip without a posting producer fails the whole weight vector.

Test plan

  • test_recurring_loop_exits_on_post_signed_contradiction expects exit 3
  • CyberGym attestation unit tests
  • public status tests
  • CI on the draft PR
  • Deploy the unit drop-in / service file before relying on stay-down in production (cathedral-validator-passive.service on the host still needs the same RestartPreventExitStatus=3)

Made with Cursor

…ction.

The docs claimed every validator DCAP-verifies CyberGym. The code checks
Cathedral's Ed25519 signature and pays on failure. v3 stays off until
distill refuses public catalog task ids. A receipt contradiction now exits 3
so systemd does not restart the writer.

Co-authored-by: Cursor <cursoragent@cursor.com>
wallscaler and others added 2 commits August 22, 2026 08:48
Exit 3 now stops the relay unit and the Docker writer. Pending-receipt
recovery keeps retrying. Catch-up text is only for an aged-out tip.

Co-authored-by: Cursor <cursoragent@cursor.com>
Git maintenance can create and delete objects/maintenance.lock during the
chmod walk. That race is not a relay-install failure.

Co-authored-by: Cursor <cursoragent@cursor.com>
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