Adding L2 Faucet support for Devnet #1392
Conversation
Superchain Faucet now supports for Devnet
✅ Deploy Preview for docs-optimism ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
📝 WalkthroughWalkthroughThis pull request updates the Sequence Diagram(s)sequenceDiagram
participant User
participant Documentation
participant SuperchainFaucet
User->>Documentation: Access devnet instructions
Documentation->>User: Display steps for obtaining testnet ETH
User->>SuperchainFaucet: Follow instructions to request testnet ETH
SuperchainFaucet-->>User: Provide testnet ETH
Possibly related PRs
Suggested labels
Suggested reviewers
📜 Recent review detailsConfiguration used: .coderabbit.yaml 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (4)
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
Documentation and Community
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
pages/stack/interop/tools/devnet.mdx (1)
49-50: Improve Instruction Tone
Consider revising the phrasing "You can utilize" to a more direct, imperative tone (for example, "Use the [Superchain Faucet] to obtainETHoninterop-alpha-0andinterop-alpha-1."). This adjustment will enhance clarity and align with best practices for instructional content.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
pages/stack/interop/tools/devnet.mdx(1 hunks)
🧰 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:
- Use sentence case, capitalizing only the first word.
- 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.
- 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/stack/interop/tools/devnet.mdx
⏰ Context from checks skipped due to timeout of 90000ms (4)
- GitHub Check: Redirect rules - docs-optimism
- GitHub Check: Header rules - docs-optimism
- GitHub Check: Pages changed - docs-optimism
- GitHub Check: pr-workflow
🔇 Additional comments (2)
pages/stack/interop/tools/devnet.mdx (2)
44-44: Header Formatting and Clarity
The new header, "Getting testnet ETH on the interop devnet," clearly introduces the section on obtaining testnet ETH via the Superchain Faucet. It adheres to sentence case guidelines by capitalizing only the first word and preserving proper nouns and acronyms appropriately.
46-47: Effective Use of the Steps Component
The insertion of the<Steps>component along with the sub-header "### Get testnet ETH from the Superchain Faucet" is an excellent structural enhancement. It organizes the instructions clearly and is consistent with the expected MDX component usage.
|
Hello I’m currently testing a large-scale smart contract deployment on the Sepolia testnet and need a higher amount of Sepolia ETH than most faucets provide. My project involves deploying + smart contracts, each managing multiple wallets, so I’m looking for [X amount] of Sepolia ETH to continue testing. I’ve already used available faucets, but they have daily limits that slow down my progress. If anyone has extra Sepolia ETH or knows a source for larger distributions, I’d really appreciate the help. 1000 or 500 sepolia is all I need 0x96070538C13533Cb838B2fb1799A3e5f621155eD I’m happy to return any unused ETH after testing or contribute back to the community in other ways. Thanks in advance! Best wishes |
3 participants
Superchain Faucet now supports for Devnet