Conversation
|
Caution Review failedThe pull request is closed. WalkthroughThis update revises documentation and configuration files to reflect changes in supported blockchain networks. It adds documentation for the Swell network, updates network lists in markdown and JSON files, and performs minor markdown formatting and whitespace cleanups. No application logic or public entity declarations are affected. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Docs
participant Config
User->>Docs: Reads about supported networks (including Swell)
User->>Config: References supported-networks.json for available networks
Docs-->>User: Provides configuration and endpoint info for Swell
Config-->>User: Lists updated supported networks
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI ⛔ Files ignored due to path filters (9)
📒 Files selected for processing (5)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
🧹 Nitpick comments (5)
blog/2025-04-25-developer-update-april-2025.md (1)
147-147: Refine “Feel free to check out the original background [post]”
Consider a more formal phrasing to suit a developer update—e.g., “For additional context, view the original background [post] on X.”blog/2025-05-28-developer-update-may-2025.md (4)
112-112: Refine the adjective for a professional tone.
Instead of “awesome graphs,” consider alternatives like “insightful graphs” or “detailed visualizations.”🧰 Tools
🪛 LanguageTool
[style] ~112-~112: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ...ts from multiple regions. Check out the awesome graphs showcasing where traffic is comi...(AWESOME)
143-143: Add missing comma in compound sentence.
Change “open-sourcing their version soon so others can build on it too” to “open-sourcing their version soon, so others can build on it too.”🧰 Tools
🪛 LanguageTool
[uncategorized] ~143-~143: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...y’ll be open-sourcing their version soon so others can build on it too. Shout out ...(COMMA_COMPOUND_SENTENCE_2)
150-150: Consistent casing for “EVM.”
Please capitalize EVM in the heading to match usage elsewhere.- ## Monad Evm/Accathon Winners + ## Monad EVM/Accathon Winners
187-187: Unify “Ship with us” heading style.
This heading (“Ship With Us 🚢”) differs in capitalization and punctuation from previous updates (“Ship with us. 🚢”). Consider standardizing across posts.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (12)
static/blog-assets/dev-update-april-2025-1.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025-2.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025-3.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025-4.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025-5.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025-6.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025-7.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025-8.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025-9.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-april-2025.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-may-2025.pngis excluded by!**/*.pngstatic/blog-assets/monad-hackathon-winners-2025.pngis excluded by!**/*.png
📒 Files selected for processing (3)
blog/2025-04-25-developer-update-april-2025.md(1 hunks)blog/2025-05-16-monad-hackathon-winners-2025.md(1 hunks)blog/2025-05-28-developer-update-may-2025.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
blog/2025-04-25-developer-update-april-2025.md
[style] ~145-~145: Consider using a less common alternative to make your writing sound more unique and professional.
Context: ...://github.com/denhampreen/loggregate). Feel free to check out the original background [post...
(FEEL_FREE_TO_STYLE_ME)
[misspelling] ~199-~199: This word is normally spelled as one.
Context: ...oming soon) using Envio, a custom-built multi-chain indexer for Uniswap V3 powered by Hyper...
(EN_COMPOUNDS_MULTI_CHAIN)
[misspelling] ~219-~219: This word is normally spelled as one.
Context: ...# Ship with us. 🚢 Envio is a modern, multi-chain EVM blockchain indexer for querying rea...
(EN_COMPOUNDS_MULTI_CHAIN)
blog/2025-05-28-developer-update-may-2025.md
[style] ~112-~112: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ...ts from multiple regions. Check out the awesome graphs showcasing where traffic is comi...
(AWESOME)
[uncategorized] ~143-~143: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...y’ll be open-sourcing their version soon so others can build on it too. Shout out ...
(COMMA_COMPOUND_SENTENCE_2)
[misspelling] ~173-~173: This word is normally spelled as one.
Context: ...hains. Blazing fast indexing and native multi-chain support make it a game-changer.” - Paul...
(EN_COMPOUNDS_MULTI_CHAIN)
[misspelling] ~189-~189: This word is normally spelled as one.
Context: ...## Ship With Us 🚢 Envio is a modern, multi-chain EVM blockchain indexer for querying rea...
(EN_COMPOUNDS_MULTI_CHAIN)
🔇 Additional comments (4)
blog/2025-04-25-developer-update-april-2025.md (1)
1-5: Frontmatter looks good.
The YAML metadata (title, sidebar_label, slug) is consistent with existing posts and follows naming conventions.blog/2025-05-16-monad-hackathon-winners-2025.md (2)
1-5: Frontmatter is properly defined.
The metadata fields (title, sidebar_label, slug) align with conventions and other posts.
7-74: Content is clear and well-structured.
Headings, links, and descriptions are concise and error-free. The narrative flows logically through the hackathon winners, calls to action, and community links.blog/2025-05-28-developer-update-may-2025.md (1)
1-5: Frontmatter is correct.
YAML metadata matches the format used in other monthly updates.
|
|
||
| ``` | ||
| context.log.info("Sucessfully handled Transfer()", { from: event.params.from, to: event.params.to }) | ||
|
|
||
| These params will be displayed in the logs in your terminal as well as in Hosted Service. | ||
|
|
||
| You can also pass an error: | ||
| } catch (error) { | ||
| context.log.error("Failed ipfs call", error) | ||
| } | ||
| ``` |
There was a problem hiding this comment.
Complete the logger snippet with a try block.
The code shows a } catch (error) without a matching try { ... }. Consider wrapping the IPFS call in try/catch to make this snippet valid.
- } catch (error) {
- context.log.error("Failed ipfs call", error)
- }
+ try {
+ // your IPFS call here
+ } catch (error) {
+ context.log.error("Failed ipfs call", error)
+ }📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ``` | |
| context.log.info("Sucessfully handled Transfer()", { from: event.params.from, to: event.params.to }) | |
| These params will be displayed in the logs in your terminal as well as in Hosted Service. | |
| You can also pass an error: | |
| } catch (error) { | |
| context.log.error("Failed ipfs call", error) | |
| } | |
| ``` | |
| context.log.info("Sucessfully handled Transfer()", { from: event.params.from, to: event.params.to }) | |
| These params will be displayed in the logs in your terminal as well as in Hosted Service. | |
| You can also pass an error: | |
| try { | |
| // your IPFS call here | |
| } catch (error) { | |
| context.log.error("Failed ipfs call", error) | |
| } |
🤖 Prompt for AI Agents
In blog/2025-04-25-developer-update-april-2025.md around lines 69 to 79, the
logging snippet includes a catch block without a corresponding try block, making
the code invalid. Wrap the IPFS call and the success log statement inside a try
block, then keep the existing catch block to handle errors properly. This will
complete the try/catch structure and ensure the snippet is syntactically
correct.
| ``` | ||
| import { FactoryContract, UserContract } from "generated"; | ||
|
|
||
| const USDC_ADDRESS = { | ||
| 84532: "0x036CbD53842c5426634e7929541eC2318f3dCF7e", | ||
| 11155111: "0x1c7D4B196Cb0C7B01d743Fbc6116a902379C7238", | ||
| }; | ||
|
|
||
| FactoryContract.UserCreted.contractRegister(async ({ event, context }) => { | ||
| context.addUserContract(event.params.userContractAddress); | ||
| }); | ||
|
|
||
| UserContract.Transfer.handler(async ({ event, context }) => { | ||
| // Filter and store only the USDC transfers that involve a Safe address | ||
| if (event.srcAddress === USDC_ADDRESS[event.chainId]) { | ||
| context.Transfer.set({ | ||
| id: `${event.chainId}_${event.block.number}_${event.logIndex}`, | ||
| from: event.params.from, | ||
| to: event.params.to, | ||
| }); | ||
| } | ||
| }, { | ||
| wildcard: true, | ||
| eventFilters: ({ addresses }) => [{ from: addresses }, { to: addresses }], | ||
| }); | ||
| ``` |
There was a problem hiding this comment.
Typo in event handler name will break the example.
The snippet references FactoryContract.UserCreted.contractRegister, but the correct event is likely UserCreated.
- FactoryContract.UserCreted.contractRegister(async ({ event, context }) => {
+ FactoryContract.UserCreated.contractRegister(async ({ event, context }) => {📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ``` | |
| import { FactoryContract, UserContract } from "generated"; | |
| const USDC_ADDRESS = { | |
| 84532: "0x036CbD53842c5426634e7929541eC2318f3dCF7e", | |
| 11155111: "0x1c7D4B196Cb0C7B01d743Fbc6116a902379C7238", | |
| }; | |
| FactoryContract.UserCreted.contractRegister(async ({ event, context }) => { | |
| context.addUserContract(event.params.userContractAddress); | |
| }); | |
| UserContract.Transfer.handler(async ({ event, context }) => { | |
| // Filter and store only the USDC transfers that involve a Safe address | |
| if (event.srcAddress === USDC_ADDRESS[event.chainId]) { | |
| context.Transfer.set({ | |
| id: `${event.chainId}_${event.block.number}_${event.logIndex}`, | |
| from: event.params.from, | |
| to: event.params.to, | |
| }); | |
| } | |
| }, { | |
| wildcard: true, | |
| eventFilters: ({ addresses }) => [{ from: addresses }, { to: addresses }], | |
| }); | |
| ``` | |
| import { FactoryContract, UserContract } from "generated"; | |
| const USDC_ADDRESS = { | |
| 84532: "0x036CbD53842c5426634e7929541eC2318f3dCF7e", | |
| 11155111: "0x1c7D4B196Cb0C7B01d743Fbc6116a902379C7238", | |
| }; | |
| FactoryContract.UserCreated.contractRegister(async ({ event, context }) => { | |
| context.addUserContract(event.params.userContractAddress); | |
| }); | |
| UserContract.Transfer.handler(async ({ event, context }) => { | |
| // Filter and store only the USDC transfers that involve a Safe address | |
| if (event.srcAddress === USDC_ADDRESS[event.chainId]) { | |
| context.Transfer.set({ | |
| id: `${event.chainId}_${event.block.number}_${event.logIndex}`, | |
| from: event.params.from, | |
| to: event.params.to, | |
| }); | |
| } | |
| }, { | |
| wildcard: true, | |
| eventFilters: ({ addresses }) => [{ from: addresses }, { to: addresses }], | |
| }); |
🤖 Prompt for AI Agents
In blog/2025-04-25-developer-update-april-2025.md between lines 28 and 53, there
is a typo in the event handler name: "UserCreted" should be corrected to
"UserCreated" in the FactoryContract event registration. Fix this by renaming
"UserCreted" to "UserCreated" to ensure the event handler is properly registered
and functional.
| #### **Effect API for Effcient External Calls** | ||
|
|
||
| The new Effect API lets you batch, memoize, and deduplicate external calls directly from your handlers. | ||
|
|
||
| Paired with loaders, it prevents overfetching and speeds up processing across large batches. | ||
|
|
||
| Check out the [walkthrough](walkthrough) on Loom or dive into our [Loaders](Loaders) guide to learn more. |
There was a problem hiding this comment.
Fix typo in heading.
The word “Effcient” is misspelled. Correct to “Efficient” to maintain professionalism.
- #### **Effect API for Effcient External Calls**
+ #### **Effect API for Efficient External Calls**📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| #### **Effect API for Effcient External Calls** | |
| The new Effect API lets you batch, memoize, and deduplicate external calls directly from your handlers. | |
| Paired with loaders, it prevents overfetching and speeds up processing across large batches. | |
| Check out the [walkthrough](walkthrough) on Loom or dive into our [Loaders](Loaders) guide to learn more. | |
| #### **Effect API for Efficient External Calls** | |
| The new Effect API lets you batch, memoize, and deduplicate external calls directly from your handlers. | |
| Paired with loaders, it prevents overfetching and speeds up processing across large batches. | |
| Check out the [walkthrough](walkthrough) on Loom or dive into our [Loaders](Loaders) guide to learn more. |
🤖 Prompt for AI Agents
In blog/2025-05-28-developer-update-may-2025.md around lines 54 to 60, correct
the typo in the heading by changing "Effcient" to "Efficient" to ensure proper
spelling and professionalism.
|
|
||
| Added **<code>accessList</code>** and **<code>authorizationList</code>** (EIP-7702) to transactions for expanded chain compatibility.** | ||
| ** | ||
|
|
There was a problem hiding this comment.
Remove stray markdown tokens.
There’s an extra closing ** at the end of the sentence and a standalone ** on the next line, which breaks formatting.
- Added **<code>accessList</code>** and **<code>authorizationList</code>** (EIP-7702) to transactions for expanded chain compatibility.**
- **
+ Added **<code>accessList</code>** and **<code>authorizationList</code>** (EIP-7702) to transactions for expanded chain compatibility.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Added **<code>accessList</code>** and **<code>authorizationList</code>** (EIP-7702) to transactions for expanded chain compatibility.** | |
| ** | |
| Added **<code>accessList</code>** and **<code>authorizationList</code>** (EIP-7702) to transactions for expanded chain compatibility. |
🤖 Prompt for AI Agents
In blog/2025-05-28-developer-update-may-2025.md around lines 39 to 42, remove
the extra closing double asterisks (**) at the end of the sentence and the
standalone double asterisks on the next line to fix the stray markdown tokens
and correct the formatting.
| We highly recommend exploring Paul’s contributions and projects in the space. He’s also an active voice on [X](https://x.com/PaulRBerg) and [Farcaster](https://farcaster.xyz/prberg), where he shares insights that go beyond crypto, diving into topics like longevity, epistemology, and physics. Give him a follow and check out his [GitHub](https://github.com/PaulRBerg | ||
| ) to stay in the loop! |
There was a problem hiding this comment.
Fix broken GitHub link syntax.
The link for Paul’s GitHub profile is split across lines and missing its closing parenthesis. Combine into one line for valid Markdown.
- Give him a follow and check out his [GitHub](https://github.com/PaulRBerg
- ) to stay in the loop!
+ Give him a follow and check out his [GitHub](https://github.com/PaulRBerg) to stay in the loop!📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| We highly recommend exploring Paul’s contributions and projects in the space. He’s also an active voice on [X](https://x.com/PaulRBerg) and [Farcaster](https://farcaster.xyz/prberg), where he shares insights that go beyond crypto, diving into topics like longevity, epistemology, and physics. Give him a follow and check out his [GitHub](https://github.com/PaulRBerg | |
| ) to stay in the loop! | |
| Give him a follow and check out his [GitHub](https://github.com/PaulRBerg) to stay in the loop! |
🤖 Prompt for AI Agents
In blog/2025-05-28-developer-update-may-2025.md around lines 177 to 178, the
GitHub link for Paul’s profile is broken because it is split across lines and
missing the closing parenthesis. Fix this by combining the entire GitHub URL and
its Markdown syntax into a single line, ensuring the link is properly enclosed
with parentheses.
|
@MJYoung114 I've already agreed to the rabbit stuff mentioned above in the version we just merged - I just want to add the missing assets. not sure what I did wrong here 🤔 |
Jordy-Baby
force-pushed
the
developer-update-may-2025-blog
branch
from
77836cb to
b5ab12c
Compare
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
2 participants
Summary by CodeRabbit
New Features
Documentation
Chores