blog: add August 2025 developer update and assets; fix external link …#700
blog: add August 2025 developer update and assets; fix external link …#700Jordy-Baby merged 1 commit intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WalkthroughAdds a new blog post file documenting the August 2025 developer update, including v2.27.0 highlights (preload optimization, per-contract start blocks), community tools, events, and media links. No code or API changes; no exported/public entity alterations. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
Poem
Tip 🔌 Remote MCP (Model Context Protocol) integration is now available!Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats. ✨ Finishing Touches🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type 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: 7
🧹 Nitpick comments (3)
blog/2025-08-29-dev-update-august-2025.md (3)
7-7: Minor: add loading/decoding for hero image; ensure asset exists.-<img src="/blog-assets/dev-update-august-2025.png" alt="Cover Image Envio Developer Community Update August 2025" width="100%"/> +<img src="/blog-assets/dev-update-august-2025.png" alt="Envio Developer Community Update — August 2025" width="100%" loading="lazy" decoding="async"/>Also confirm the asset path
/blog-assets/dev-update-august-2025.pngexists in the PR.
110-112: Specify shell language for command fence (MD040).-``` -npx chainpulse -``` +```bash +npx chainpulse +```
136-137: Remove double space before link; minor copy polish.-We’ve joined the official list of [K8GB adopters](https://k8gb.io/ADOPTERS/). HyperSync is now served from multiple regions, giving builders faster and more reliable access wherever they are. +We’ve joined the official list of [K8GB adopters](https://k8gb.io/ADOPTERS/). HyperSync is now served from multiple regions, giving builders faster and more reliable access wherever they are.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (9)
static/blog-assets/aug-2025-DOTM.pngis excluded by!**/*.pngstatic/blog-assets/aug-playlist-2025.pngis excluded by!**/*.pngstatic/blog-assets/banned-list.pngis excluded by!**/*.pngstatic/blog-assets/chain-pulse.pngis excluded by!**/*.pngstatic/blog-assets/dev-update-august-2025.pngis excluded by!**/*.pngstatic/blog-assets/k8gb.pngis excluded by!**/*.pngstatic/blog-assets/liquidator.pngis excluded by!**/*.pngstatic/blog-assets/mobil3-hackathon.pngis excluded by!**/*.pngstatic/blog-assets/zup-integration.pngis excluded by!**/*.png
📒 Files selected for processing (1)
blog/2025-08-29-dev-update-august-2025.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
blog/2025-08-29-dev-update-august-2025.md
[grammar] ~65-~65: There might be a mistake here.
Context: ...## 👷♀️👷♂️ Contributing Improvements We’ve updated our **CONTRIBUTING.m...
(QB_NEW_EN)
[grammar] ~72-~72: There might be a mistake here.
Context: ... improve the experience for everyone. 😉 👉 See full [release notes](https://gith...
(QB_NEW_EN)
[grammar] ~74-~74: There might be a mistake here.
Context: ...everyone. 😉 👉 See full release notes 👉 Star us on [GitHub](https://github.co...
(QB_NEW_EN)
[grammar] ~76-~76: There might be a mistake here.
Context: ...ttps://github.com/enviodev/hyperindex) ⭐ ## Introducing Shipper Logs <iframe width=...
(QB_NEW_EN)
[grammar] ~100-~100: There might be a mistake here.
Context: ... you can instantly see: - 📊 Throughput - 🔄 Transaction activity - 👥 Address act...
(QB_NEW_EN)
[grammar] ~101-~101: There might be a mistake here.
Context: ... 📊 Throughput - 🔄 Transaction activity - 👥 Address activity - 📑 Logs & other ke...
(QB_NEW_EN)
[grammar] ~102-~102: There might be a mistake here.
Context: ...ansaction activity - 👥 Address activity - 📑 Logs & other key metrics Chains alre...
(QB_NEW_EN)
[grammar] ~103-~103: There might be a mistake here.
Context: ...s activity - 📑 Logs & other key metrics Chains already cooking include: BNB, Meg...
(QB_NEW_EN)
[grammar] ~115-~115: There might be a mistake here.
Context: ...jonjonclark/status/1958497121293787146). ## Envio Powers Zup Protocol <img src="/b...
(QB_NEW_EN)
[grammar] ~129-~129: There might be a mistake here.
Context: ...k out Zup Protocol: app.zupprotocol.xyz ## HyperSync is now Globally Distributed <...
(QB_NEW_EN)
[grammar] ~139-~139: There might be a mistake here.
Context: ... ## 🇲🇽 Mobil3 Hackathon - Mexico City 
We had a great time at the [Mobil3](http...
(QB_NEW_EN)
[grammar] ~153-~153: There might be a mistake here.
Context: ...n incredible event! ## 💸 $943M Frozen 
Say hello to the only list you don’t wan...
(QB_NEW_EN)
[style] ~159-~159: For conciseness, consider replacing this expression with an adverb.
Context: ...ross USDT and USDC on Ethereum mainnet. Right now, over $943M is locked in blacklisted wa...
(AT_THE_MOMENT)
[grammar] ~163-~163: There might be a mistake here.
Context: ...DenhamPreen/status/1956037853927846261). ## 💧 Introducing Liquidator <img src="/bl...
(QB_NEW_EN)
[grammar] ~166-~166: There might be a mistake here.
Context: ...846261). ## 💧 Introducing Liquidator 
Say hello to Liquidator, a new tool that...
(QB_NEW_EN)
[grammar] ~174-~174: There might be a mistake here.
Context: ...g soon. Which one should we add next? 👀 👉 See the original post on [X](https://...
(QB_NEW_EN)
[grammar] ~176-~176: There might be a mistake here.
Context: ...jonjonclark/status/1950609313719783846). ## 📦 Telegram to Notion Sync CRM Tool Man...
(QB_NEW_EN)
[grammar] ~179-~179: There might be a mistake here.
Context: ... ## 📦 Telegram to Notion Sync CRM Tool Managing endless Telegram groups is a ha...
(QB_NEW_EN)
[grammar] ~187-~187: There might be a mistake here.
Context: ...KenauVith32) 👉 Check it out on GitHub ## 🗓️ Upcoming Events * [Encode London](...
(QB_NEW_EN)
[grammar] ~190-~190: There might be a mistake here.
Context: ...am-to-notiondb) ## 🗓️ Upcoming Events * [Encode London](https://luma.com/Encode-L...
(QB_NEW_EN)
[grammar] ~192-~192: There might be a mistake here.
Context: ...ode-London-25): 24th → 26th October 2025 * [Devconnect Buenos Aires](https://devconn...
(QB_NEW_EN)
[grammar] ~196-~196: There might be a mistake here.
Context: ...ember 2025 ## 🧑💻 Featured Developer 
This month’s featured developer is Mikko...
(QB_NEW_EN)
[style] ~202-~202: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ...n-source communities. Thanks for being an awesome member of our community, Mikko! ...
(AWESOME)
[grammar] ~210-~210: There might be a mistake here.
Context: ...building. ## 🎧️ Playlist of the Month 
▶️ [Open Spotify](https://open.spotify.c...
(QB_NEW_EN)
[grammar] ~217-~217: There might be a mistake here.
Context: ...i=23e45edbfde34be1) ## 🚢 Ship With Us Envio is a multi-chain EVM blockchain in...
(QB_NEW_EN)
[grammar] ~224-~224: There might be a mistake here.
Context: ...ium=newsletter&utm_campaign=new-post) 💌 Website | [X](https...
(QB_NEW_EN)
🪛 markdownlint-cli2 (0.17.2)
blog/2025-08-29-dev-update-august-2025.md
19-19: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4
(MD001, heading-increment)
26-26: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
41-41: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
65-65: Multiple spaces after hash on atx style heading
(MD019, no-multiple-space-atx)
110-110: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
129-129: Spaces inside link text
(MD039, no-space-in-links)
192-192: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
193-193: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
205-205: Code block style
Expected: fenced; Actual: indented
(MD046, code-block-style)
🔇 Additional comments (2)
blog/2025-08-29-dev-update-august-2025.md (2)
159-161: Add timestamp context for volatile figures
Prefix the statistics with “As of August 29, 2025” to clarify when these values were accurate. Confirm that the totals—$943 M overall, $833.78 M in USDT, and $109.73 M in USDC—are correct as of that date.
-This dashboard tracks funds frozen across USDT and USDC on Ethereum mainnet. Right now, over $943M is locked in blacklisted wallets. USDT accounts for $833.78M and USDC makes up $109.73M.
+This dashboard tracks funds frozen across USDT and USDC on Ethereum mainnet. As of August 29, 2025, over $943M is locked in blacklisted wallets. USDT accounts for $833.78M and USDC makes up $109.73M.
1-5: Update front matter for this blog post
Remove sidebar_label, make slug relative, add description and tags:
---
title: Envio Developer Update August 2025
-sidebar_label: Envio Developer Update August 2025
-slug: /envio-developer-update-august-2025
+slug: envio-developer-update-august-2025
+description: August 2025 update: HyperIndex preload optimization, per-contract start blocks, HyperSync global distribution, community tools, events, and more.
+tags:
+ - releases
+ - hyperindex
+ - hypersync
+ - community
---
Verify in this file only (fix any leading / and http:// links):
rg -nP '^slug:\s*/' blog/2025-08-29-dev-update-august-2025.md
rg -n 'http://' blog/2025-08-29-dev-update-august-2025.md
| ## ⚡ BIG Releases: v2.27.0 | ||
|
|
||
|
|
||
| #### Preload Optimization | ||
|
|
||
| HyperIndex now preloads entities used by handlers via batched database queries, maintaining the original order of event processing. Paired with the Effect API for external calls, this gives big performance gains over other indexing solutions. | ||
|
|
||
| Set a single line in your config and make your handlers run multiple times faster without changing a single line of code: | ||
|
|
||
|
|
||
| ``` | ||
| preload_handlers: true | ||
| ``` | ||
|
|
||
|
|
||
| *⚠️ Note: Preload optimization runs your handlers twice. From **<code>envio@2.27</code>**, all new indexers include it by default.* |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Fix heading level and add fenced code language (MD001, MD040).
-## ⚡ BIG Releases: v2.27.0
+## ⚡ BIG Releases: v2.27.0
@@
-#### Preload Optimization
+### Preload Optimization
@@
-```
+```yaml
preload_handlers: true@@
-envio@2.27, all new indexers include it by default.
+envio@2.27, all new indexers include it by default.
If the version should be 2.27.0 in text, adjust accordingly.
<details>
<summary>🧰 Tools</summary>
<details>
<summary>🪛 markdownlint-cli2 (0.17.2)</summary>
19-19: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4
(MD001, heading-increment)
---
26-26: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
</details>
</details>
<!-- fingerprinting:phantom:triton:chinchilla -->
<!-- This is an auto-generated comment by CodeRabbit -->
| #### Contract-specific start block | ||
|
|
||
| HyperIndex now supports indexing with start blocks on a per-contract basis (previously, start blocks were only per-network), a highly requested feature contributed by one of our community members, [Rangel Stoilov](https://github.com/rori4). | ||
|
|
||
| **Example**: register NFT contracts from a factory but start processing Transfers only from block 30,000,000: | ||
|
|
||
|
|
||
| ``` | ||
| name: nft-indexer | ||
| description: NFT Factory | ||
| networks: | ||
| - id: 1337 | ||
| start_block: 0 | ||
| contracts: | ||
| - name: NftFactory | ||
| address: 0x4675a6B115329294e0518A2B7cC12B70987895C4 | ||
| handler: src/EventHandlers.ts | ||
| events: | ||
| - event: SimpleNftCreated(string name, string symbol, uint256 maxSupply, address contractAddress) | ||
|
|
||
| - name: Nft | ||
| # No address field - we'll discover these addresses from SimpleNftCreated events | ||
| start_block: | ||
| handler: src/EventHandlers.ts | ||
| start_block: 30000000 # Overwrite the network start block | ||
| events: | ||
| - event: Transfer(address from, address to, uint256 tokenId) | ||
| ``` |
There was a problem hiding this comment.
YAML example has a duplicate/empty start_block; add language to fence and correct structure.
-#### Contract-specific start block
+### Contract-specific start block
@@
-```
+```yaml
name: nft-indexer
description: NFT Factory
networks:
- id: 1337
start_block: 0
contracts:
- name: NftFactory
address: 0x4675a6B115329294e0518A2B7cC12B70987895C4
handler: src/EventHandlers.ts
events:
- event: SimpleNftCreated(string name, string symbol, uint256 maxSupply, address contractAddress)
- name: Nft
- # No address field - we'll discover these addresses from SimpleNftCreated events
- start_block:
+ # No address field - discovered from SimpleNftCreated events
handler: src/EventHandlers.ts
start_block: 30000000 # Overwrite the network start block
events:
- event: Transfer(address from, address to, uint256 tokenId)
<details>
<summary>🧰 Tools</summary>
<details>
<summary>🪛 markdownlint-cli2 (0.17.2)</summary>
41-41: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
</details>
</details>
<details>
<summary>🤖 Prompt for AI Agents</summary>
In blog/2025-08-29-dev-update-august-2025.md around lines 34-61 the YAML example
contains a duplicate empty "start_block" entry and an unclear comment; replace
the snippet with a properly fenced YAML block (```yaml) that removes the empty
start_block under the "Nft" contract, move/keep only the explicit start_block:
30000000 line, and update the comment to "No address field - discovered from
SimpleNftCreated events" so the example is structurally correct and clearly
documented.
</details>
<!-- fingerprinting:phantom:triton:chinchilla -->
<!-- This is an auto-generated comment by CodeRabbit -->
| #### 👷♀️👷♂️ Contributing Improvements | ||
|
|
||
| We’ve updated our **<code>CONTRIBUTING.md</code>** with a detailed guide to navigating the HyperIndex codebase and examples of changes in action. We’ve also added `.cursor` rules to make developing new HyperIndex features easier. | ||
|
|
||
|
|
||
| #### Embrace Vibe-Coding | ||
|
|
||
| All new projects now include initial `.cursor` rules to help you build indexers with agent support. Got ideas? Send a PR with rule suggestions to improve the experience for everyone. 😉 | ||
|
|
||
| 👉 See full [release notes](https://github.com/enviodev/hyperindex/releases) | ||
|
|
||
| 👉 Star us on [GitHub](https://github.com/enviodev/hyperindex) ⭐ |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Normalize heading spacing/level (MD019, MD001).
-#### 👷♀️👷♂️ Contributing Improvements
+### 👷♀️👷♂️ Contributing Improvements
@@
-👉 See full [release notes](https://github.com/enviodev/hyperindex/releases)
-👉 Star us on [GitHub](https://github.com/enviodev/hyperindex) ⭐
+👉 See full [release notes](https://github.com/enviodev/hyperindex/releases)
+👉 Star us on [GitHub](https://github.com/enviodev/hyperindex) ⭐📝 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.
| #### 👷♀️👷♂️ Contributing Improvements | |
| We’ve updated our **<code>CONTRIBUTING.md</code>** with a detailed guide to navigating the HyperIndex codebase and examples of changes in action. We’ve also added `.cursor` rules to make developing new HyperIndex features easier. | |
| #### Embrace Vibe-Coding | |
| All new projects now include initial `.cursor` rules to help you build indexers with agent support. Got ideas? Send a PR with rule suggestions to improve the experience for everyone. 😉 | |
| 👉 See full [release notes](https://github.com/enviodev/hyperindex/releases) | |
| 👉 Star us on [GitHub](https://github.com/enviodev/hyperindex) ⭐ | |
| ### 👷♀️👷♂️ Contributing Improvements | |
| We’ve updated our **<code>CONTRIBUTING.md</code>** with a detailed guide to navigating the HyperIndex codebase and examples of changes in action. We’ve also added `.cursor` rules to make developing new HyperIndex features easier. | |
| #### Embrace Vibe-Coding | |
| All new projects now include initial `.cursor` rules to help you build indexers with agent support. Got ideas? Send a PR with rule suggestions to improve the experience for everyone. 😉 | |
| 👉 See full [release notes](https://github.com/enviodev/hyperindex/releases) | |
| 👉 Star us on [GitHub](https://github.com/enviodev/hyperindex) ⭐ |
🧰 Tools
🪛 LanguageTool
[grammar] ~65-~65: There might be a mistake here.
Context: ...## 👷♀️👷♂️ Contributing Improvements We’ve updated our **CONTRIBUTING.m...
(QB_NEW_EN)
[grammar] ~72-~72: There might be a mistake here.
Context: ... improve the experience for everyone. 😉 👉 See full [release notes](https://gith...
(QB_NEW_EN)
[grammar] ~74-~74: There might be a mistake here.
Context: ...everyone. 😉 👉 See full release notes 👉 Star us on [GitHub](https://github.co...
(QB_NEW_EN)
[grammar] ~76-~76: There might be a mistake here.
Context: ...ttps://github.com/enviodev/hyperindex) ⭐ ## Introducing Shipper Logs <iframe width=...
(QB_NEW_EN)
🪛 markdownlint-cli2 (0.17.2)
65-65: Multiple spaces after hash on atx style heading
(MD019, no-multiple-space-atx)
🤖 Prompt for AI Agents
In blog/2025-08-29-dev-update-august-2025.md around lines 65 to 76, the headings
violate MD019/MD001 by inconsistent heading levels and missing blank lines; fix
by ensuring there is exactly one blank line before each heading and that heading
levels are semantically consistent (e.g., use "###" for subheadings under a
single top-level H1), adjust "Contributing Improvements" and "Embrace
Vibe-Coding" to the same appropriate level, and remove or add blank lines as
needed so each heading is preceded and followed by a blank line where required.
| <iframe width="560" height="315" | ||
| src="https://www.youtube.com/embed/QqbH78CEid8" | ||
| frameborder="0" | ||
| allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" | ||
| allowfullscreen> | ||
| </iframe> | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Add a title to iframe for accessibility; consider MDX attribute casing.
-<iframe width="560" height="315"
- src="https://www.youtube.com/embed/QqbH78CEid8"
- frameborder="0"
- allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture"
- allowfullscreen>
+<iframe width="560" height="315"
+ src="https://www.youtube.com/embed/QqbH78CEid8"
+ title="Shipper Logs — Episode 1: Preload Optimization"
+ frameBorder="0"
+ allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture; clipboard-write; web-share"
+ referrerpolicy="strict-origin-when-cross-origin"
+ allowFullScreen>
</iframe>📝 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.
| <iframe width="560" height="315" | |
| src="https://www.youtube.com/embed/QqbH78CEid8" | |
| frameborder="0" | |
| allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" | |
| allowfullscreen> | |
| </iframe> | |
| <iframe width="560" height="315" | |
| src="https://www.youtube.com/embed/QqbH78CEid8" | |
| title="Shipper Logs — Episode 1: Preload Optimization" | |
| frameBorder="0" | |
| allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture; clipboard-write; web-share" | |
| referrerpolicy="strict-origin-when-cross-origin" | |
| allowFullScreen> | |
| </iframe> |
🤖 Prompt for AI Agents
In blog/2025-08-29-dev-update-august-2025.md around lines 81 to 87, the iframe
lacks a title for accessibility and uses HTML attribute casing that may not work
in MDX; add a descriptive title attribute (e.g. title="YouTube — Dev Update
August 2025") and convert HTML-only attributes to MDX/JSX casing where needed
(use allowFullScreen instead of allowfullscreen, keep frameBorder as-is or use
camelCase if required by your MDX config), ensuring the iframe remains
accessible and valid in MDX.
|
|
||
| Powered by Envio, you can compare 1,000+ combos in just 10 seconds. | ||
|
|
||
| 👉 Check out Zup Protocol:[ app.zupprotocol.xyz](https://app.zupprotocol.xyz) |
There was a problem hiding this comment.
Fix spacing inside link text (MD039).
-👉 Check out Zup Protocol:[ app.zupprotocol.xyz](https://app.zupprotocol.xyz)
+👉 Check out Zup Protocol: [app.zupprotocol.xyz](https://app.zupprotocol.xyz)📝 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.
| 👉 Check out Zup Protocol:[ app.zupprotocol.xyz](https://app.zupprotocol.xyz) | |
| 👉 Check out Zup Protocol: [app.zupprotocol.xyz](https://app.zupprotocol.xyz) |
🧰 Tools
🪛 LanguageTool
[grammar] ~129-~129: There might be a mistake here.
Context: ...k out Zup Protocol: app.zupprotocol.xyz ## HyperSync is now Globally Distributed <...
(QB_NEW_EN)
🪛 markdownlint-cli2 (0.17.2)
129-129: Spaces inside link text
(MD039, no-space-in-links)
🤖 Prompt for AI Agents
In blog/2025-08-29-dev-update-august-2025.md around line 129, the link text
contains an extra leading space inside the square brackets ("[
app.zupprotocol.xyz](https://app.zupprotocol.xyz)"); remove the internal spacing
so the link text is "[app.zupprotocol.xyz](https://app.zupprotocol.xyz)" to
satisfy MD039 (no spaces inside link text).
| ## 🗓️ Upcoming Events | ||
|
|
||
| * [Encode London](https://luma.com/Encode-London-25): 24th → 26th October 2025 | ||
| * [Devconnect Buenos Aires](https://devconnect.org/): 17th → 22nd November 2025 | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Unify list style and improve date formatting (MD004).
-* [Encode London](https://luma.com/Encode-London-25): 24th → 26th October 2025
-* [Devconnect Buenos Aires](https://devconnect.org/): 17th → 22nd November 2025
+- [Encode London](https://luma.com/Encode-London-25): October 24–26, 2025
+- [Devconnect Buenos Aires](https://devconnect.org/): November 17–22, 2025📝 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.
| ## 🗓️ Upcoming Events | |
| * [Encode London](https://luma.com/Encode-London-25): 24th → 26th October 2025 | |
| * [Devconnect Buenos Aires](https://devconnect.org/): 17th → 22nd November 2025 | |
| ## 🗓️ Upcoming Events | |
| - [Encode London](https://luma.com/Encode-London-25): October 24–26, 2025 | |
| - [Devconnect Buenos Aires](https://devconnect.org/): November 17–22, 2025 |
🧰 Tools
🪛 LanguageTool
[grammar] ~190-~190: There might be a mistake here.
Context: ...am-to-notiondb) ## 🗓️ Upcoming Events * [Encode London](https://luma.com/Encode-L...
(QB_NEW_EN)
[grammar] ~192-~192: There might be a mistake here.
Context: ...ode-London-25): 24th → 26th October 2025 * [Devconnect Buenos Aires](https://devconn...
(QB_NEW_EN)
🪛 markdownlint-cli2 (0.17.2)
192-192: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
193-193: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
🤖 Prompt for AI Agents
In blog/2025-08-29-dev-update-august-2025.md around lines 190 to 194, the
unordered list uses inconsistent style and the date ranges use a right-arrow
character; update the list to a single marker style (e.g., use hyphens "-" for
every item) and normalize date ranges to use an en dash with consistent month
formatting (e.g., "24–26 October 2025" and "17–22 November 2025") so the
markdown follows MD004 and has consistent, readable dates.
| ***“We use Envio because it's the first indexer that works. Envio is easy to integrate with modern data research and trading pipelines based in Python. This allows us to integrate more chains, faster, go deeper in data, and finally have a developer experience blockchain programmers have craved for.”*** - *Mikko Ohtamaa, CEO & Co-Founder at Trading Strategy* | ||
|
|
||
| Be sure to follow them on [X](https://x.com/moo9000) and check out their work on [GitHub](https://github.com/miohtama/) to stay up to date with what they are building. |
There was a problem hiding this comment.
Quote is rendered as a code block; convert to blockquote (MD046).
- ***“We use Envio because it's the first indexer that works. Envio is easy to integrate with modern data research and trading pipelines based in Python. This allows us to integrate more chains, faster, go deeper in data, and finally have a developer experience blockchain programmers have craved for.”*** - *Mikko Ohtamaa, CEO & Co-Founder at Trading Strategy*
+> “We use Envio because it's the first indexer that works. Envio is easy to integrate with modern data research and trading pipelines based in Python. This allows us to integrate more chains, faster, go deeper in data, and finally have a developer experience blockchain programmers have craved for.”
+>
+> — <em>Mikko Ohtamaa, CEO & Co‑Founder at Trading Strategy</em>📝 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 use Envio because it's the first indexer that works. Envio is easy to integrate with modern data research and trading pipelines based in Python. This allows us to integrate more chains, faster, go deeper in data, and finally have a developer experience blockchain programmers have craved for.”*** - *Mikko Ohtamaa, CEO & Co-Founder at Trading Strategy* | |
| Be sure to follow them on [X](https://x.com/moo9000) and check out their work on [GitHub](https://github.com/miohtama/) to stay up to date with what they are building. | |
| > “We use Envio because it's the first indexer that works. Envio is easy to integrate with modern data research and trading pipelines based in Python. This allows us to integrate more chains, faster, go deeper in data, and finally have a developer experience blockchain programmers have craved for.” | |
| > | |
| > — <em>Mikko Ohtamaa, CEO & Co-Founder at Trading Strategy</em> | |
| Be sure to follow them on [X](https://x.com/moo9000) and check out their work on [GitHub](https://github.com/miohtama/) to stay up to date with what they are building. |
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
205-205: Code block style
Expected: fenced; Actual: indented
(MD046, code-block-style)
🤖 Prompt for AI Agents
In blog/2025-08-29-dev-update-august-2025.md around lines 205 to 207 the quote
is currently formatted as a code block; replace the code-fence block with a
Markdown blockquote: prefix each quote line with "> " and keep the attribution
italicized on its own line (e.g., "> — *Name, Title*") so the text is rendered
as a proper blockquote and satisfies MD046.
2 participants
…protocol
Summary by CodeRabbit