Enhance UX documentation for wallet_sendCalls usage#1
Open
Enhance UX documentation for wallet_sendCalls usage#1
Conversation
The current docs show wallet_sendCalls examples without warning that calling it directly via raw RPC bypasses Auto Spend Permissions entirely. The "skip further approval" UI silently never appears with no error thrown, making this very hard to debug. Added a warning to prevent developers from hitting this.
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.
The current docs show
wallet_sendCallsexamples without warning that calling it directly via raw RPC bypasses Auto Spend Permissions entirely. The "skip further approval" UI silently never appears with no error thrown, making this very hard to debug.What changed? Why?
Added a
<Warning>block in the Send transactions section to make it clear that usingwallet_sendCallsvia raw RPC bypasses the Auto Spend Permissions flow. Developers should useuseWriteContractoruseSendCallswith the Base Account connector instead.Notes to reviewers
This is a docs-only change. No code was modified.
How has it been tested?
This is a documentation-only change adding a warning block. The issue itself was reproduced by a developer integrating sub accounts with RainbowKit who spent significant time debugging why Auto Spend Permissions were silently not triggering despite correct SDK configuration. The root cause was confirmed to be raw
wallet_sendCallsusage bypassing the Base Account execution flow.