Skip to content
This repository was archived by the owner on Dec 8, 2025. It is now read-only.

Conversation

@bguiz
Copy link
Contributor

@bguiz bguiz commented Nov 17, 2025

Summary by CodeRabbit

  • Documentation
    • Added a new EVM integrations cheat sheet to the developer docs covering network configuration (including chain identifier and deprecation note), explorers (GUI and API references), recommended and alternative RPC endpoints, major contract addresses, bridge integration guidance, wallet support options, oracle providers, reference links, and usage snippets.

@coderabbitai
Copy link

coderabbitai bot commented Nov 17, 2025

Walkthrough

Added a new EVM Integrations Cheatsheet markdown file and updated the documentation table of contents to include a link to that cheat sheet under EVM Developers.

Changes

Cohort / File(s) Summary
Documentation Index
.gitbook/SUMMARY.md
Added "EVM Integrations Cheatsheet" entry to the EVM Developers section in the table of contents.
New EVM Integration Reference
.gitbook/developers-evm/integrations-cheat-sheet-evm.md
Added a comprehensive cheat sheet covering network config (chain ID 1776, deprecation note), explorers, RPC endpoints (recommended vs not recommended), contract addresses (USDT, wETH, wINJ, USDC, MultiCall), bridges, wallets (injectived, MetaMask, Keplr), oracles (Api3, Pyth, Chainlink), reference links, code snippets, and some TODO/duplicated sections.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

  • Verify accuracy of chain ID, RPC endpoints, and listed contract addresses.
  • Validate external reference URLs and guide links.
  • Resolve duplicated MetaMask text and any TODO markers or placeholder images.
  • Skim for clarity and consistency with existing docs formatting.

Poem

🐰 I hopped through docs with nimble feet,
A cheatsheet nest I stitched so neat,
Chains and wallets in a row,
Contracts, RPCs — ready to go! 🚀

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: adding a new EVM integrations cheat sheet document to the documentation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch docs/integ-cheat-sheet

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Nitpick comments (1)
.gitbook/developers-evm/integrations-cheat-sheet-evm.md (1)

100-100: Resolve TODO markers before merge.

The <!-- TODO img --> and <!-- TODO image --> comments indicate incomplete work. Clarify the intention: should these be placeholders for screenshot assets, or should the instructions be refined?

Before merging, please either:

  1. Add the referenced image/screenshot asset, or
  2. Remove the TODO and finalize the instructions as-is, or
  3. Link to an existing screenshot resource if available.

Also applies to: 109-109

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d8e95f8 and f26fde4.

📒 Files selected for processing (2)
  • .gitbook/SUMMARY.md (1 hunks)
  • .gitbook/developers-evm/integrations-cheat-sheet-evm.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
.gitbook/developers-evm/integrations-cheat-sheet-evm.md

[grammar] ~76-~76: Use a hyphen to join words.
Context: ...rammatic control, e.g. application/ DApp operated accounts. Installation quick s...

(QB_NEW_EN_HYPHEN)

🪛 markdownlint-cli2 (0.18.1)
.gitbook/developers-evm/integrations-cheat-sheet-evm.md

29-29: Unordered list indentation
Expected: 2; Actual: 1

(MD007, ul-indent)


29-29: Hard tabs
Column: 1

(MD010, no-hard-tabs)


30-30: Unordered list indentation
Expected: 2; Actual: 1

(MD007, ul-indent)


30-30: Hard tabs
Column: 1

(MD010, no-hard-tabs)


31-31: Unordered list indentation
Expected: 2; Actual: 1

(MD007, ul-indent)


31-31: Hard tabs
Column: 1

(MD010, no-hard-tabs)


32-32: Unordered list indentation
Expected: 2; Actual: 1

(MD007, ul-indent)


32-32: Hard tabs
Column: 1

(MD010, no-hard-tabs)


33-33: Unordered list indentation
Expected: 4; Actual: 2

(MD007, ul-indent)


33-33: Hard tabs
Column: 1

(MD010, no-hard-tabs)


34-34: Unordered list indentation
Expected: 4; Actual: 2

(MD007, ul-indent)


34-34: Hard tabs
Column: 1

(MD010, no-hard-tabs)


36-36: Unordered list indentation
Expected: 2; Actual: 1

(MD007, ul-indent)


36-36: Hard tabs
Column: 1

(MD010, no-hard-tabs)


37-37: Unordered list indentation
Expected: 2; Actual: 1

(MD007, ul-indent)


37-37: Hard tabs
Column: 1

(MD010, no-hard-tabs)


38-38: Unordered list indentation
Expected: 2; Actual: 1

(MD007, ul-indent)


38-38: Hard tabs
Column: 1

(MD010, no-hard-tabs)


39-39: Unordered list indentation
Expected: 2; Actual: 1

(MD007, ul-indent)


39-39: Hard tabs
Column: 1

(MD010, no-hard-tabs)


40-40: Unordered list indentation
Expected: 4; Actual: 2

(MD007, ul-indent)


40-40: Hard tabs
Column: 1

(MD010, no-hard-tabs)


41-41: Unordered list indentation
Expected: 4; Actual: 2

(MD007, ul-indent)


41-41: Hard tabs
Column: 1

(MD010, no-hard-tabs)


101-101: Multiple headings with the same content

(MD024, no-duplicate-heading)

🔇 Additional comments (2)
.gitbook/developers-evm/integrations-cheat-sheet-evm.md (1)

1-90: Overall structure and content look good.

The cheatsheet provides clear organization and comprehensive coverage of key integration points (network config, explorers, RPC endpoints, contract addresses, bridges, wallets, and oracles). The deprecation notes for InEVM are helpful, and references to canonical documentation are well-placed.

Address the formatting and duplication issues flagged above, and the document will be ready.

Also applies to: 110-131

.gitbook/SUMMARY.md (1)

138-138: Table of contents entry is well-positioned and correctly formatted.

The new "EVM Integrations Cheatsheet" entry is properly placed in the EVM Developers section with correct path reference and formatting. The placement after "EVM Network Information" makes logical sense.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

♻️ Duplicate comments (1)
.gitbook/developers-evm/integrations-cheat-sheet-evm.md (1)

28-41: Hard tabs and indentation issues remain unfixed from previous review.

Static analysis continues to flag hard tabs (MD010) and incorrect list indentation (MD007) in the RPC Endpoints section. This was previously raised and needs to be corrected—replace all hard tabs with spaces and use consistent 2-space indentation for top-level list items and 4-space for nested items as per Markdown standards.

🧹 Nitpick comments (1)
.gitbook/developers-evm/integrations-cheat-sheet-evm.md (1)

3-3: Minor: Improve formatting of slash-separated items.

The line uses "build/ deploy/ integrate" with spaces after slashes. Consider using a more consistent format such as "build/deploy/integrate" or the more readable "build, deploy, or integrate" for better readability.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f26fde4 and 17f6771.

⛔ Files ignored due to path filters (1)
  • .gitbook/.gitbook/assets/blockscout-add-injective-button.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • .gitbook/developers-evm/integrations-cheat-sheet-evm.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.18.1)
.gitbook/developers-evm/integrations-cheat-sheet-evm.md

29-29: Unordered list indentation
Expected: 2; Actual: 1

(MD007, ul-indent)


29-29: Hard tabs
Column: 1

(MD010, no-hard-tabs)


30-30: Unordered list indentation
Expected: 2; Actual: 1

(MD007, ul-indent)


30-30: Hard tabs
Column: 1

(MD010, no-hard-tabs)


31-31: Unordered list indentation
Expected: 2; Actual: 1

(MD007, ul-indent)


31-31: Hard tabs
Column: 1

(MD010, no-hard-tabs)


32-32: Unordered list indentation
Expected: 2; Actual: 1

(MD007, ul-indent)


32-32: Hard tabs
Column: 1

(MD010, no-hard-tabs)


33-33: Unordered list indentation
Expected: 4; Actual: 2

(MD007, ul-indent)


33-33: Hard tabs
Column: 1

(MD010, no-hard-tabs)


34-34: Unordered list indentation
Expected: 4; Actual: 2

(MD007, ul-indent)


34-34: Hard tabs
Column: 1

(MD010, no-hard-tabs)


36-36: Unordered list indentation
Expected: 2; Actual: 1

(MD007, ul-indent)


36-36: Hard tabs
Column: 1

(MD010, no-hard-tabs)


37-37: Unordered list indentation
Expected: 2; Actual: 1

(MD007, ul-indent)


37-37: Hard tabs
Column: 1

(MD010, no-hard-tabs)


38-38: Unordered list indentation
Expected: 2; Actual: 1

(MD007, ul-indent)


38-38: Hard tabs
Column: 1

(MD010, no-hard-tabs)


39-39: Unordered list indentation
Expected: 2; Actual: 1

(MD007, ul-indent)


39-39: Hard tabs
Column: 1

(MD010, no-hard-tabs)


40-40: Unordered list indentation
Expected: 4; Actual: 2

(MD007, ul-indent)


40-40: Hard tabs
Column: 1

(MD010, no-hard-tabs)


41-41: Unordered list indentation
Expected: 4; Actual: 2

(MD007, ul-indent)


41-41: Hard tabs
Column: 1

(MD010, no-hard-tabs)


101-101: Multiple headings with the same content

(MD024, no-duplicate-heading)

🔇 Additional comments (2)
.gitbook/developers-evm/integrations-cheat-sheet-evm.md (2)

76-76: Verify semantic intent of grammar change on line 76.

The line was changed from "application/ DApp operated accounts" to "application or dApp-operated accounts." While the hyphenation is now correct, the semantic meaning has shifted from "application/DApp" (both) to "application or dApp" (either/or). Confirm this change is intentional, or revert to "application/DApp-operated accounts" if both were meant.


92-102: MetaMask duplication has been resolved.

The duplicate MetaMask section previously flagged has been removed, and a single complete section with the image reference remains. This change looks good.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants