Clarify when to use Proxy vs Safe examples #13
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
1 participant
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.
Add a short note on when to use Proxy vs Safe examples (email/Magic vs browser wallets).
Clarify that both example flows expose the same market interactions and mainly differ in how transactions are authorized and signed.
Note
Clarifies README on when to use Proxy vs Safe examples (email/Magic vs browser wallets), noting equivalent interactions and differing auth/signing, plus a minor code block formatting fix.
README.mdto clarify when to useProxy(email/Magic) vsSafe(browser wallets) examples.Written by Cursor Bugbot for commit 2ba51dd. This will update automatically on new commits. Configure here.