creating docs -- dev-tools/wormhole-messaging#494
Open
swarnasn29 wants to merge 1 commit into
Open
Conversation
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
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.
Title
Docs: Add Wormhole Cross-Chain Messaging Integration Guide
Description
Purpose: Close the documentation gap for developers who want to use Wormhole's arbitrary message passing on Rootstock. The existing Wormhole page only covers the SDK tooling overview (Connect, Queries,
TypeScript SDK). There was no guide explaining how to receive and verify cross-chain messages on-chain.
Context: New builders targeting Rootstock with Wormhole had no clear integration path for Verified Action Approvals (VAAs). This guide solves that cold-start problem end-to-end.
Changes:
Core Contract deployment
Screenshots/GIFs
N/A — text and code documentation only. Verified visually via local Docusaurus dev server at http://localhost:3000/dev-tools/cross-chain-bridges/wormhole-messaging/.
Testing
Verification: Started the local Docusaurus dev server to confirm the page renders correctly and appears in the sidebar.
npm start -- --no-open
Output:
[INFO] Starting the development server...
[SUCCESS] Docusaurus website is running at: http://localhost:3000/
Confirmed:
Quality Checklist
Guidelines: I have read and followed the Contributing Guidelines.
Vale Linter: I have run vale locally and resolved all
Rootstock.Roboticsand style warnings using.cursorrulesor 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) andRootstock(not RSK).Refs