fix: feegrant w curl

[jcstein]

Overview

Summary by CodeRabbit

• Documentation
  • Revised the guide to clarify the role of an address used in fee granting transactions.
  • Updated the parameter description to emphasize that this address now represents the recipient of permission, ensuring clearer instructions for users.
  • Left other fee transaction details unchanged.

[coderabbitai]

Walkthrough

This update revises the JSON request and its documentation for the feegrant feature. The key change is updating the signer_address field: it now references the $GRANTEE_ADDRESS rather than $GRANTER_ADDRESS. The corresponding parameter description is modified to indicate it represents the address being granted permission to use the granter's funds. The fee_granter_address remains unchanged, still indicating the address responsible for covering transaction fees.

Changes

File	Change Summary
how-to-guides/feegrant-for-blobs.md	- Updated signer_address to reference $GRANTEE_ADDRESS instead of $GRANTER_ADDRESS. - Revised its description from "the address granting the allowance" to "the address being granted permission to use the granter's funds". - fee_granter_address description retained.

Poem

I’m a rabbit quick on my feet,
Hopping through docs with a merry beat.
The signer now’s a grantee in our code’s tale,
Allowing funds with a freshly set sail.
Whiskers twitching in the digital breeze,
I cheer these changes with a joyful squeeze!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2773f73 and f37e663.

📒 Files selected for processing (1)

• how-to-guides/feegrant-for-blobs.md (2 hunks)

🔇 Additional comments (2)

how-to-guides/feegrant-for-blobs.md (2)

258-259: Updated "signer_address" Field in JSON Request
The change correctly updates the "signer_address" parameter to use "$GRANTEE_ADDRESS" instead of the granter’s address. This aligns with the intended role of the signer being the recipient of the fee allowance. Please verify that all other references (both in examples and command descriptions) maintain this consistency.

---

288-289: Revised Parameter Descriptions
The parameter description for signer_address now reads "the address being granted permission to use the granter's funds," which accurately reflects the new implementation. Ensure that this updated narrative is consistently applied throughout the document.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[Copilot]

Pull Request Overview

This PR updates the feegrant example by correcting the signer address in the curl command and updating the associated documentation.

• Updated the signer_address in the curl request from "$GRANTER_ADDRESS" to "$GRANTEE_ADDRESS"
• Adjusted the parameter description to accurately reflect that the signer_address represents the address being granted permission

[github-actions]

PR Preview Action v1.6.0
🚀 View preview at https://celestiaorg.github.io/docs-preview/pr-1965/
Built to branch main at 2025-03-31 21:26 UTC. Preview will be ready when the GitHub Pages deployment is complete.