Skip to content

Conversation

nvitorovic
Copy link
Contributor

Updating information on Tenderly platform

This PR adds clarifies or more info about using Tenderly in following areas:

  • Analytics (clarifications)
  • Block Explorers
  • RPC providers list
  • RPC gas estimation and setting gas parameters

No tested added, simple content update.

N/A

@nvitorovic nvitorovic requested review from 0xmariniere and a team as code owners February 13, 2025 11:23
Copy link

netlify bot commented Feb 13, 2025

Deploy Preview for docs-optimism ready!

Name Link
🔨 Latest commit f44eeb4
🔍 Latest deploy log https://app.netlify.com/sites/docs-optimism/deploys/67add616c28a550008af127b
😎 Deploy Preview https://deploy-preview-1363--docs-optimism.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@nvitorovic nvitorovic marked this pull request as draft February 13, 2025 11:23
Copy link
Contributor

coderabbitai bot commented Feb 13, 2025

📝 Walkthrough

Walkthrough

This pull request updates several documentation pages for OP Stack applications by adding and modifying content related to Tenderly. A new section titled "Testing and Staging with Tenderly" outlines the benefits of using Tenderly Virtual TestNets, including features such as Mainnet State Replication, unlimited test tokens, collaborative testing, CI/CD integration, and development tools for transaction analysis. Additionally, the changes update the descriptions and formatting across multiple files: the JSON structure of the console object is adjusted for clarity, the overview of Tenderly in analytics and block explorer guides is streamlined, and new entries for Tenderly-related faucets and RPC providers are introduced. The documentation now also mentions Tenderly methods (tenderly_estimateGas and tenderly_gasPrice) as alternatives for handling gas estimations and real-time gas predictions, further integrating Tenderly into the developer workflow.

Possibly related PRs

  • Adding thirdweb faucets #829: Enhances testnet documentation by adding new faucet entries, aligning with updates for testnet faucet information.

Suggested labels

documentation

Suggested reviewers

  • sbvegan
  • krofax

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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.

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.

Copy link
Contributor

@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

🧹 Nitpick comments (5)
pages/app-developers/tools/build/analytics-tools.mdx (1)

22-27: Improve clarity and readability of the Tenderly section.

The content structure is good, but there are opportunities to enhance readability:

  1. Add an introductory sentence before the bullet points to better set context.
  2. Consider grouping related features (monitoring, automation, simulation) together.
 [Tenderly](https://tenderly.co/?mtm_campaign=ext-docs&mtm_kwd=optimism) provides comprehensive monitoring and security solutions for OP-powered Chains, allowing you to stay informed and respond proactively to potential issues in real time.

+Tenderly offers the following key features:
+
 *   Configure [Tenderly Alerts](https://docs.tenderly.co/alerts/intro-to-alerts?mtm_campaign=ext-docs&mtm_kwd=optimism) for monitoring wallets and setting up real-time notifications on transactions and contract events. Notifications trigger external webhooks, PagerDuty, or chat apps like Telegram and Slack.
 *   Rely on [Developer Explorer](https://docs.tenderly.co/developer-explorer?mtm_campaign=ext-docs&mtm_kwd=optimism) to monitor and analyze transaction execution with high level of details.
 *   Use [Web3 Actions](https://docs.tenderly.co/web3-actions/intro-to-web3-actions?mtm_campaign=ext-docs&mtm_kwd=optimism) to automate predefined responses, improving security and user experience.
 *   Integrate [Simulation RPC](https://docs.tenderly.co/simulations/single-simulations#simulate-via-rpc?mtm_campaign=ext-docs&mtm_kwd=optimism) to predict transaction outcomes such as the expected asset changes, precise gas usage, and emitted events.
pages/app-developers/transactions/parameters.mdx (1)

63-66: Improve the introduction of the Tenderly gasPrice method.

The sentence contains redundant use of "alternatively." Consider restructuring for better flow.

-Alternatively, you can rely on Tenderly's [`tenderly_gasPrice`](https://docs.tenderly.co/node/rpc-reference/optimism-mainnet/tenderly_gasPrice?mtm_campaign=ext-docs&mtm_kwd=optimism) to get real-time gas predictions with 3 levels of likelihood for transaction inclusion.
+You can also use Tenderly's [`tenderly_gasPrice`](https://docs.tenderly.co/node/rpc-reference/optimism-mainnet/tenderly_gasPrice?mtm_campaign=ext-docs&mtm_kwd=optimism) to get real-time gas predictions with 3 levels of likelihood for transaction inclusion.
🧰 Tools
🪛 LanguageTool

[style] ~66-~66: This adverb was used twice in the sentence. Consider removing one of them or replacing them with a synonym.
Context: ...ternatively, you can rely on Tenderly's [tenderly_gasPrice](https://docs.tenderly.co/nod...

(ADVERB_REPETITION_PREMIUM)

pages/app-developers/testing-apps.mdx (1)

44-44: Fix compound adjective hyphenation.

The term "third party" should be hyphenated when used as a compound adjective before a noun.

-*   Create a Virtual TestNet to get access to third party contracts (e.g. Uniswap) and it's latest or historical state.
+*   Create a Virtual TestNet to get access to third-party contracts (e.g., Uniswap) and its latest or historical state.

Note: Also fixed "it's" to "its" and added a comma after "e.g."

🧰 Tools
🪛 LanguageTool

[uncategorized] ~44-~44: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...eate a Virtual TestNet to get access to third party contracts (e.g. Uniswap) and it's lates...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

pages/app-developers/transactions/estimates.mdx (1)

40-40: Improve sentence structure while maintaining valuable content.

The addition of Tenderly's gas estimation method is beneficial. However, let's improve readability by removing the redundant "alternatively".

-This means you can feed your transaction to the [`eth_estimateGas`](https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_estimategas) JSON-RPC method just like you would on Ethereum. Alternatively, use Tenderly's [`tenderly_estimateGas`](https://docs.tenderly.co/node/rpc-reference/optimism-mainnet/tenderly_estimateGas) for 100% accurate gas estimations.
+This means you can feed your transaction to the [`eth_estimateGas`](https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_estimategas) JSON-RPC method just like you would on Ethereum. You can also use Tenderly's [`tenderly_estimateGas`](https://docs.tenderly.co/node/rpc-reference/optimism-mainnet/tenderly_estimateGas) for 100% accurate gas estimations.
🧰 Tools
🪛 LanguageTool

[style] ~40-~40: This adverb was used twice in the sentence. Consider removing one of them or replacing them with a synonym.
Context: ...Ethereum. Alternatively, use Tenderly's [tenderly_estimateGas](https://docs.tenderly.co/...

(ADVERB_REPETITION_PREMIUM)

pages/app-developers/tools/connect/rpc-providers.mdx (1)

141-141: Enhance URL tracking parameters.

The content is well-structured and informative. Consider standardizing the URL tracking parameters to match other providers' format.

-[Tenderly](https://www.tenderly.co?mtm_campaign=ext-docs&mtm_kwd=optimism)
+[Tenderly](https://www.tenderly.co?utm_source=op-docs&utm_medium=partner-docs)
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d8f8060 and f44eeb4.

📒 Files selected for processing (8)
  • pages/app-developers/testing-apps.mdx (1 hunks)
  • pages/app-developers/tools/_meta.json (1 hunks)
  • pages/app-developers/tools/build/analytics-tools.mdx (1 hunks)
  • pages/app-developers/tools/build/block-explorers.mdx (3 hunks)
  • pages/app-developers/tools/build/faucets.mdx (1 hunks)
  • pages/app-developers/tools/connect/rpc-providers.mdx (1 hunks)
  • pages/app-developers/transactions/estimates.mdx (1 hunks)
  • pages/app-developers/transactions/parameters.mdx (2 hunks)
✅ Files skipped from review due to trivial changes (1)
  • pages/app-developers/tools/_meta.json
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.mdx`: "ALWAYS review Markdown content THOROUGHLY with ...

**/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

  • Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
  • Avoid gender-specific language and use the imperative form.
  • Monitor capitalization for emphasis. Avoid using all caps, italics, or bold for emphasis.
  • Ensure proper nouns are capitalized in sentences.
  • Apply the Oxford comma.
  • Use proper title case for buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
  • Use correct spelling and grammar at all times (IMPORTANT).
  • For H1, H2, and H3 headers:
    1. Use sentence case, capitalizing only the first word.
    2. Preserve the capitalization of proper nouns, technical terms, and acronyms as defined in the 'nouns.txt' file located in the root directory of the project.
    3. Do not automatically lowercase words that appear in the 'nouns.txt' file, regardless of their position in the header.
  • Flag any headers that seem to inconsistently apply these rules for manual review.
  • When reviewing capitalization, always refer to the 'nouns.txt' file for the correct capitalization of proper nouns and technical terms specific to the project.
    "
  • pages/app-developers/tools/build/block-explorers.mdx
  • pages/app-developers/tools/build/analytics-tools.mdx
  • pages/app-developers/testing-apps.mdx
  • pages/app-developers/tools/build/faucets.mdx
  • pages/app-developers/tools/connect/rpc-providers.mdx
  • pages/app-developers/transactions/estimates.mdx
  • pages/app-developers/transactions/parameters.mdx
🪛 LanguageTool
pages/app-developers/testing-apps.mdx

[formatting] ~39-~39: Insert a comma after ‘cases’: “In many cases,”?
Context: ...s. ## Integration with other products In many cases a decentralized application requires th...

(IN_MOST_CASES_COMMA)


[uncategorized] ~44-~44: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...eate a Virtual TestNet to get access to third party contracts (e.g. Uniswap) and it's lates...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

pages/app-developers/transactions/estimates.mdx

[style] ~40-~40: This adverb was used twice in the sentence. Consider removing one of them or replacing them with a synonym.
Context: ...Ethereum. Alternatively, use Tenderly's [tenderly_estimateGas](https://docs.tenderly.co/...

(ADVERB_REPETITION_PREMIUM)

pages/app-developers/transactions/parameters.mdx

[style] ~66-~66: This adverb was used twice in the sentence. Consider removing one of them or replacing them with a synonym.
Context: ...ternatively, you can rely on Tenderly's [tenderly_gasPrice](https://docs.tenderly.co/nod...

(ADVERB_REPETITION_PREMIUM)

🔇 Additional comments (2)
pages/app-developers/tools/build/faucets.mdx (1)

32-44: LGTM! Table formatting and content updates are well-structured.

The table formatting is consistent, and the new Tenderly faucet entry is properly documented with appropriate links and network information.

pages/app-developers/tools/build/block-explorers.mdx (1)

70-82: LGTM! The Tenderly section is well-organized and comprehensive.

The section provides a clear overview of Tenderly's Developer Explorer features with proper documentation links and tracking parameters.

@nvitorovic nvitorovic marked this pull request as ready for review February 13, 2025 11:25
@nvitorovic
Copy link
Contributor Author

@0xmariniere couldn't add a label post-PR creation, sorry about this
Would add rpc-provider & faucet out of existing ones

@krofax krofax merged commit b39895e into ethereum-optimism:main Feb 18, 2025
4 checks passed
This was referenced Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants