docs: bso automatic retries fee estimation update#1222
Open
avarobinson wants to merge 3 commits intomainfrom
Open
docs: bso automatic retries fee estimation update#1222avarobinson wants to merge 3 commits intomainfrom
avarobinson wants to merge 3 commits intomainfrom
Conversation
Enhance Bundler Sponsored Operations (BSO) documentation to clearly emphasize the automatic retry and fee management benefits: - bundler-sponsored-operations.mdx: Add prominent callout at the top, new 'Automatic retries and fee management' section explaining how the bundler handles fees under the hood, comparison table vs standard fee management, and updated benefits list with fee/retry advantages - bundler-api-quickstart.mdx: Add tip callout highlighting BSO as a way to skip fee estimation entirely - bundler-api-fee-logic.mdx: Add tip at the top directing readers to BSO as a simpler alternative, and a tip after the fee calculation steps - bundler-faqs.mdx: Add contextual tips in 'How can I track the status of a userOp', 'How do I get my userOp unstuck', and 'precheck failed' sections pointing to BSO as the solution to these common pain points Requested-by: https://alchemyinsights.slack.com/archives/D0ASNFCHFFH/p1776266036508709
…nd-replace claims
Refine Bundler Sponsored Operations documentation to be more accurate
and conservative in its claims:
- bundler-sponsored-operations.mdx: Remove the "Bundler sponsorship vs.
standard fee management" comparison table, remove the "Why this matters"
section that repeated fee estimation steps, replace drop-and-replace
claims with "no guarantee" language, simplify section headings
("How it works" instead of "How it works under the hood"), and
tighten the benefits list
- bundler-api-quickstart.mdx: Soften tip from "eliminate fee estimation
entirely" to "skip fee estimation", remove drop-and-replace mention
- bundler-api-fee-logic.mdx: Soften tip title and language, remove
"eliminate" phrasing
- bundler-faqs.mdx: Replace "eliminate this problem entirely" with
"can help with this", replace "avoid precheck failed" with "can help
avoid", add "no guarantee" qualifiers, use "consider" instead of
"use" for softer recommendation tone
Requested-by: https://alchemyinsights.slack.com/archives/D0ASNFCHFFH/p1776351910484719
🔗 Preview Mode
|
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.
Description
Related Issues
Changes Made
Testing
pnpm run validate)