envio 3.0.0-alpha.2 → 3.0.0-alpha.21

package/README.md

@@ -1,45 +1,179 @@
-# HyperIndex: Ultra-Fast Multichain Indexer
+<div align="center">
+  <h1>HyperIndex: Ultra-Fast Multichain Indexer</h1>
+  <p><strong>The fastest independently benchmarked multichain blockchain indexer.</strong></p>
+  <p>
+    <a href="https://github.com/enviodev/hyperindex/releases"><img src="https://img.shields.io/github/release/enviodev/hyperindex.svg" alt="GitHub release" /></a>
+    <a href="https://github.com/enviodev/hyperindex/issues"><img src="https://img.shields.io/github/issues/enviodev/hyperindex.svg" alt="GitHub issues" /></a>
+    <a href="https://github.com/enviodev/hyperindex/graphs/contributors"><img src="https://img.shields.io/github/contributors/enviodev/hyperindex.svg" alt="GitHub contributors" /></a>
+    <a href="https://discord.gg/DhfFhzuJQh"><img src="https://img.shields.io/badge/Discord-Join%20Chat-7289da?logo=discord&logoColor=white" alt="Discord" /></a>
+    <a href="https://github.com/enviodev/hyperindex/stargazers"><img src="https://img.shields.io/github/stars/enviodev/hyperindex.svg" alt="GitHub stars" /></a>
+  </p>
+  <p>
+    <a href="https://docs.envio.dev">Documentation</a> ·
+    <a href="https://envio.dev">Hosted Service</a> ·
+    <a href="https://discord.gg/DhfFhzuJQh">Discord</a> ·
+    <a href="https://docs.envio.dev/blog/best-blockchain-indexers-2026">Benchmarks</a>
+  </p>
+</div>
 
-[![GitHub release](https://img.shields.io/github/release/enviodev/hyperindex.svg)](https://github.com/enviodev/hyperindex/releases) [![GitHub issues](https://img.shields.io/github/issues/enviodev/hyperindex.svg)](https://github.com/enviodev/hyperindex/issues) [![GitHub contributors](https://img.shields.io/github/contributors/enviodev/hyperindex.svg)](https://github.com/enviodev/hyperindex/graphs/contributors) [![Discord](https://img.shields.io/badge/Discord-Join%20Chat-7289da?logo=discord&logoColor=white)](https://discord.gg/DhfFhzuJQh) [![GitHub stars](https://img.shields.io/github/stars/enviodev/hyperindex.svg)](https://github.com/enviodev/hyperindex/stargazers)
+---
+## What is HyperIndex?
 
-HyperIndex is a fast, developer-friendly multichain indexer, optimized for both local development and reliable hosted deployment. It empowers developers to effortlessly build robust backends for blockchain applications.
+HyperIndex is Envio's full-featured blockchain indexing framework. It transforms onchain events into structured, queryable databases with GraphQL APIs, built for developers who care about performance and a clean local experience.
 
-> For comprehensive documentation, visit our [Documentation Portal](https://docs.envio.dev).
-> For hosted services and other solutions, visit [envio.dev](https://envio.dev).
+Powered by [HyperSync](https://docs.envio.dev/docs/HyperSync/overview), Envio's proprietary data engine, HyperIndex delivers up to 2000x faster data access than traditional RPC endpoints. That's the difference between syncing in minutes instead of days.
 
-![Envio Sync Gif](./sync.gif)
+![Envio Sync](sync.gif)
+
+---
+
+## Why HyperIndex?
+
+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.
+
+Independent benchmarks run by Sentio confirm it:
+
+- **Uniswap V2 Factory** (May 2025): HyperIndex completed in 1 minute. 15x faster than the nearest competitor (Subsquid), 143x faster than The Graph, 158x faster than Ponder
+- **LBTC Token with RPC calls** (April 2025): HyperIndex completed in 3 minutes vs 3 hours 9 minutes for The Graph
+
+[View full benchmark results →](https://docs.envio.dev/docs/HyperIndex/benchmarks)
+
+---
+
+## What you can build?
+ 
+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.
+ 
+A few things already running in production:
+ 
+- [v4.xyz](https://v4.xyz): the hub for Uniswap V4 data and analytics, indexing across 10 chains in real-time
+- [Stable Volume](https://www.stablevolume.com/): real-time stablecoin transaction monitoring across 10+ chains
+- [Stable Radar](https://stable-radar.com): real-time USDC transaction dashboard across multiple chains
+- [Liqo](https://liqo.xyz): multichain liquidation tracking for DeFi lending protocols
+- [Safe Stats](https://safe-stats.vercel.app/): real-time analytics for Safe multisig activity across all chains
+- [Oracle Wars](https://oraclewars.xyz/): real-time oracle price comparison across multiple oracles
+- [Chain Density](https://chaindensity.xyz/): transaction and event density analysis for any address across 70+ chains
+- [LogTUI](https://www.npmjs.com/package/logtui): terminal UI for monitoring blockchain events in real-time
+ 
+[See the full showcase →](https://docs.envio.dev/showcase)
+
+---
 
 ## Key Features
 
-- **[Indexer auto-generation](https://docs.envio.dev/docs/HyperIndex/contract-import)** – Generate Indexers directly from smart contract addresses
-- **High performance** – Historical backfills at over 10,000+ events per second ([fastest in market](https://docs.envio.dev/blog/indexer-benchmarking-results))
-- **Local development** – Full-featured local environment with Docker
-- **[Multichain indexing](https://docs.envio.dev/docs/HyperIndex/multichain-indexing)** – Index any EVM-compatible blockchain and Fuel (simultaneously)
-- **Real-time indexing** – Instantly track blockchain events
-- **[Reorg support](https://docs.envio.dev/docs/HyperIndex/reorgs-support)** – Graceful handling of blockchain reorganizations
-- **GraphQL API** – Easy-to-query indexed data
-- **Flexible language support** – JavaScript, TypeScript, and ReScript
-- **Factory contract support** – Index data from 1M+ dynamically registered contracts seamlessly
-- **On-chain & off-chain data integration** – Easily combine multiple data sources
-- **[Self-hosted & managed options](https://docs.envio.dev/docs/HyperIndex/hosted-service)** – Run your own setup or use HyperIndex hosted services
-- **Detailed logging & error reporting** – Debug and optimize with clarity
-- **External API actions** – Trigger external services based on blockchain events
-- **[Wildcard topic indexing](https://docs.envio.dev/docs/HyperIndex/wildcard-indexing)** – Flexible indexing based on event topics
-- **Fallback RPC data sources** – Enhanced reliability with RPC connections
+**Performance**
+- Historical backfills at 10,000+ events per second
+- Up to 2000x faster than traditional RPC via HyperSync (enabled by default, no config required)
+- Sync times reduced from days to minutes
+- Fallback RPC support for reliability without touching your indexer code
+
+**Multichain indexing**
+- Index EVM, SVM, and Fuel blockchains from a single indexer
+- 70+ EVM chains with native HyperSync support, plus any EVM chain via RPC
+- Unordered multichain mode for maximum throughput across chains
+- Real-time indexing with reorg handling built in
+
+**Developer experience**
+- Auto-generate an indexer directly from a smart contract address or ABI, no manual setup required
+- Write handlers in TypeScript, JavaScript, or ReScript
+- Full local development environment with Docker
+- GraphQL API generated automatically from your schema
+- Wildcard topic indexing: index by event signatures across any contract, not just specified addresses
+- Factory contract support for 1M+ dynamically registered contracts
+- Onchain and off-chain data integration
+- External API actions triggered by blockchain events
+- Detailed logging and error reporting
+
+**Deployment**
+- Managed [hosted service](https://docs.envio.dev/docs/HyperIndex/hosted-service) with static endpoints, built-in alerts, and production-ready infrastructure
+- Self-hosted via Docker
+- No vendor lock-in. Switch between HyperSync and RPC at any time
+
+**Agentic development**
+- HyperIndex is the default indexing framework for AI-assisted and agentic workflows via Envio's hosted service CLI (`envio-cloud`) and Claude skills
+- 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)
+
+---
+
+## Getting started
+
+**Requirements**: Node.js, Docker (only needed for local development)
+
+```bash
+npx envio init
+```
+
+This scaffolds your entire indexer project, config, schema, and handler functions, in seconds. You can generate from a contract address, choose from templates, or start from an existing example.
+
+From there, three files define your indexer:
+
+- `config.yaml` — networks, contracts, events, and indexing behaviour
+- `schema.graphql` — the shape of your indexed data
+- `src/EventHandlers.*` — your handler logic in TypeScript, JavaScript, or ReScript
+
+[Full getting started guide →](https://docs.envio.dev/docs/HyperIndex/getting-started)
 
-## Getting Started
+---
 
-Check out our [Getting Started Guide](https://docs.envio.dev/docs/HyperIndex/getting-started) to start querying your smart contract data with just a few clicks!
+## HyperSync
 
-## Performance
+HyperSync is the data engine that makes HyperIndex fast. It's active by default for all supported networks, no configuration needed.
 
-HyperIndex delivers industry-leading indexing speeds, with capability to process thousands of events per second while maintaining data integrity across multiple chains.
+Instead of making individual RPC calls per block, HyperSync retrieves multiple data points per round trip with advanced filtering. The result: sync speeds up to 2000x faster than standard RPC, dramatically lower infrastructure costs, and no rate limit headaches on supported networks.
 
-## Contribution & Support
+HyperSync can also be used directly for custom data pipelines in Python, Rust, Node.js, and Go, independent of HyperIndex.
+
+[HyperSync docs →](https://docs.envio.dev/docs/HyperSync/overview)
+
+---
+
+## Supported networks
+
+HyperIndex supports any EVM-compatible L1, L2, or L3, plus Fuel and Solana (experimental). 70+ chains have native HyperSync support for maximum speed. For any EVM chain not on the HyperSync list, RPC-based indexing works out of the box.
+
+[Full network list →](https://docs.envio.dev/docs/HyperIndex/supported-networks)
+
+---
+
+## Migrating from The Graph, Ponder, or Subsquid
+
+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.
+
+Teams migrating from The Graph can access 2 months of free hosting and full migration support.
+
+[Migration guide →](https://docs.envio.dev/docs/HyperIndex/migration-guide)
+
+---
+
+## Documentation
+
+Full documentation lives at [docs.envio.dev](https://docs.envio.dev).
+
+Key sections:
+- [Getting Started](https://docs.envio.dev/docs/HyperIndex/getting-started)
+- [Contract Import / Auto-generation](https://docs.envio.dev/docs/HyperIndex/contract-import)
+- [Multichain Indexing](https://docs.envio.dev/docs/HyperIndex/multichain-indexing)
+- [Wildcard Indexing](https://docs.envio.dev/docs/HyperIndex/wildcard-indexing)
+- [Reorg Support](https://docs.envio.dev/docs/HyperIndex/reorgs-support)
+- [Hosted Service](https://docs.envio.dev/docs/HyperIndex/hosted-service)
+- [HyperSync as Data Source](https://docs.envio.dev/docs/HyperIndex/hypersync)
+- [Migration Guide](https://docs.envio.dev/docs/HyperIndex/migration-guide)
+
+---
+
+## Community and support
 
 - Follow us on [X](https://twitter.com/envio_indexer)
-- Join our [Discord community](https://discord.gg/DhfFhzuJQh)
-- Report issues on [GitHub](https://github.com/enviodev/hyperindex/issues/new/choose)
-- Check our [Common Issues](https://docs.envio.dev/docs/common-issues) page for troubleshooting
+- Join the [Discord](https://discord.gg/DhfFhzuJQh), fastest way to get help
+- Open an issue on [GitHub](https://github.com/enviodev/hyperindex/issues/new/choose)
+- Browse [common issues](https://docs.envio.dev/docs/common-issues) for quick troubleshooting
+
+If HyperIndex is useful to you, a ⭐ on this repo goes a long way.
+
+---
+
+<div align="center">
+
+Built by [Envio](https://envio.dev) · [Docs](https://docs.envio.dev)
 
-If you find HyperIndex useful, please consider giving us a ⭐ on this repo!
+</div>

package/bin.mjs

@@ -0,0 +1,49 @@
+#!/usr/bin/env node
+//@ts-check
+
+import { spawnSync } from "child_process";
+import { createRequire } from "module";
+
+const require = createRequire(import.meta.url);
+
+/**
+ * Returns the executable path for envio located inside node_modules.
+ * The naming convention is envio-${os}-${arch}
+ * @see https://nodejs.org/api/os.html#osarch
+ * @see https://nodejs.org/api/os.html#osplatform
+ * @example "x/xx/node_modules/envio-darwin-arm64"
+ */
+function getExePath() {
+  const pkg = `envio-${process.platform}-${process.arch}`;
+  const bin = "bin/envio";
+
+  try {
+    return require.resolve(`${pkg}/${bin}`);
+  } catch {}
+
+  throw new Error(
+    `Couldn't find envio binary package "${pkg}".\n` +
+      `Checked: require.resolve("${pkg}/${bin}")\n` +
+      `If you're using pnpm, yarn, or npm with --omit=optional, ensure optional ` +
+      `dependencies are installed:\n` +
+      `  npm install ${pkg}\n`
+  );
+}
+
+/**
+ * Runs `envio` with args using nodejs spawn
+ */
+function runEnvio() {
+  const args = process.argv.slice(2);
+  const exePath = getExePath();
+
+  const processResult = spawnSync(exePath, args, { stdio: "inherit" });
+
+  if (processResult.error) {
+    console.error(`Failed to run envio binary at ${exePath}: ${processResult.error.message}`);
+    process.exit(1);
+  }
+  process.exit(processResult.status ?? 1);
+}
+
+runEnvio();

package/evm.schema.json

@@ -15,17 +15,6 @@
       "description": "Name of the project",
       "type": "string"
     },
-    "ecosystem": {
-      "description": "Ecosystem of the project.",
-      "anyOf": [
-        {
-          "$ref": "#/$defs/EcosystemTag"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
     "schema": {
       "description": "Custom path to schema.graphql file",
       "type": [
@@ -40,6 +29,33 @@
         "null"
       ]
     },
+    "handlers": {
+      "description": "Optional relative path to handlers directory for auto-loading. Defaults to 'src/handlers' if not specified.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "full_batch_size": {
+      "description": "Target number of events to be processed per batch. Set it to smaller number if you have many Effect API calls which are slow to resolve and can't be batched. (Default: 5000)",
+      "type": [
+        "integer",
+        "null"
+      ],
+      "format": "uint64",
+      "minimum": 0
+    },
+    "ecosystem": {
+      "description": "Ecosystem of the project.",
+      "anyOf": [
+        {
+          "$ref": "#/$defs/EcosystemTag"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
     "contracts": {
       "description": "Global contract definitions that must contain all definitions except addresses. You can share a single handler/abi/event definitions for contracts across multiple chains.",
       "type": [
@@ -54,31 +70,9 @@
       "description": "Configuration of the blockchain chains that the project is deployed on.",
       "type": "array",
       "items": {
-        "$ref": "#/$defs/Network"
+        "$ref": "#/$defs/Chain"
       }
     },
-    "multichain": {
-      "description": "Multichain mode: 'ordered' processes events across chains in order, 'unordered' processes chain events in order, but non-deterministically relatively to other chains (default: unordered)",
-      "anyOf": [
-        {
-          "$ref": "#/$defs/Multichain"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "event_decoder": {
-      "description": "The event decoder to use for the indexer (default: hypersync-client)",
-      "anyOf": [
-        {
-          "$ref": "#/$defs/EventDecoder"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
     "rollback_on_reorg": {
       "description": "A flag to indicate if the indexer should rollback to the last known valid block on a reorg. This currently incurs a performance hit on historical sync and is recommended to turn this off while developing (default: true)",
       "type": [
@@ -121,13 +115,6 @@
           "type": "null"
         }
       ]
-    },
-    "handlers": {
-      "description": "Optional relative path to handlers directory for auto-loading. Defaults to 'src/handlers' if not specified.",
-      "type": [
-        "string",
-        "null"
-      ]
     }
   },
   "additionalProperties": false,
@@ -259,7 +246,6 @@
         "root",
         "status",
         "yParity",
-        "chainId",
         "accessList",
         "maxFeePerBlobGas",
         "blobVersionedHashes",
@@ -301,31 +287,20 @@
         "mixHash"
       ]
     },
-    "Network": {
+    "Chain": {
       "type": "object",
       "properties": {
         "id": {
-          "description": "The public blockchain network ID.",
+          "description": "The public blockchain chain ID.",
           "type": "integer",
           "format": "uint64",
           "minimum": 0
         },
-        "rpc_config": {
-          "description": "RPC configuration for utilizing as the network's data-source. Typically optional for chains with HyperSync support, which is highly recommended. HyperSync dramatically enhances performance, providing up to a 1000x speed boost over traditional RPC.",
-          "anyOf": [
-            {
-              "$ref": "#/$defs/RpcConfig"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
         "rpc": {
-          "description": "RPC configuration for your indexer. If not specified otherwise, for networks supported by HyperSync, RPC serves as a fallback for added reliability. For others, it acts as the primary data-source. HyperSync offers significant performance improvements, up to a 1000x faster than traditional RPC.",
+          "description": "RPC configuration for your indexer. If not specified otherwise, for chains supported by HyperSync, RPC serves as a fallback for added reliability. For others, it acts as the primary data-source. HyperSync offers significant performance improvements, up to a 1000x faster than traditional RPC.",
           "anyOf": [
             {
-              "$ref": "#/$defs/NetworkRpc"
+              "$ref": "#/$defs/RpcSelection"
             },
             {
               "type": "null"
@@ -343,89 +318,17 @@
             }
           ]
         },
-        "confirmed_block_threshold": {
+        "max_reorg_depth": {
           "description": "The number of blocks from the head that the indexer should account for in case of reorgs.",
           "type": [
             "integer",
             "null"
           ],
-          "format": "int32"
-        },
-        "start_block": {
-          "description": "The block at which the indexer should start ingesting data",
-          "type": "integer",
-          "format": "uint64",
-          "minimum": 0
-        },
-        "end_block": {
-          "description": "The block at which the indexer should terminate.",
-          "type": [
-            "integer",
-            "null"
-          ],
-          "format": "uint64",
-          "minimum": 0
-        },
-        "contracts": {
-          "description": "All the contracts that should be indexed on the given network",
-          "type": "array",
-          "items": {
-            "$ref": "#/$defs/NetworkContract_for_ContractConfig"
-          }
-        }
-      },
-      "additionalProperties": false,
-      "required": [
-        "id",
-        "start_block",
-        "contracts"
-      ]
-    },
-    "RpcConfig": {
-      "type": "object",
-      "properties": {
-        "url": {
-          "description": "URL of the RPC endpoint. Can be a single URL or an array of URLs. If multiple URLs are provided, the first one will be used as the primary RPC endpoint and the rest will be used as fallbacks.",
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "array",
-              "items": {
-                "type": "string"
-              }
-            }
-          ]
-        },
-        "initial_block_interval": {
-          "description": "The starting interval in range of blocks per query",
-          "type": [
-            "integer",
-            "null"
-          ],
-          "format": "uint32",
-          "minimum": 0
-        },
-        "backoff_multiplicative": {
-          "description": "After an RPC error, how much to scale back the number of blocks requested at once",
-          "type": [
-            "number",
-            "null"
-          ],
-          "format": "double"
-        },
-        "acceleration_additive": {
-          "description": "Without RPC errors or timeouts, how much to increase the number of blocks requested by for the next batch",
-          "type": [
-            "integer",
-            "null"
-          ],
           "format": "uint32",
           "minimum": 0
         },
-        "interval_ceiling": {
-          "description": "Do not further increase the block interval past this limit",
+        "block_lag": {
+          "description": "The number of blocks behind the chain head that the indexer should lag. Useful for avoiding reorg issues by indexing slightly behind the tip.",
           "type": [
             "integer",
             "null"
@@ -433,40 +336,39 @@
           "format": "uint32",
           "minimum": 0
         },
-        "backoff_millis": {
-          "description": "After an error, how long to wait before retrying",
-          "type": [
-            "integer",
-            "null"
-          ],
-          "format": "uint32",
+        "start_block": {
+          "description": "The block at which the indexer should start ingesting data",
+          "type": "integer",
+          "format": "uint64",
           "minimum": 0
         },
-        "fallback_stall_timeout": {
-          "description": "If a fallback RPC is provided, the amount of time in ms to wait before kicking off the next provider",
+        "end_block": {
+          "description": "The block at which the indexer should terminate.",
           "type": [
             "integer",
             "null"
           ],
-          "format": "uint32",
+          "format": "uint64",
           "minimum": 0
         },
-        "query_timeout_millis": {
-          "description": "How long to wait before cancelling an RPC request",
+        "contracts": {
+          "description": "All the contracts that should be indexed on the given chain",
           "type": [
-            "integer",
+            "array",
             "null"
           ],
-          "format": "uint32",
-          "minimum": 0
+          "items": {
+            "$ref": "#/$defs/ChainContract_for_ContractConfig"
+          }
         }
       },
       "additionalProperties": false,
       "required": [
-        "url"
+        "id",
+        "start_block"
       ]
     },
-    "NetworkRpc": {
+    "RpcSelection": {
       "anyOf": [
         {
           "type": "string"
@@ -490,8 +392,22 @@
           "type": "string"
         },
         "for": {
-          "description": "Determines if this RPC is for historical sync, real-time chain indexing, or as a fallback.",
-          "$ref": "#/$defs/For"
+          "description": "Determines if this RPC is for historical sync, real-time chain indexing, or as a fallback. If not specified, defaults to \"fallback\" when HyperSync is available for the chain, or \"sync\" otherwise.",
+          "anyOf": [
+            {
+              "$ref": "#/$defs/For"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "ws": {
+          "description": "Optional WebSocket endpoint URL (wss:// or ws://) for real-time block header notifications via eth_subscribe(\"newHeads\"). Provides lower latency than HTTP polling for detecting new blocks.",
+          "type": [
+            "string",
+            "null"
+          ]
         },
         "initial_block_interval": {
           "description": "The starting interval in range of blocks per query",
@@ -554,12 +470,20 @@
           ],
           "format": "uint32",
           "minimum": 0
+        },
+        "polling_interval": {
+          "description": "How frequently (in milliseconds) to check for new blocks in realtime. Default is 1000ms. Note: Setting this higher than block time does not reduce RPC usage as every block is still fetched to check for reorgs.",
+          "type": [
+            "integer",
+            "null"
+          ],
+          "format": "uint32",
+          "minimum": 0
         }
       },
       "additionalProperties": false,
       "required": [
-        "url",
-        "for"
+        "url"
       ]
     },
     "For": {
@@ -594,7 +518,7 @@
         "url"
       ]
     },
-    "NetworkContract_for_ContractConfig": {
+    "ChainContract_for_ContractConfig": {
       "type": "object",
       "properties": {
         "name": {
@@ -606,7 +530,7 @@
           "$ref": "#/$defs/Addresses"
         },
         "start_block": {
-          "description": "The block at which the indexer should start ingesting data for this specific contract. If not specified, uses the network start_block. Can be greater than the network start_block for more specific indexing.",
+          "description": "The block at which the indexer should start ingesting data for this specific contract. If not specified, uses the chain start_block. Can be greater than the chain start_block for more specific indexing.",
           "type": [
             "integer",
             "null"
@@ -672,20 +596,6 @@
         }
       ]
     },
-    "Multichain": {
-      "type": "string",
-      "enum": [
-        "ordered",
-        "unordered"
-      ]
-    },
-    "EventDecoder": {
-      "type": "string",
-      "enum": [
-        "viem",
-        "hypersync-client"
-      ]
-    },
     "AddressFormat": {
       "type": "string",
       "enum": [