add rsk_getSorageBytesAt method documentation

[ivegabr]

This pull request adds documentation for the new Rootstock-specific RPC method rsk_getStorageBytesAt to the developer docs. This method allows users to retrieve raw bytes from a contract's storage at a given address and block, supporting use cases such as bridge data inspection and retrieval of storage values larger than 32 bytes.

New RPC method documentation:

• Added a detailed section for the rsk_getStorageBytesAt method, including its purpose, parameters, notes on usage, and example requests/responses.## Title
• Clear and concise description of the change (e.g., "Docs: Add Tutorial for PowPeg Node Setup")

Description

• Purpose: Briefly explain the reason for this change.
• Context: Describe the issue resolved or the feature added.
• Changes: Summarize the specific updates made to the documentation.

Screenshots/GIFs

• Include any relevant visuals to demonstrate changes in layout or components.

Testing

• Verification: How did you test these changes? (e.g., ran yarn build or yarn check-links:external to check for broken internal / external links).
• Output: Paste any relevant terminal output or local build logs.
• Use N/A if not applicable.

Quality Checklist

• Please confirm the following standards have been met:

• Guidelines: I have read and followed the Contributing Guidelines.
• Vale Linter: I have run vale locally and resolved all Rootstock.Robotics and style warnings using .cursorrules or style guide vale automation.
• Rootstock Engineer Voice: I have removed AI-style "fluff" (e.g., unleash, delve into, testament to, ever-evolving landscape).
• Structural Clarity: I have replaced em dashes (—) with commas or periods and ensured there are no stacked headings.
• Code Quality: Technical comments are placed above the code line, not inline at the end.
• Terminology: I am using rBTC (not Smart Bitcoin) and Rootstock (not RSK).

Refs

• Related links to issues, tickets, or external discussions.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
devportal-rootstock	Ready	Preview, Comment	Mar 30, 2026 9:29am

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA ba96e03.

Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Files

[github-actions]

🔗 Broken Links/Anchors Found in en

The build found broken internal links or anchors.

🔗 Broken Links

- Broken link on source page path = /dev-tools/:
   -> linking to /resources/guides/superbridge/

⚓ Broken Anchors

---

How to fix:

1. Check if the linked page exists
2. Update the link to the correct URL
3. If the page was moved, update to the new location
4. If the page was deleted, remove the link
5. For anchors, verify the heading ID exists on the target page

[github-actions]

🔗 Broken Links/Anchors Found in en

The build found broken internal links or anchors.

🔗 Broken Links

- Broken link on source page path = /dev-tools/:
   -> linking to /resources/guides/superbridge/

⚓ Broken Anchors

---

How to fix:

1. Check if the linked page exists
2. Update the link to the correct URL
3. If the page was moved, update to the new location
4. If the page was deleted, remove the link
5. For anchors, verify the heading ID exists on the target page

[github-actions]

🔗 Broken Links/Anchors Found in en

The build found broken internal links or anchors.

🔗 Broken Links

- Broken link on source page path = /dev-tools/:
   -> linking to /resources/guides/superbridge/

⚓ Broken Anchors

---

How to fix:

1. Check if the linked page exists
2. Update the link to the correct URL
3. If the page was moved, update to the new location
4. If the page was deleted, remove the link
5. For anchors, verify the heading ID exists on the target page