Skip to content

Update 2026-02-25-dev-update-february-2026.md #804

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Jordy-Baby merged 1 commit into from
Feb 18, 2026
Merged

Update 2026-02-25-dev-update-february-2026.md #804

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
50 changes: 46 additions & 4 deletions blog/2026-02-25-dev-update-february-2026.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,12 +9,54 @@ description: "Envio Developer Update February 2026: HyperIndex v3 alpha.13 with

<!--truncate-->

February brings a new HyperIndex V3 alpha release along with expanded network support and feature updates. We shipped HyperIndex v3.0.0 alpha.13 with 3x faster historical backfills, support for DESC indices, improved RPC source support, experimental WebSocket support, and a breaking configuration change with `rpc_config` removed in favour of `rpc`.
February brings a couple new HyperIndex V3 alpha release along with expanded network support and feature updates. We shipped HyperIndex v3.0.0 alpha.13 & alpha.14 with 3x faster historical backfills, support for DESC indices, improved RPC source support, experimental WebSocket support, and a breaking configuration change with `rpc_config` removed in favour of `rpc`, new getWhere API, removed ordered multichain mode support, big Cursor/Claude update and much more!
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 18, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Grammar: "a couple new … release" → "a couple of new … releases"

"A couple new" is missing the preposition "of", and "release" should be plural to agree with "alpha.13 & alpha.14".

✏️ Suggested fix 
-February brings a couple new HyperIndex V3 alpha release along with expanded network support and feature updates.
+February brings a couple of new HyperIndex V3 alpha releases along with expanded network support and feature updates.
📝 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.

Suggested change
February brings a couple new HyperIndex V3 alpha release along with expanded network support and feature updates. We shipped HyperIndex v3.0.0 alpha.13 & alpha.14 with 3x faster historical backfills, support for DESC indices, improved RPC source support, experimental WebSocket support, and a breaking configuration change with `rpc_config` removed in favour of `rpc`, new getWhere API, removed ordered multichain mode support, big Cursor/Claude update and much more!
February brings a couple of new HyperIndex V3 alpha releases along with expanded network support and feature updates. We shipped HyperIndex v3.0.0 alpha.13 & alpha.14 with 3x faster historical backfills, support for DESC indices, improved RPC source support, experimental WebSocket support, and a breaking configuration change with `rpc_config` removed in favour of `rpc`, new getWhere API, removed ordered multichain mode support, big Cursor/Claude update and much more!
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@blog/2026-02-25-dev-update-february-2026.md` at line 12, Update the opening
sentence that currently reads "February brings a couple new HyperIndex V3 alpha
release..." to correct grammar: change it to "February brings a couple of new
HyperIndex V3 alpha releases..." (referencing the phrase containing "HyperIndex
v3.0.0 alpha.13 & alpha.14") so it includes the missing preposition "of" and
pluralizes "release" to "releases".


We expanded our indexing support to MegaETH mainnet and Sei. This month also includes a new multi part YouTube series on building with HyperIndex and updates to our Uniswap v4 alert bots. Let’s dive in!
We expanded our indexing support to MegaETH mainnet and Sei. This month also includes a new multi-part YouTube series on building with HyperIndex and updates to our Uniswap v4 alert bots. Let’s dive in!


## ⚡ New release: HyperIndex v3.0.0 - alpha.13
## ⚡ New release: HyperIndex v3.0.0 - alpha.13 & alpha.14

### Alpha.14

### 🚨 Breaking: New getWhere API

We updated our getWhere API to enable support for multiple filters at a time in future HyperIndex versions. Instead of chaining, it now uses a single function call with filters that match GraphQL style for familiarity.

```
Old: context.Entity.getWhere.fieldName.eq(value)
New: context.Entity.getWhere({ fieldName: { _eq: value } })
```
Comment on lines +25 to +28
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 18, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Add a language identifier to the fenced code block.

The code block shows a before/after diff of the getWhere API. Without a language specifier the block renders unstyled and triggers markdownlint MD040. Use diff for proper syntax highlighting.

✏️ Suggested fix 
-```
+```diff
 Old: context.Entity.getWhere.fieldName.eq(value)
 New: context.Entity.getWhere({ fieldName: { _eq: value } })
 ```
🧰 Tools
🪛 markdownlint-cli2 (0.21.0)

[warning] 25-25: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@blog/2026-02-25-dev-update-february-2026.md` around lines 25 - 28, The fenced
code block showing the getWhere API diff lacks a language identifier; update the
block that contains "Old: context.Entity.getWhere.fieldName.eq(value)" / "New:
context.Entity.getWhere({ fieldName: { _eq: value } })" by adding the language
specifier `diff` immediately after the opening triple backticks so the snippet
renders with proper syntax highlighting and resolves markdownlint MD040.

### 🔄 Breaking: Removed Ordered Multichain Mode Support
Comment on lines +28 to +29
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 18, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Missing blank line between closing code fence and next heading.

Some Markdown renderers (including Docusaurus/MDX) require a blank line between a closing ``` and the following ### heading. Without it, the heading may be parsed as continuation text of the fenced block.

✏️ Suggested fix 
 New: context.Entity.getWhere({ fieldName: { _eq: value } })

🔄 Breaking: Removed Ordered Multichain Mode Support

</details>

<details>
<summary>🤖 Prompt for AI Agents</summary>

Verify each finding against the current code and only fix it if needed.

In @blog/2026-02-25-dev-update-february-2026.md around lines 28 - 29, Add a
single blank line between the preceding closing code fence and the heading "###
🔄 Breaking: Removed Ordered Multichain Mode Support" so the heading is not
treated as part of the fenced code block; locate the closing ``` before that
heading and insert one empty line above the "### 🔄 Breaking: Removed Ordered
Multichain Mode Support" line.


</details>

<!-- fingerprinting:phantom:triton:churro -->

<!-- This is an auto-generated comment by CodeRabbit -->


Ordered Multichain Mode forced events across all processed chains into global onchain order, causing significant latency and allowing one bad chain to freeze the entire indexing process.
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 18, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Inconsistent hyphenation: "onchain" vs "on-chain".

Line 31 uses "onchain order" (no hyphen) while line 33 uses "on-chain order per chain" (hyphenated). Pick one form and apply it consistently throughout the section.

🧰 Tools
🪛 LanguageTool

[grammar] ~31-~31: Ensure spelling is correct
Context: ...across all processed chains into global onchain order, causing significant latency and ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@blog/2026-02-25-dev-update-february-2026.md` at line 31, The phrase "onchain"
appears inconsistently with "on-chain" in the "Ordered Multichain Mode"
paragraph; choose one hyphenation and normalize all occurrences in that section
(e.g., change "onchain order" to "on-chain order" or vice versa) by editing the
paragraph containing the "Ordered Multichain Mode" heading and the sentence that
mentions "on-chain order per chain" so both use the same form.


Events are still processed in on-chain order per chain.
For cross-chain interactions, create a partial entity on one chain and finalize it when the related event arrives on another chain. This provides lower latency and a more reliable system.

### 🤖 Big Cursor/Claude Skills Update

We updated `envio init` to create projects with multiple skills to support agentic driven development.
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 18, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Hyphenate the compound modifier "agentic-driven".

"agentic driven development" should be "agentic-driven development" when used as a compound adjective before a noun.

✏️ Suggested fix 
-We updated `envio init` to create projects with multiple skills to support agentic driven development.
+We updated `envio init` to create projects with multiple skills to support agentic-driven development.
📝 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.

Suggested change
We updated `envio init` to create projects with multiple skills to support agentic driven development.
We updated `envio init` to create projects with multiple skills to support agentic-driven development.
🧰 Tools
🪛 LanguageTool

[grammar] ~38-~38: Use a hyphen to join words.
Context: ... with multiple skills to support agentic driven development. The LLM landscape c...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@blog/2026-02-25-dev-update-february-2026.md` at line 38, The phrase "agentic
driven development" should be hyphenated as the compound modifier
"agentic-driven" before "development"; update the sentence that mentions `envio
init` so it reads "...to support agentic-driven development" replacing "agentic
driven development" with "agentic-driven development".


The LLM landscape changes quickly, so we welcome feedback to improve the skills and the development experience with them.

### ⛓️ Chain Info for Test Indexer

```
const indexer = createTestIndexer();

indexer.chainIds
indexer.chains

indexer.chains[1].id
indexer.chains[1].name
indexer.chains[1].startBlock
indexer.chains[1].endBlock

indexer.chains[1].ERC20.abi
indexer.chains[1].ERC20.addresses // Useful to test dynamic registrations
```
Comment on lines +44 to +57
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 18, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Add a language identifier to the fenced code block.

The snippet is TypeScript/JavaScript. Specifying the language enables syntax highlighting and satisfies markdownlint MD040.

✏️ Suggested fix 
-```
+```typescript
 const indexer = createTestIndexer();
 ...
🧰 Tools
🪛 markdownlint-cli2 (0.21.0)

[warning] 44-44: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@blog/2026-02-25-dev-update-february-2026.md` around lines 44 - 57, The fenced
code block containing TypeScript usage (e.g., createTestIndexer(),
indexer.chainIds, indexer.chains, indexer.chains[1].ERC20.abi) needs a language
identifier for syntax highlighting and to satisfy markdownlint MD040; change the
opening fence from ``` to ```typescript so the snippet is recognized as
TypeScript/JavaScript and leave the rest of the block unchanged.


### Alpha.13

This alpha release focused on performance improvements, expanded indexing capabilities, and RPC configuration changes as we continue iterating on V3.

Expand Down Expand Up @@ -210,4 +252,4 @@ Stay tuned for more monthly updates by subscribing to our newsletter, following

[Subscribe to our newsletter](https://envio.beehiiv.com/subscribe?utm_source=envio.beehiiv.com&utm_medium=newsletter&utm_campaign=new-post) 💌

[Website](https://envio.dev/) | [X](https://twitter.com/envio_indexer) | [Discord](https://discord.com/invite/gt7yEUZKeB) | [Telegram](https://t.me/+5mI61oZibEM5OGQ8) | [GitHub](https://github.com/enviodev) | [YouTube](https://www.youtube.com/channel/UCR7nZ2yzEtc5SZNM0dhrkhA) | [Reddit](https://www.reddit.com/user/Envio_indexer)
[Website](https://envio.dev/) | [X](https://twitter.com/envio_indexer) | [Discord](https://discord.com/invite/gt7yEUZKeB) | [Telegram](https://t.me/+5mI61oZibEM5OGQ8) | [GitHub](https://github.com/enviodev) | [YouTube](https://www.youtube.com/channel/UCR7nZ2yzEtc5SZNM0dhrkhA) | [Reddit](https://www.reddit.com/user/Envio_indexer)