Repository navigation
Background jobs keep their proofs private and offchain - #9
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013aDTfwQ3nirTB9pDCaFZmo
chrisjleal
marked this pull request as ready for review
October 20, 2026 18:35
…its three refusals in one place Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013aDTfwQ3nirTB9pDCaFZmo
chrisjleal
marked this pull request as draft
October 20, 2026 19:33
chrisjleal
marked this pull request as ready for review
October 20, 2026 19:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
User-facing change
Before: Proofs and the
proofable_verifypage said a blockchain record is optional, viaoptions.publishToHubortargetChains. They said nothing about background jobs.After: Proofs states the whole rule in one place. A background job keeps its proofs private and offchain, because nobody is present to ask and injected text could ask for more. A job's request is refused with these codes:
JOB_ONCHAIN_PUBLISH_DENIEDfor a blockchain record;JOB_PUBLIC_PROOF_DENIEDfor a public or link-only proof;JOB_VISIBILITY_CHANGE_DENIEDfor a visibility change.Each refusal points the reader to their own signed-in session. The
proofable_verifypage links to that rule rather than repeating it.Merge timing: the service refuses the on-chain request today. The public-proof and visibility refusals ship with the next service release, so this stays a draft until then.
Changelog
## [Unreleased]inCHANGELOG.md.How you checked it
npm run validatepasses on the branch.🤖 Generated with Claude Code
https://claude.ai/code/session_013aDTfwQ3nirTB9pDCaFZmo