Repository navigation
Conversation
Introduce a challenge-bound Web3 grant branch that authenticates pre-existing identities without user creation, with transactional nonce consumption and regression tests for concurrency and rollback. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
This branch has not been deployed
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.
Summary
POST /web3/challengeandexisting_user_onlyon the Web3 token grant for login without user creation.RFC / design discussion: #2915
Test plan
go test -p 1 -run '^(TestR8Web3ExistingOnly|TestWeb3|TestOtp|TestToken)$'on disposable Postgres (dev container)go build/go veton patched treemake docker-test/ race detector) — maintainer pipelineCompatibility
existing_user_onlydefaults tofalse).Notes
This is a draft for maintainer review per CONTRIBUTING; feedback on naming, privacy, and SDK exposure is welcome before merge.