Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Rate limit exceeded@Jordy-Baby has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 20 minutes and 9 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (19)
WalkthroughThis pull request updates 43 blog posts with consistent branding and messaging changes. The updates standardize Envio's product description, normalize terminology from "multi-chain" to "multichain," replace the "Ship with us" section with "About Envio," modernize social links, and refactor closing call-to-action blocks across all posts. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Notes:
Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
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. Comment |
Jordy-Baby
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 59
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
blog/2024-08-13-case-study-sablier.md (1)
13-13: Update terminology to "multichain" throughout body content of this file.The review comment is correct. Script verification confirms the file contains six instances of "multi-chain" (lines 13, 15, 29, 31, 45, 62) while the title and description use "Multichain." This inconsistency violates the PR's stated objective to normalize to "multichain" without hyphens.
Apply all six corrections as listed in the original comment to align body content with the standardized terminology established in the file's metadata.
blog/2025-03-31-envio-dev-update-march-2025.md (1)
302-311: Replace "Ship with us" footer with standardized "About Envio" section to complete the batch update.This file is part of the PR's blog footer consolidation (56 files modified), but the footer section at lines 302–311 was not updated. While the body content was changed, the "Ship with us. 🚢" section remains. Replace it with the standardized "About Envio" format to match the other updated files:
-## Ship with us. 🚢 - -[Envio](https://envio.dev/) is a modern, multi-chain EVM blockchain indexing framework that is speed-optimized for querying real-time and historical data. - -If you're a blockchain developer looking to enhance your development process and unlock the true potential of Web3 infrastructure, look no further. Join our growing community of elite developers, check out our docs, and let's work together to revolutionize the blockchain world and propel your project to the next level. - -Stay tuned for more monthly updates by subscribing to our newsletter, following us on X, or hopping into our Discord for more up-to-date information. - - -[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) | [Farcaster](https://warpcast.com/envio) | [Medium](https://medium.com/@Envio_Indexer) | [YouTube](https://www.youtube.com/channel/UCR7nZ2yzEtc5SZNM0dhrkhA) | [Reddit](https://www.reddit.com/user/Envio_indexer) | [GitHub](https://github.com/enviodev) +## About Envio + +[Envio](https://envio.dev) is a fast, developer-friendly blockchain indexer and the fastest, most flexible way to get on-chain data, making real-time data accessible for developers across the Web3 ecosystem. + +With Envio, developers can query and stream blockchain data efficiently without the complexity of running their own infrastructure. Envio's blockchain indexing tools supports any EVM network and is trusted by many teams building everything from DeFi platforms to analytics dashboards and production applications. + +If you're a blockchain developer or analyst looking to enhance your workflow, look no further. Join our growing community of Web3 builders and explore our docs. + +[Website](https://envio.dev/) | [X](https://twitter.com/envio_indexer) | [Discord](https://discord.com/invite/gt7yEUZKeB) | [Farcaster](https://warpcast.com/envio) | [GitHub](https://github.com/enviodev) | [Medium](https://medium.com/@Envio_Indexer)
🧹 Nitpick comments (4)
blog/2023-10-04-how-to-become-a-blockchain-dapp-developer.md (1)
105-113: Compound adjective on line 107 needs hyphenation; overall section is professional and on-brand.The new "About Envio" section and consolidated social footer align well with the PR's branding standardization objectives. However, line 107 contains a compound adjective that should be hyphenated.
Apply this diff:
-[Envio](https://envio.dev) is a fast, developer friendly blockchain indexer and the fastest, most flexible way to get on-chain data, making real-time data accessible for developers across the Web3 ecosystem. +[Envio](https://envio.dev) is a fast, developer-friendly blockchain indexer and the fastest, most flexible way to get on-chain data, making real-time data accessible for developers across the Web3 ecosystem.blog/2024-10-29-envio-community-update-oct-2024.md (1)
151-157: Fix hyphenation in "About Envio" description across all affected blog posts.Line 151 uses "developer friendly" which should be hyphenated as a compound adjective modifying "blockchain indexer". This grammar issue appears systematically across approximately 44 blog posts in the repository—a standardization opportunity for this PR.
Apply this diff to the target file:
-[Envio](https://envio.dev) is a fast, developer friendly blockchain indexer and the fastest, most flexible way to get on-chain data, making real-time data accessible for developers across the Web3 ecosystem. +[Envio](https://envio.dev) is a fast, developer-friendly blockchain indexer and the fastest, most flexible way to get on-chain data, making real-time data accessible for developers across the Web3 ecosystem.Consider applying this fix systematically across all blog posts that contain this phrase to ensure consistency.
blog/2025-01-21-what-is-a-blockchain-indexer.md (1)
24-24: Fix markdown structure: use proper heading levels instead of emphasis for section titles.Sections labeled with
**4. Multichain Support**,**5. Customizability**, and**6. Hosted Service**should use####heading syntax instead of bold emphasis, per markdownlint rules.Apply this diff:
-**4. Multichain Support** +#### 4. Multichain Support -**5. Customizability** +#### 5. Customizability -**6. Hosted Service** +#### 6. Hosted ServiceAlso applies to: 40-40, 44-44
blog/2024-02-12-envio-azuro-developer-grant-multi-chain-open-source-indexer.md (1)
28-28: Improve link text for accessibility.The link text "here" is not descriptive; consider using more specific text that indicates the destination or purpose.
For example:
-Learn more about the grant opportunity [here](https://docs.envio.dev/blog/envio-azuro-developer-grant-multi-chain-indexer). +Learn more about the [Envio & Azuro grant opportunity](https://docs.envio.dev/blog/envio-azuro-developer-grant-multi-chain-indexer).
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (56)
blog/2023-08-08-methods-to-query-blockchain-data.md(3 hunks)blog/2023-08-17-what-is-an-indexer.md(2 hunks)blog/2023-08-22-envio-grant-program-is-live.md(3 hunks)blog/2023-08-31-navigating-challenges-in-blockchain-indexing.md(3 hunks)blog/2023-09-06-envio-community-update-1.md(1 hunks)blog/2023-09-27-envio-community-update-2.md(1 hunks)blog/2023-10-04-how-to-become-a-blockchain-dapp-developer.md(2 hunks)blog/2023-10-19-envio-celebrates-first-grantee-project-multi-chain-liquidation-metrics-indexer.md(2 hunks)blog/2023-10-24-indexer-benchmarking-results.md(6 hunks)blog/2023-10-26-envio-community-update-3.md(2 hunks)blog/2023-11-09-powers-of-dedicated-hosting-for-web3-apps.md(3 hunks)blog/2023-11-15-simplify-data-retrieval-multi-chain-dapps.md(4 hunks)blog/2023-11-23-envio-bounty-poap-multi-chain-indexer.md(2 hunks)blog/2023-11-29-envio-community-update-4.md(1 hunks)blog/2023-12-13-envio-bounty-erc4626-token-vault-indexer.md(3 hunks)blog/2023-12-19-envio-community-update-5.md(1 hunks)blog/2024-01-17-envio-empowers-jarvis-network.md(3 hunks)blog/2024-01-31-envio-community-update-6.md(1 hunks)blog/2024-02-12-envio-azuro-developer-grant-multi-chain-open-source-indexer.md(3 hunks)blog/2024-02-20-envio-data-indexing-on-lukso.md(2 hunks)blog/2024-03-01-envio-community-update-7.md(2 hunks)blog/2024-03-27-envio-community-update-8.md(1 hunks)blog/2024-03-27-envio-data-indexing-on-harmony.md(1 hunks)blog/2024-03-28-envio-celebrates-azuro-indexer-grantee.md(2 hunks)blog/2024-04-22-envio-hypersync-powers-data-access-on-fuel-network.md(1 hunks)blog/2024-05-08-envio-community-update-9.md(1 hunks)blog/2024-05-24-case-study-peppy-finance.md(1 hunks)blog/2024-05-30-envio-community-update-may-2024.md(1 hunks)blog/2024-07-01-envio-community-update-june-2024.md(1 hunks)blog/2024-07-17-case-study-gblast.md(2 hunks)blog/2024-08-13-case-study-sablier.md(1 hunks)blog/2024-08-19-building-chaindensity.md(1 hunks)blog/2024-09-27-case-study-limitless.md(3 hunks)blog/2024-10-09-case-study-bridgg-op-superchain.md(0 hunks)blog/2024-10-15-ethonline24-envio-hackathon-winners.md(1 hunks)blog/2024-10-29-envio-community-update-oct-2024.md(1 hunks)blog/2024-11-08-hosted-service-v2.md(1 hunks)blog/2024-11-13-how-to-cut-aws-cloud-costs.md(3 hunks)blog/2024-11-26-indexing-and-reorgs.md(1 hunks)blog/2024-12-09-tokenizing-real-world-assets.md(1 hunks)blog/2024-12-18-case-study-zkpass.md(3 hunks)blog/2024-12-24-envio-community-update-december.md(2 hunks)blog/2025-01-21-what-is-a-blockchain-indexer.md(4 hunks)blog/2025-03-17-what-is-multi-chain-indexing.md(4 hunks)blog/2025-03-26-envio-supports-70-networks.md(4 hunks)blog/2025-03-31-envio-dev-update-march-2025.md(3 hunks)blog/2025-04-15-oracle-wars.md(1 hunks)blog/2025-05-16-monad-hackathon-winners-2025.md(2 hunks)blog/2025-06-12-how-to-index-monad-data-using-envio.md(3 hunks)blog/2025-06-17-how-to-index-megaeth-data-using-envio.md(2 hunks)blog/2025-06-24-building-visualizers-and-dashboards-on-monad.md(2 hunks)blog/2025-06-24-dev-update-june-2025.md(2 hunks)blog/2025-07-30-dev-update-july-2025.md(1 hunks)blog/2025-08-29-dev-update-august-2025.md(1 hunks)blog/2025-09-30-dev-update-september-2025.md(1 hunks)blog/2025-10-28-dev-update-october-2025.md(1 hunks)
💤 Files with no reviewable changes (1)
- blog/2024-10-09-case-study-bridgg-op-superchain.md
🧰 Additional context used
🪛 LanguageTool
blog/2024-08-19-building-chaindensity.md
[grammar] ~140-~140: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2023-11-29-envio-community-update-4.md
[grammar] ~108-~108: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-10-15-ethonline24-envio-hackathon-winners.md
[grammar] ~65-~65: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2023-10-24-indexer-benchmarking-results.md
[grammar] ~135-~135: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-10-29-envio-community-update-oct-2024.md
[grammar] ~151-~151: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2023-08-08-methods-to-query-blockchain-data.md
[grammar] ~84-~84: Ensure spelling is correct
Context: ... GraphQL. Blockchain indexing solutions liek Envio abstract away a lot of the comple...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~99-~99: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2023-10-26-envio-community-update-3.md
[grammar] ~88-~88: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-12-09-tokenizing-real-world-assets.md
[grammar] ~79-~79: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-11-08-hosted-service-v2.md
[grammar] ~67-~67: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-12-18-case-study-zkpass.md
[grammar] ~99-~99: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2023-11-23-envio-bounty-poap-multi-chain-indexer.md
[grammar] ~54-~54: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2023-09-27-envio-community-update-2.md
[grammar] ~73-~73: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-03-01-envio-community-update-7.md
[grammar] ~265-~265: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2023-12-19-envio-community-update-5.md
[grammar] ~113-~113: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-07-01-envio-community-update-june-2024.md
[grammar] ~97-~97: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-03-27-envio-community-update-8.md
[grammar] ~193-~193: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-01-17-envio-empowers-jarvis-network.md
[grammar] ~83-~83: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2023-09-06-envio-community-update-1.md
[grammar] ~70-~70: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2023-08-31-navigating-challenges-in-blockchain-indexing.md
[grammar] ~48-~48: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-05-30-envio-community-update-may-2024.md
[grammar] ~123-~123: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2025-05-16-monad-hackathon-winners-2025.md
[grammar] ~66-~66: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-02-20-envio-data-indexing-on-lukso.md
[grammar] ~50-~50: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-02-12-envio-azuro-developer-grant-multi-chain-open-source-indexer.md
[grammar] ~101-~101: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2023-11-15-simplify-data-retrieval-multi-chain-dapps.md
[style] ~29-~29: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...Contract Example A Greeter contract is a very simple smart contract that allows a user to wr...
(EN_WEAK_ADJECTIVE)
[style] ~102-~102: Consider a different adjective to strengthen your wording.
Context: ...now-live). ## Conclusion By gaining a deep understanding of how multichain indexin...
(DEEP_PROFOUND)
[grammar] ~106-~106: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-04-22-envio-hypersync-powers-data-access-on-fuel-network.md
[grammar] ~146-~146: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-05-24-case-study-peppy-finance.md
[grammar] ~73-~73: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-07-17-case-study-gblast.md
[grammar] ~89-~89: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2025-03-26-envio-supports-70-networks.md
[grammar] ~73-~73: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2023-10-04-how-to-become-a-blockchain-dapp-developer.md
[grammar] ~107-~107: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-09-27-case-study-limitless.md
[grammar] ~113-~113: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-03-27-envio-data-indexing-on-harmony.md
[grammar] ~48-~48: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2023-08-22-envio-grant-program-is-live.md
[grammar] ~16-~16: Ensure spelling is correct
Context: ...ilding brilliant dApps. This is where blcockhain indexing solutions like Envio come in. ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~79-~79: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-05-08-envio-community-update-9.md
[grammar] ~226-~226: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2025-01-21-what-is-a-blockchain-indexer.md
[grammar] ~34-~34: Ensure spelling is correct
Context: ...#### 3. Responsive Apps Blockchain ndexers are optimized for low-latency queries, ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~106-~106: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2023-11-09-powers-of-dedicated-hosting-for-web3-apps.md
[grammar] ~57-~57: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2023-10-19-envio-celebrates-first-grantee-project-multi-chain-liquidation-metrics-indexer.md
[style] ~19-~19: The word “free” tends to be overused. Consider using an alternative wording to strengthen your writing.
Context: ...t going to be able to build a bot in my free time that competes with bots funded by fully...
(FREE_TIME)
[grammar] ~21-~21: Ensure spelling is correct
Context: ...e into how Joss approached building his blcockhain indexer using Envio 👇 For milestone A...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~170-~170: Ensure spelling is correct
Context: ... The most noticeable difference between theGraph and Envio is indexing speed. Anyone who...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~170-~170: Ensure spelling is correct
Context: ... is indexing speed. Anyone who has used theGraph is familiar with the feeling of a corti...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~174-~174: Consider a more concise word here.
Context: ...e supply of crypto assets as collateral in order to borrow the base asset. Accounts can a...
(IN_ORDER_TO_PREMIUM)
[grammar] ~178-~178: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2023-12-13-envio-bounty-erc4626-token-vault-indexer.md
[grammar] ~68-~68: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-11-26-indexing-and-reorgs.md
[grammar] ~124-~124: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-08-13-case-study-sablier.md
[grammar] ~138-~138: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2025-04-15-oracle-wars.md
[grammar] ~109-~109: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-03-28-envio-celebrates-azuro-indexer-grantee.md
[grammar] ~70-~70: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-11-13-how-to-cut-aws-cloud-costs.md
[grammar] ~140-~140: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2023-08-17-what-is-an-indexer.md
[grammar] ~22-~22: Use a hyphen to join words.
Context: ...ar and fast way to view and work with on chain activity. Similar to the index of ...
(QB_NEW_EN_HYPHEN)
[grammar] ~22-~22: Use a hyphen to join words.
Context: ...the index of a book, it takes complex on chain data and organises it so developer...
(QB_NEW_EN_HYPHEN)
[grammar] ~108-~108: Use a hyphen to join words.
Context: ...e dApp development process: - Developer friendly: Blockchain indexing solutions ...
(QB_NEW_EN_HYPHEN)
[grammar] ~120-~120: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
blog/2024-01-31-envio-community-update-6.md
[grammar] ~114-~114: Use a hyphen to join words.
Context: ...(https://envio.dev) is a fast, developer friendly blockchain indexer and the fast...
(QB_NEW_EN_HYPHEN)
🪛 markdownlint-cli2 (0.18.1)
blog/2024-01-17-envio-empowers-jarvis-network.md
16-16: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
blog/2024-02-12-envio-azuro-developer-grant-multi-chain-open-source-indexer.md
28-28: Link text should be descriptive
(MD059, descriptive-link-text)
blog/2023-10-04-how-to-become-a-blockchain-dapp-developer.md
29-29: Link text should be descriptive
(MD059, descriptive-link-text)
blog/2025-01-21-what-is-a-blockchain-indexer.md
24-24: Heading levels should only increment by one level at a time
Expected: h3; Actual: h5
(MD001, heading-increment)
36-36: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
40-40: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
44-44: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
blog/2025-06-12-how-to-index-monad-data-using-envio.md
24-24: Heading levels should only increment by one level at a time
Expected: h3; Actual: h4
(MD001, heading-increment)
blog/2023-11-09-powers-of-dedicated-hosting-for-web3-apps.md
20-20: Link text should be descriptive
(MD059, descriptive-link-text)
43-43: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
blog/2023-10-19-envio-celebrates-first-grantee-project-multi-chain-liquidation-metrics-indexer.md
16-16: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
🔇 Additional comments (52)
blog/2023-10-04-how-to-become-a-blockchain-dapp-developer.md (1)
12-12: Content updates are clear and well-articulated.The reworded intro, grammatical improvements (singular "dApp" in header), and clarified descriptions of frontend, smart contracts, RPC communication, and the section header all enhance readability and accuracy without altering the core message.
Also applies to: 14-14, 22-22, 26-26, 32-32, 34-34, 99-99
blog/2024-05-08-envio-community-update-9.md (1)
224-232: Closing section updates align well with PR objectives.The rebranding of "Ship with us" to "About Envio" with modernized messaging and refreshed social links (Website, X, Discord, Farcaster, GitHub, Medium) are consistent with the standardization goals across the 43 blog posts in this PR. The new product description is clear and developer-focused.
blog/2023-08-31-navigating-challenges-in-blockchain-indexing.md (1)
12-12: Branding and terminology updates are well-executed and consistent.The changes successfully standardize terminology (e.g., "multi-chain" → "multichain"), position Envio prominently as the indexing solution throughout, replace the generic "Ship with us" section with a product-focused "About Envio" overview, and add consolidated external links (Website, X, Discord, Farcaster, GitHub, Medium). These updates align well with the PR objectives and improve the post's clarity and marketing positioning.
Also applies to: 24-26, 40-42, 46-54
blog/2024-01-31-envio-community-update-6.md (1)
112-120: New "About Envio" section successfully replaces legacy content.The updated section aligns well with the PR objectives: it replaces the "Ship with us" header with "About Envio," consolidates the product description around EVM compatibility and ease of use, and updates the social links to include Farcaster and GitHub. The copy is clear, focused on developer value, and consistent with the modernization efforts described in the PR summary.
blog/2025-06-17-how-to-index-megaeth-data-using-envio.md (3)
44-44: Heading update improves clarity.The revised heading "How to Index Data on MegaEth" is more descriptive and clearly conveys the post's instructional nature compared to the previous version.
117-117: Terminology standardization applied correctly.The change from "multi-chain" to "multichain" aligns with the PR's standardization objectives and reflects current industry convention. The rest of the About Envio section is well-written and accurately describes Envio's positioning.
1-120: Discrepancy between AI summary and annotated code.The AI summary states that "a new introductory descriptive paragraph [was] inserted between the existing HyperIndex and HyperSync sections" (lines 49–50), but these lines are not marked with
~in the annotated code, suggesting they were not changed in this PR. Only lines 44 and 117 are marked as modified. Please clarify whether the HyperIndex description paragraph was added as part of this change or was pre-existing.blog/2024-07-17-case-study-gblast.md (1)
12-12: LGTM. The reworded opening sentence flows naturally and establishes a direct, compelling hook tied to the GBlast integration example.blog/2024-04-22-envio-hypersync-powers-data-access-on-fuel-network.md (1)
146-152: Content and links align well with PR standardization objectives.The "About Envio" section (lines 146–148) now clearly articulates Envio's value proposition as a fast, EVM-native indexer that eliminates infrastructure overhead—consistent with the PR's goal to standardize messaging across blog posts. The updated CTA (line 150) invites a broad developer/analyst audience, and the refreshed social links (line 152) replace older channels with Farcaster and GitHub, aligning with the stated modernization of the link footers.
blog/2023-10-24-indexer-benchmarking-results.md (2)
55-57: Terminology standardization looks solid.The wording updates consistently shift from generic "indexers" to explicit "blockchain indexers" and "blockchain indexing solutions," which strengthens the technical framing and aligns with current marketing language. The copy refinements at lines 97, 116, 125, and 129 preserve the original analytical tone while sharpening clarity.
Also applies to: 97-97, 116-116, 125-125, 129-129
133-141: About Envio section is well-positioned and complete.The new promotional section cleanly replaces the previous closing with a cohesive company overview, inclusive social links (X, Discord, Farcaster, GitHub, Medium), and a clear call-to-action inviting developers to explore the docs and community. This aligns well with the PR's objective to modernize branding and social presence.
blog/2024-09-27-case-study-limitless.md (1)
52-59: Content updates align well with PR objectives.The section reframes ("What is Limitless Exchange?" and "How Envio powers Limitless's Daily Prediction Markets") and the standardized "About Envio" section with social links are consistent with the broader PR pattern for this documentation refresh. The marketing-focused messaging emphasizing real-time data access, developer ergonomics, and EVM network support is clear and well-positioned.
Also applies to: 113-119
blog/2024-02-20-envio-data-indexing-on-lukso.md (2)
14-16: Updated heading and description look good.The new "How to index data on LUKSO using Envio" heading provides better context, and the condensed Envio description balances technical detail with accessibility for the target audience.
23-23: Verify terminology consistency: "Multi-chain" vs. "multichain".The PR objectives indicate standardization from "multi-chain" to "multichain." Line 23 still uses "Multi-chain indexing" (hyphenated). Clarify whether this inconsistency is intentional or should be updated to align with the broader PR terminology updates.
blog/2024-12-24-envio-community-update-december.md (4)
55-55: LGTM!Star emoji placement is clean and the formatting looks good.
152-152: LGTM!Transition text is clear and guides readers to the newsletter/social links.
148-148: Verify terminology consistency: "multi-chain" should be "multichain".Line 148 uses the hyphenated form "multi-chain," but other sections of this file (lines 74, 76) and the PR objectives indicate a standardization to "multichain" (no hyphen). Confirm whether this line was intentionally left unchanged or if it's an oversight.
146-157: Verify footer section updates.Based on the PR summary, the footer should reflect updated branding and link consolidation. Confirm:
- Should "Ship with us. 🚢" (line 146) be replaced with "About Envio"?
- Should the social links (line 157) be updated to remove YouTube, Reddit, and Hey (as mentioned in the PR objectives)?
The current footer may be incomplete relative to the broader PR changes across 43 blog posts.
blog/2024-08-19-building-chaindensity.md (1)
138-146: About Envio update aligns with PR objectives.The updated "About Envio" section and social links refresh are consistent with the PR objectives. The new messaging emphasizes Envio as a developer-friendly indexer with EVM support, the social links have been updated to include Farcaster and GitHub, and the closing CTA now targets Web3 builders and analysts—all of which align with the broader branding and messaging standardization across this PR.
blog/2024-08-13-case-study-sablier.md (2)
138-142: Fix hyphenation in "developer friendly".Line 138 uses "developer friendly" which should be hyphenated as "developer-friendly" per standard English style for compound adjectives. The rewritten About Envio section reads well otherwise and aligns with the updated branding; please apply this single correction.
-[Envio](https://envio.dev) is a fast, developer friendly blockchain indexer and the fastest, most flexible way to get on-chain data, making real-time data accessible for developers across the Web3 ecosystem. +[Envio](https://envio.dev) is a fast, developer-friendly blockchain indexer and the fastest, most flexible way to get on-chain data, making real-time data accessible for developers across the Web3 ecosystem.Flagged by static analysis (QB_NEW_EN_HYPHEN).
144-144: Social links update looks good.The updated social links section appropriately includes GitHub and removes legacy platforms, reflecting current Envio community presence. All URLs are well-formed and relevant.
blog/2023-10-19-envio-celebrates-first-grantee-project-multi-chain-liquidation-metrics-indexer.md (1)
176-184: About Envio section refresh looks solid.The rewrite elevates the header level, modernizes the messaging to position Envio as a fast and developer-friendly tool for cross-chain data access, and includes comprehensive social/product links. This aligns well with the PR's standardization goals.
blog/2025-07-30-dev-update-july-2025.md (1)
135-143: Terminology standardization looks good.The shift from "multi-chain" to "multichain" aligns with the broader branding updates in this PR and reflects industry-standard terminology. The Ship With Us section is clear and compelling.
blog/2025-09-30-dev-update-september-2025.md (1)
214-223: Terminology update applied consistently.The "multichain" terminology normalizes well with the product description. Ship With Us section messaging is consistent with other updated posts.
blog/2025-10-28-dev-update-october-2025.md (1)
196-205: Consistent terminology update.The multichain terminology is properly applied. Ship With Us messaging follows the established pattern from the other updated posts.
blog/2025-08-29-dev-update-august-2025.md (1)
219-228: Terminology standardization applied.Multichain terminology is consistent with the other updated dev updates. Ship With Us messaging is aligned with the broader PR changes.
blog/2025-06-24-dev-update-june-2025.md (2)
12-12: Terminology updated throughout the post.The "multichain" terminology shift on line 12 is consistent with the PR's broader branding refresh and reads more naturally in the introductory sentence.
190-199: Ship With Us section aligns with standardized messaging.The multichain terminology on line 192 is consistent with the other updated dev updates and maintains the clear, developer-friendly tone.
blog/2025-06-12-how-to-index-monad-data-using-envio.md (2)
38-38: Heading update improves clarity.The change from "Start Indexing Data on Monad" to "How to Index Data on Monad" makes the section title more direct and consistent with other tutorial headings in the post.
109-115: About Envio section with consistent branding.The multichain terminology on line 111 aligns with the standardized messaging across the PR. The About Envio block provides clear information about Envio's capabilities and maintains consistency with other updated posts.
blog/2025-06-24-building-visualizers-and-dashboards-on-monad.md (2)
133-159: Structured indexing stack documentation improves clarity.The new subsections for HyperIndex, HyperSync, and HyperRPC provide valuable context and structure, making it easier for developers to understand Envio's tooling. The heading change from "Index" to "Indexing" improves consistency with other tutorial posts.
167-171: About Envio section with consistent multichain terminology.The About Envio block on line 169 uses the standardized "multichain" terminology and provides clear value prop messaging consistent with other updated posts. Links are properly formatted.
blog/2025-04-15-oracle-wars.md (1)
107-115: No duplication found. The About Envio section appears only once in the file.The verification confirms that the "About Envio" block appears exactly once (lines 107-115) in blog/2025-04-15-oracle-wars.md. There is no duplicate or unintended repetition of this content elsewhere in the post.
Likely an incorrect or invalid review comment.
blog/2025-01-21-what-is-a-blockchain-indexer.md (1)
22-22: Add hyphens to compound modifiers "on-chain".These phrases are used as modifiers and should be hyphenated for consistency.
Apply this diff:
-A blockchain indexer is a specialized tool designed to simplify the process of working with on-chain data. It organizes complex data into a structured, ready-to-use format, making it far easier for you to query and retrieve the exact data you need. +A blockchain indexer is a specialized tool designed to simplify the process of working with on-chain data. It organizes complex data into a structured, ready-to-use format, making it far easier for you to query and retrieve the exact data you need.(Note: The provided text already contains "on-chain" correctly hyphenated; this may be a false positive from the linter.)
Likely an incorrect or invalid review comment.
blog/2023-08-08-methods-to-query-blockchain-data.md (1)
97-105: New About Envio section aligns with PR objectives.The replacement of the closing section with a standardized "About Envio" block and consolidated social links follows the intended branding update pattern.
blog/2024-05-30-envio-community-update-may-2024.md (1)
121-129: About Envio section properly replaces community call-to-action.Standardized messaging and consolidated social links follow the PR's branding update pattern.
blog/2023-11-29-envio-community-update-4.md (1)
106-114: About Envio section properly replaces "Ship with us" block.Standardized messaging and social links follow the PR pattern.
blog/2024-11-08-hosted-service-v2.md (1)
65-73: About Envio section properly positioned with consolidated social links.The file appropriately includes both a hosted-service-specific section (line 58) and a general product description section (line 65).
blog/2023-09-06-envio-community-update-1.md (1)
68-76: About Envio section replaces closing content with standardized messaging.New section follows the PR's branding consolidation pattern.
blog/2023-09-27-envio-community-update-2.md (1)
71-79: About Envio section replaces old content with standardized messaging.Section follows the PR's branding consolidation pattern.
blog/2024-03-28-envio-celebrates-azuro-indexer-grantee.md (2)
29-31: Bullet point formatting improvements.Trailing content has been cleaned up for consistency.
68-76: About Envio section replaces old content with standardized messaging.Section follows the PR's branding consolidation pattern.
blog/2025-03-31-envio-dev-update-march-2025.md (2)
13-13: Text update for clarity.Removal of "Continues to" in the intro improves sentence flow.
258-265: Multichain terminology updated consistently.Lines 258 and 262–265 correctly normalize "multi-chain" to "multichain" per PR objectives.
blog/2023-12-13-envio-bounty-erc4626-token-vault-indexer.md (1)
15-15: Branding and messaging updates look good.The standardized "About Envio" section (lines 66–74) with consolidated social links and updated product description aligns well with the PR objectives. The marketing copy refinements on lines 15 and 48 strengthen clarity around Envio's positioning.
Also applies to: 48-48, 66-74
blog/2023-10-26-envio-community-update-3.md (1)
15-15: Standardized About Envio section and social links.The replacement of the "Ship with us" section with a polished "About Envio" block (lines 86–94) maintains consistent messaging across the blog and consolidates social links effectively.
Also applies to: 86-94
blog/2024-05-24-case-study-peppy-finance.md (1)
71-79: Standardized About Envio block with consolidated social links.The updated About Envio section (lines 71–79) follows the consistent pattern across the PR with standardized product messaging and a consolidated footer of social/resource links.
blog/2025-03-17-what-is-multi-chain-indexing.md (1)
2-5: Comprehensive multichain terminology normalization.This file systematically updates "multi-chain" to "multichain" throughout (front matter, headings, body text). The terminology change is consistent and aligns with the PR's goal to standardize Envio's terminology across blog posts. The About Envio section (lines 123–124) is updated with the multichain descriptor.
Also applies to: 13-13, 15-15, 18-18, 20-20, 29-29, 32-32, 37-37, 42-42, 47-47, 52-52, 55-55, 57-57, 60-60, 67-67, 74-74, 97-97, 101-101, 106-106, 116-116, 118-118, 123-124
blog/2023-11-15-simplify-data-retrieval-multi-chain-dapps.md (2)
81-81: Verify syntax in TypeScript code snippet.Line 81 shows
import { GreetingEntity } *from* "../generated/src/Types.gen";with asterisks aroundfrom. This appears to be a markdown rendering issue or typo. The import statement should use proper TypeScript syntax without asterisks.Apply this diff:
- import { GreetingEntity } *from* "../generated/src/Types.gen"; + import { GreetingEntity } from "../generated/src/Types.gen";
2-2: Comprehensive multichain terminology update with standardized About Envio section.The systematic "multi-chain" → "multichain" normalization across the file (title, headings, body) is thorough and consistent with PR objectives. The About Envio section (lines 104–112) follows the standardized format.
Also applies to: 3-3, 13-13, 15-15, 19-19, 21-21, 27-27, 29-29, 62-62, 96-96, 98-98, 102-102, 104-112
blog/2024-01-17-envio-empowers-jarvis-network.md (1)
12-12: Multichain terminology normalized and About Envio section standardized.The updates to lines 12, 18, 22, 57, 59, 63, and 69 systematically apply the multichain terminology across the post. The About Envio section (lines 81–89) follows the PR's standardized format with consolidated social links.
Also applies to: 18-18, 22-22, 57-57, 59-59, 63-63, 69-69, 81-89
blog/2023-11-09-powers-of-dedicated-hosting-for-web3-apps.md (1)
13-13: Content and branding updates are well-aligned.The rewordings on lines 13, 15, 21, and 41 strengthen the messaging around Envio's hosted service benefits. The standardized About Envio section (lines 55–63) with consolidated social links is consistent with the PR's branding refresh across all blog posts.
Also applies to: 15-15, 21-21, 41-41, 43-43, 55-63
...2023-10-19-envio-celebrates-first-grantee-project-multi-chain-liquidation-metrics-indexer.md
Outdated
Show resolved
Hide resolved
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
…hain-liquidation-metrics-indexer.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
2 participants
Summary by CodeRabbit
Documentation