Open
Conversation
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.
Description:
adds
Handler.authorizationRelay()— a handler that serves an/authorizepage for cross-domain access key authorization.problem
every mpp-powered app currently needs its own passkey wallet per domain (webauthn rpId limitation). users have to create a new wallet and fund it separately for each app. this kills adoption.
solution
a relay page that lets third-party apps authorize access keys against the user's existing tempo wallet via popup + postMessage.
flow:
tempo.xyz/authorize?keyAddress=0x...&hash=0x...postMessagesame pattern as
tempo wallet loginin the CLI — but for the browser.usage:
companion PR: wevm/wagmi —
crossDomainAccessKeyconnector wevm/wagmi#5027