Skip to content

Background jobs keep their proofs private and offchain #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chrisjleal merged 4 commits into from
Oct 20, 2026
Merged

Background jobs keep their proofs private and offchain #9

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9e04b89
Background jobs cannot request a blockchain record, and the docs say so.
claude Oct 20, 2026
518d7e3
Merge remote-tracking branch 'origin/main' into claude/marketplace-se…
claude Oct 20, 2026
2083280
Merge remote-tracking branch 'origin/main' into claude/marketplace-se…
claude Oct 20, 2026
efa6e46
Proofs: a background job keeps its proofs private and offchain, with …
claude Oct 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ Product release notes: [docs.proofable.me/changelog](https://docs.proofable.me/c

- **Changelog entries for `@proofable/mcp` 0.1.7 and `@proofable/sdk` 0.1.6.**
- **Eligibility clause in the Terms of Use.** Section 4 states the minimum age and the capacity to contract. The Terms had no eligibility or age statement before.
- **Background jobs keep proofs private and offchain.** [Proofs](/proofs) says that a background job's request for a blockchain record, a public or link-only proof, or a visibility change is refused with `JOB_ONCHAIN_PUBLISH_DENIED`, `JOB_PUBLIC_PROOF_DENIED` or `JOB_VISIBILITY_CHANGE_DENIED`.

### Changed

Expand Down
2 changes: 1 addition & 1 deletion mcp/verify.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ When signed in, **omit `walletAddress`**. The tool uses your profile account fro
| `chain` | No | CAIP-2 chain when needed |
| `signedTimestamp` | No | Optional timestamp for direct creation or preparation |
| `options.returnUrl` | No | Where to send the user if a hosted step is needed |
| `options.publishToHub` | No | Record the proof on the hub chain. Offchain by default. Does not change who can see the proof. |
| `options.publishToHub` | No | Record the proof on the hub chain. Offchain by default. Does not change who can see the proof. A background job's request is refused ([Proofs](/proofs)). |

```json
{ "verifierIds": ["ownership-basic"], "data": { "content": "Hello Proofable" } }
Expand Down
2 changes: 2 additions & 0 deletions proofs.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,8 @@ Unlisted proofs are public to anyone who has the proof ID. To share a private pr

Proofs are stored offchain by default. A blockchain record is optional: request it with `options.publishToHub: true` or `targetChains`. IPFS pinning is optional with `enableIpfs: true`. Neither changes who can read the proof, and neither replaces a status check.

A background job keeps its proofs private and offchain. Nobody is present to ask, and its prompt or a page it reads can carry injected instructions, so a job's request for a blockchain record, a public or link-only proof, or a visibility change is refused (`JOB_ONCHAIN_PUBLISH_DENIED`, `JOB_PUBLIC_PROOF_DENIED`, `JOB_VISIBILITY_CHANGE_DENIED`). Publish from your own signed-in session instead.

## Reuse

Before a protected action, check the current proof instead of repeating the original check. [Reuse verification](/use-cases/reuse-verification)
Expand Down
Loading