blog: update Polymarket event count across AI blogs

[Jordy-Baby]

Summary

Propagates the Polymarket event-count correction from #920 to the three other recently merged AI blogs. @DZakh flagged on #914 that the "4,000,000,000 events" figure is stale ("It's 6,509,376,000 now"); the same understated figure appeared across the other three posts.

The 4B-in-6-days number is the initial historical sync milestone (still true, documented in the Polymarket case study). The indexer has kept running and is now past 6.5B. Each occurrence now keeps the verifiable sync milestone and adds the current total.

Changes — 7 occurrences across 3 blogs

ai-subgraph-migration-hyperindex-claude.md (3)

• TL;DR, the "full historical sync" paragraph, and the FAQ

ai-onchain-app-hyperindex-claude.md (3)

• TL;DR, the local-dev paragraph, and the FAQ
• Note: the local-dev line attributes the figure to the Polymarket case study — kept "4,000,000,000 ... in 6 days" as what the case study documents (accurate) and added the current total as a separate clause, rather than misattributing 6.5B to the case study.

ai-agents-acting-onchain-indexer.md (1)

• The "HyperSync historical throughput" bullet

Wording

"over 6,500,000,000" / "over 6.5B" rather than the exact 6,509,376,000 — the count grows continuously, so an exact figure is stale on publish. Consistent with the phrasing used in #920.

Pre-flight checks

• scripts/validate-blog-social-images.js passes (65 posts)
• All 7 occurrences updated
• Case-study attribution kept accurate (no misattribution of the 6.5B figure)

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
envio-docs	Ready	Preview, Comment	May 15, 2026 3:44pm

[coderabbitai]

Warning

Rate limit exceeded

@Jordy-Baby has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 39 minutes and 9 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e52ffc84-002c-44dd-9cf5-dc8bd7a0e373

📥 Commits

Reviewing files that changed from the base of the PR and between aa4a430 and 5167e63.

📒 Files selected for processing (3)

• blog/2026-05-14-ai-agents-acting-onchain-indexer.md
• blog/2026-05-14-ai-onchain-app-hyperindex-claude.md
• blog/2026-05-14-ai-subgraph-migration-hyperindex-claude.md

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}