docs: clarify what Base Verify Onchain writes onchain - #1834
Merged
Conversation
- Add a "What goes onchain" section covering the exact fields a claim publishes, what never touches the chain, and what an observer can infer from a public policy plus a public claim - Note that verify.base.dev shows offchain credentials only, and that onchain claim history lives in the partner app's contract - Mark Base Verify Onchain as Base Sepolia only, not on mainnet
Collaborator
✅ Heimdall Review Status
|
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
soheimam
approved these changes
Aug 19, 2026
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
3 participants
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.
What changed? Why?
The Base Verify Onchain guide explained that
identityHashis one-way and per-contract, but never stated what a claim actually makes permanently public, or where onchain claim history lives.identityHash, the claiming wallet,expiration, the signature, and the contract's publicprovider/conditions), what never touches the chain, and what an observer can infer by pairing a public policy with a public claim.verify.base.devsurfaces offchain credentials only. Onchain claim history lives in the partner app's contract storage and cannot be viewed or undone there, including after a user deletes their verification.Notes to reviewers
Claims were checked against the deployed contracts rather than the existing docs. Worth a look: the example consumers emit
Claimed(address indexed user, bytes32 indexed identityHash), which makes the wallet-to-hash pairing queryable straight from logs. That was undocumented and it is the sharpest disclosure on the page.How has it been tested?
node scripts/lint-mdx.json both files. The "code block missing language specifier" errors it reports are pre-existing on closing fences in both files and unrelated to this change, which adds no code blocks.#what-goes-onchainanchor and the new cross-link to/apps/guides/verify-onchainboth resolve.