docs: add spend permissions cookbook guide#1328
Open
erhnysr wants to merge 3 commits intobase:masterfrom
Open
Conversation
Adds a clarification note about using the correct RPC endpoint when building on Base.
wq qwqw ::::WQ :wq
Collaborator
🟡 Heimdall Review Status
|
Author
|
This cookbook guide focuses on the practical implementation of Spend Permissions. It’s designed to help developers build more seamless, 'one-click' experiences on Base by providing clear code examples and step-by-step logic. Ready for review! |
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
2 participants
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
Adds a new implementation guide for Spend Permissions within the Base Cookbook.
Changes
Detailed the 3-step lifecycle: Request, Approval, and Execution.
Provided a production-ready TypeScript code snippet for building permissions.
Included backend execution examples using viem/wagmi.
Why?
Spend Permissions are a key feature for improving UX in smart wallets. This guide helps developers implement seamless "one-click" or "gasless" experiences for their users.