docs: add rundler_getUserOperationGasPrice api spec#1159
docs: add rundler_getUserOperationGasPrice api spec#1159
Conversation
Co-Authored-By: Claude <noreply@anthropic.com>
🔗 Preview Mode
|
🔍 Link CheckStatus: ⏭️ Skipped (no content changes) |
This is not GA yet.Method is gated behind a waffle flag. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4d3b7c6b15
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| baseFee: "0x165a0bc00" | ||
| blockNumber: "0x12a3b4c" | ||
| suggested: | ||
| maxPriorityFeePerGas: "0x746a5280" | ||
| maxFeePerGas: "0x1dcd65000" |
There was a problem hiding this comment.
Align gas-price example with documented buffer calculation
The example values contradict the method description: maxFeePerGas is documented as “base fee with a 50% buffer plus suggested priority fee,” but with baseFee=0x165a0bc00 and maxPriorityFeePerGas=0x746a5280, the shown maxFeePerGas=0x1dcd65000 is much lower than that formula would produce. Because this is an API reference example, consumers who mirror these numbers can underprice user operations and see slower or failed inclusion.
Useful? React with 👍 / 👎.
Description
Related Issues
Changes Made
Testing
pnpm run validate)