envio-linux-arm64 3.15.0 → 3.16.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +40 -34
- package/envio.node +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
<div align="center">
|
|
2
|
-
<h1>HyperIndex
|
|
3
|
-
<p><strong>
|
|
2
|
+
<h1>HyperIndex</h1>
|
|
3
|
+
<p><strong>Build custom blockchain APIs and analytics. Real-time, with enterprise SLAs.</strong></p>
|
|
4
4
|
<p>
|
|
5
5
|
<a href="https://github.com/enviodev/hyperindex/releases"><img src="https://img.shields.io/github/release/enviodev/hyperindex.svg" alt="GitHub release" /></a>
|
|
6
6
|
<a href="https://github.com/enviodev/hyperindex/issues"><img src="https://img.shields.io/github/issues/enviodev/hyperindex.svg" alt="GitHub issues" /></a>
|
|
@@ -10,18 +10,20 @@
|
|
|
10
10
|
</p>
|
|
11
11
|
<p>
|
|
12
12
|
<a href="https://docs.envio.dev">Documentation</a> ·
|
|
13
|
-
<a href="https://envio.dev">
|
|
13
|
+
<a href="https://envio.dev">Envio Cloud</a> ·
|
|
14
|
+
<a href="https://github.com/enviodev/open-indexer-benchmark">Benchmark</a> ·
|
|
15
|
+
<a href="https://docs.envio.dev/docs/HyperIndex/quickstart-with-ai">Build with AI</a> ·
|
|
14
16
|
<a href="https://discord.gg/DhfFhzuJQh">Discord</a> ·
|
|
15
|
-
<a href="https://
|
|
17
|
+
<a href="https://envio.dev/pricing">Contact sales</a>
|
|
16
18
|
</p>
|
|
17
19
|
</div>
|
|
18
20
|
|
|
19
21
|
---
|
|
20
22
|
## What is HyperIndex?
|
|
21
23
|
|
|
22
|
-
HyperIndex is Envio's
|
|
24
|
+
HyperIndex is Envio's blockchain indexing framework. Choose the contracts and events to track, write TypeScript handlers that shape the data, and HyperIndex keeps it up to date across EVM chains, Solana and Fuel, handles chain reorgs, and serves the result as a GraphQL API or direct Postgres/ClickHouse SQL.
|
|
23
25
|
|
|
24
|
-
|
|
26
|
+
It reads chain data through [HyperSync](https://docs.envio.dev/docs/HyperSync/overview), Envio's blockchain data API, which is up to 2,000x faster than JSON-RPC. Run it yourself with Docker, or deploy to [Envio Cloud](https://docs.envio.dev/docs/HyperIndex/hosted-service). Cloud starts with a free development plan and scales with your project up to Dedicated infrastructure with a 99.99% uptime SLA.
|
|
25
27
|
|
|
26
28
|

|
|
27
29
|
|
|
@@ -31,12 +33,9 @@ Powered by [HyperSync](https://docs.envio.dev/docs/HyperSync/overview), Envio's
|
|
|
31
33
|
|
|
32
34
|
Most blockchain indexers are bottlenecked by RPC. HyperIndex isn't. HyperSync, the data engine underneath, is a purpose-built, Rust-based query layer that retrieves multiple blocks per round trip, cuts out the overhead, and makes historical backfills genuinely fast.
|
|
33
35
|
|
|
34
|
-
|
|
36
|
+
The [open indexer benchmark](https://github.com/enviodev/open-indexer-benchmark) tracks current speed results across scenarios, and HyperIndex passes every reliability check. Every number there comes from code in the repository, so you can run it yourself.
|
|
35
37
|
|
|
36
|
-
|
|
37
|
-
- **LBTC Token with RPC calls** (April 2025): HyperIndex completed in 3 minutes vs 3 hours 9 minutes for The Graph
|
|
38
|
-
|
|
39
|
-
[View full benchmark results →](https://docs.envio.dev/docs/HyperIndex/benchmarks)
|
|
38
|
+
[How the benchmarks work →](https://docs.envio.dev/docs/HyperIndex/benchmarks)
|
|
40
39
|
|
|
41
40
|
---
|
|
42
41
|
|
|
@@ -44,15 +43,14 @@ Independent benchmarks run by Sentio confirm it:
|
|
|
44
43
|
|
|
45
44
|
HyperIndex and HyperSync are the data layer for DeFi dashboards, protocol analytics, block explorers, stablecoin monitors, liquidation trackers, oracle comparisons, NFT explorers, and any application that needs fast, structured onchain data.
|
|
46
45
|
|
|
47
|
-
A few
|
|
46
|
+
A few apps built with them, from the showcase:
|
|
48
47
|
|
|
49
|
-
- [v4.xyz](https://v4.xyz): the hub for Uniswap V4 data and analytics,
|
|
50
|
-
- [Stable Volume](https://www.stablevolume.com/): real-time stablecoin transaction monitoring across
|
|
48
|
+
- [v4.xyz](https://v4.xyz): the hub for Uniswap V4 data and analytics, indexed in real time across chains
|
|
49
|
+
- [Stable Volume](https://www.stablevolume.com/): real-time stablecoin transaction monitoring across chains
|
|
51
50
|
- [Stable Radar](https://stable-radar.com): real-time USDC transaction dashboard across multiple chains
|
|
52
51
|
- [Liqo](https://liqo.xyz): multichain liquidation tracking for DeFi lending protocols
|
|
53
|
-
- [Safe Stats](https://safe-stats.vercel.app/): real-time analytics for Safe multisig activity across all chains
|
|
54
52
|
- [Oracle Wars](https://oraclewars.xyz/): real-time oracle price comparison across multiple oracles
|
|
55
|
-
- [Chain Density](https://chaindensity.xyz/): transaction and event density analysis for any address across
|
|
53
|
+
- [Chain Density](https://chaindensity.xyz/): transaction and event density analysis for any address across chains
|
|
56
54
|
- [LogTUI](https://www.npmjs.com/package/logtui): terminal UI for monitoring blockchain events in real-time
|
|
57
55
|
|
|
58
56
|
[See the full showcase →](https://docs.envio.dev/showcase)
|
|
@@ -62,34 +60,33 @@ A few things already running in production:
|
|
|
62
60
|
## Key Features
|
|
63
61
|
|
|
64
62
|
**Performance**
|
|
65
|
-
- Historical backfills at
|
|
66
|
-
- Up to
|
|
67
|
-
- Sync times reduced from days to minutes
|
|
63
|
+
- Historical backfills at 100,000+ events per second ([benchmarking](https://docs.envio.dev/docs/HyperIndex/benchmarking))
|
|
64
|
+
- Up to 2,000x faster than JSON-RPC via HyperSync (on by default, no config required)
|
|
68
65
|
- Fallback RPC support for reliability without touching your indexer code
|
|
69
66
|
|
|
70
67
|
**Multichain indexing**
|
|
71
68
|
- Index EVM, SVM, and Fuel blockchains from a single indexer
|
|
72
|
-
-
|
|
69
|
+
- Every chain on the [HyperSync network list](https://docs.envio.dev/docs/HyperSync/hypersync-supported-networks), plus any EVM chain via RPC
|
|
73
70
|
- Real-time indexing with reorg handling built in
|
|
74
71
|
|
|
75
72
|
**Developer experience**
|
|
76
73
|
- Auto-generate an indexer directly from a smart contract address or ABI, no manual setup required
|
|
77
|
-
- Write handlers in TypeScript, JavaScript
|
|
74
|
+
- Write handlers in TypeScript or ReScript, and plain JavaScript handler files load too
|
|
78
75
|
- Full local development environment with Docker
|
|
79
76
|
- GraphQL API generated automatically from your schema
|
|
80
77
|
- Wildcard topic indexing: index by event signatures across any contract, not just specified addresses
|
|
81
|
-
- Factory contract support for
|
|
78
|
+
- Factory contract support for dynamically registered contracts
|
|
82
79
|
- Onchain and off-chain data integration
|
|
83
80
|
- External API actions triggered by blockchain events
|
|
84
81
|
- Detailed logging and error reporting
|
|
85
82
|
|
|
86
83
|
**Deployment**
|
|
87
|
-
-
|
|
84
|
+
- [Envio Cloud](https://docs.envio.dev/docs/HyperIndex/hosted-service), managed hosting with static endpoints and built-in alerts, from a free development plan up to Dedicated deployments with an SLA of up to 99.99% uptime
|
|
88
85
|
- Self-hosted via Docker
|
|
89
86
|
- No vendor lock-in. Switch between HyperSync and RPC at any time
|
|
90
87
|
|
|
91
88
|
**Agentic development**
|
|
92
|
-
-
|
|
89
|
+
- Build and deploy with an AI agent using the Envio Cloud CLI (`envio-cloud`) and the [HyperIndex skills](https://github.com/enviodev/hyperindex/tree/main/packages/cli/templates/static/shared/.claude/skills) that `envio init` adds to every project
|
|
93
90
|
- An agent can scaffold, configure, and deploy a production-ready indexer without touching a config file. [400,000 events indexed in ~20 seconds](https://docs.envio.dev/blog/agentic-blockchain-indexing-envio-hyperindex)
|
|
94
91
|
- Powerful built-in testing framework purpose-built for AI-driven development. Agents can write, run, and iterate on handler tests in a tight feedback loop, catching regressions before deploy
|
|
95
92
|
|
|
@@ -97,7 +94,7 @@ A few things already running in production:
|
|
|
97
94
|
|
|
98
95
|
## Getting started
|
|
99
96
|
|
|
100
|
-
**Requirements**: Node.js, Docker
|
|
97
|
+
**Requirements**: Node.js 22.15 or newer, and Docker for local development. pnpm is recommended.
|
|
101
98
|
|
|
102
99
|
```bash
|
|
103
100
|
pnpx envio init
|
|
@@ -119,7 +116,7 @@ From there, three files define your indexer:
|
|
|
119
116
|
|
|
120
117
|
HyperSync is the data engine that makes HyperIndex fast. It's active by default for all supported networks, no configuration needed.
|
|
121
118
|
|
|
122
|
-
Instead of making individual RPC calls per block, HyperSync retrieves multiple data points per round trip with advanced filtering. The result
|
|
119
|
+
Instead of making individual RPC calls per block, HyperSync retrieves multiple data points per round trip with advanced filtering. The result is sync speeds up to 2,000x faster than JSON-RPC, lower infrastructure costs, and no rate limits to work around on supported networks.
|
|
123
120
|
|
|
124
121
|
HyperSync can also be used directly for custom data pipelines in Python, Rust, Node.js, and Go, independent of HyperIndex.
|
|
125
122
|
|
|
@@ -129,19 +126,17 @@ HyperSync can also be used directly for custom data pipelines in Python, Rust, N
|
|
|
129
126
|
|
|
130
127
|
## Supported networks
|
|
131
128
|
|
|
132
|
-
HyperIndex supports any EVM-compatible L1, L2, or L3, plus Fuel and Solana (
|
|
129
|
+
HyperIndex supports any EVM-compatible L1, L2, or L3, plus Fuel and Solana. Chains on the [HyperSync network list](https://docs.envio.dev/docs/HyperSync/hypersync-supported-networks) get first-class HyperSync support. For any EVM chain not on the HyperSync list, RPC-based indexing works out of the box. Solana indexing runs on HyperSync for Solana, with instruction-level handlers and IDL-aware decoding.
|
|
133
130
|
|
|
134
131
|
[Full network list →](https://docs.envio.dev/docs/HyperIndex/supported-networks)
|
|
135
132
|
|
|
136
133
|
---
|
|
137
134
|
|
|
138
|
-
## Migrating
|
|
139
|
-
|
|
140
|
-
HyperIndex has a dedicated migration guide that covers config conversion, schema mapping, and query differences in 3 steps. Envio also offers white-glove migration support. Reach out on Discord and the team will help you get set up.
|
|
135
|
+
## Migrating an existing indexer
|
|
141
136
|
|
|
142
|
-
|
|
137
|
+
The migration guides cover config conversion, schema mapping and query differences, and you can [migrate with an AI agent](https://docs.envio.dev/docs/HyperIndex/migrate-with-ai). If you run subgraphs, Envio can also migrate and host them for you with Subgraph Hosting, while your applications keep querying a subgraph-compatible endpoint. For hands-on help, see [services](https://envio.dev/pricing/services) or ask on Discord.
|
|
143
138
|
|
|
144
|
-
[Migration
|
|
139
|
+
[Migration guides →](https://docs.envio.dev/docs/HyperIndex/migration-guide)
|
|
145
140
|
|
|
146
141
|
---
|
|
147
142
|
|
|
@@ -155,16 +150,27 @@ Key sections:
|
|
|
155
150
|
- [Multichain Indexing](https://docs.envio.dev/docs/HyperIndex/multichain-indexing)
|
|
156
151
|
- [Wildcard Indexing](https://docs.envio.dev/docs/HyperIndex/wildcard-indexing)
|
|
157
152
|
- [Reorg Support](https://docs.envio.dev/docs/HyperIndex/reorgs-support)
|
|
158
|
-
- [
|
|
153
|
+
- [Envio Cloud](https://docs.envio.dev/docs/HyperIndex/hosted-service)
|
|
159
154
|
- [HyperSync as Data Source](https://docs.envio.dev/docs/HyperIndex/hypersync)
|
|
160
155
|
- [Migration Guide](https://docs.envio.dev/docs/HyperIndex/migration-guide)
|
|
161
156
|
|
|
162
157
|
---
|
|
163
158
|
|
|
159
|
+
## Build with an AI agent
|
|
160
|
+
|
|
161
|
+
HyperIndex works with Claude Code, Cursor, Codex and other coding agents.
|
|
162
|
+
|
|
163
|
+
- **Docs for agents.** Point your agent at [llms.txt](https://docs.envio.dev/llms.txt), or the full text at [llms-full.txt](https://docs.envio.dev/llms-full.txt).
|
|
164
|
+
- **Docs MCP server.** Add `https://docs.envio.dev/mcp` to your agent for `docs_search` and `docs_fetch`. See the [MCP server guide](https://docs.envio.dev/docs/HyperIndex/mcp-server).
|
|
165
|
+
- **Skills.** `pnpx envio init` adds the [HyperIndex skills](https://github.com/enviodev/hyperindex/tree/main/packages/cli/templates/static/shared/.claude/skills) to every new project. After upgrading `envio`, run `pnpm envio skills update` to refresh them.
|
|
166
|
+
- **Quickstart.** Follow [Quickstart with AI](https://docs.envio.dev/docs/HyperIndex/quickstart-with-ai) to go from a contract address to a deployed GraphQL API.
|
|
167
|
+
|
|
168
|
+
---
|
|
169
|
+
|
|
164
170
|
## Community and support
|
|
165
171
|
|
|
166
172
|
- Follow us on [X](https://twitter.com/envio_indexer)
|
|
167
|
-
- Join the [Discord](https://discord.gg/DhfFhzuJQh), fastest
|
|
173
|
+
- Join the [Discord](https://discord.gg/DhfFhzuJQh) or [Telegram](https://t.me/+BeS5ihVUFONjNGFk), the fastest ways to get help
|
|
168
174
|
- Open an issue on [GitHub](https://github.com/enviodev/hyperindex/issues/new/choose)
|
|
169
175
|
- Browse [common issues](https://docs.envio.dev/docs/common-issues) for quick troubleshooting
|
|
170
176
|
|
package/envio.node
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
1
|
[diffend] Oversized file quarantined before diffing.
|
|
2
2
|
name: package/envio.node
|
|
3
|
-
size:
|
|
4
|
-
sha256:
|
|
3
|
+
size: 50267568 bytes
|
|
4
|
+
sha256: 3674a308e1f6cfedf35f14dcda82c5505ce42488fa3cc47e9df8e1124d7fcb58
|