Document 51Did creator context verification - #221
Open
jwrosewell wants to merge 3 commits into
Open
Conversation
…tates Describe context verification alongside signature verification: what it confirms (same device the identifier was created on), the three verify endpoints and their JSON, the context result values, the combined signature/context states, the must-call-from-the-browser rule, and the render-time use case. Outcome-level only.
Contributor
Add the verify-context and verify-full response shapes, the resource-key and metering requirement, and the diagnostic factor block. Clarify that a verified context cannot be forged by tampering.
jwrosewell
marked this pull request as ready for review
July 18, 2026 17:12
Name the check "creator context" verification (context for short) in the identifier docs so it is clear what the context is. Endpoint and field names are unchanged.
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.
Documents creator context verification (context for short) alongside the existing signature verification in the 51Did identifier docs.
What
invalid)./verify, context-only/verify-context, and combined/verify-full. All three require a Resource Key and are metered (401 without a key, 403 without the entitlement).contextresult values (verified / invalid / absent / indeterminate) and the combined signature+context states, including that a verified context cannot be forged by tampering.factorsblock (transport / device / network), returned when the context does not cleanly verify, to help locate an integration problem. Neutral labels only.Outcome-level only: describes what is checked and what each result means, not how it works. The published payload layout table is unchanged.