feat(network): add hl-node network + eRPC HyperEVM alias#666
Open
bussyjd wants to merge 3 commits into
Open
Conversation
Add hl-node as an obol-stack network (Chart/values/helmfile via bedag/raw): a Hyperliquid non-validating node StatefulSet (hostNetwork, nodeSelector), Service exposing the HyperEVM JSON-RPC on :3001/evm, and a metadata ConfigMap. Register the local node's HyperEVM RPC (chain 999) as an eRPC upstream alias `hyperevm` (+ `hyperevm-testnet`) via resolveLocalERPCRegistration, so in-cluster consumers reach HyperCore at http://erpc.erpc.svc.cluster.local/rpc/hyperevm instead of a hardcoded basket. Claude-Session: https://claude.ai/code/session_01YUTW7NfxjUoVtyKgR6nPQC
0.1.x brings the unified selection-policy engine, in-house failsafe with per-attempt observability, and dRPC REST-based network discovery. The legacy `selectionPolicy.evalFunction` blocks remain valid via the 0.1.x compat shim (synthesized to `selectionPolicy.eval`, emits a deprecation warning) — a follow-up can migrate them to the new `selectionPolicy.eval` form. Claude-Session: https://claude.ai/code/session_01YUTW7NfxjUoVtyKgR6nPQC
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds hl-node (Hyperliquid non-validating node) as a first-class obol-stack network and wires its HyperEVM JSON-RPC into eRPC.
internal/embed/networks/hl-node/— network templates (Chart/values/helmfile viabedag/raw): a node StatefulSet (hostNetwork,nodeSelectorto a chosen host), aServiceexposing the HyperEVM JSON-RPC on:3001/evm, and a metadata ConfigMap. Flags:--chain,--flags,--root-ip,--host,--image,--storage-size.internal/network/erpc.go—resolveLocalERPCRegistrationregisters the local node's HyperEVM RPC (chain999) as an eRPC upstream aliashyperevm(+hyperevm-testnet), so in-cluster consumers reach HyperCore athttp://erpc.erpc.svc.cluster.local/rpc/hyperevminstead of a hardcoded public-RPC basket.Why
This is the obol-stack-native path for running a Hyperliquid node and exposing its HyperEVM read surface (mark/oracle/OI precompiles) through the existing eRPC gateway — the same way local Ethereum nodes are auto-registered as eRPC upstreams. It lets downstream services (e.g. a Hyperliquid trading-intelligence API) consume HyperCore on-chain reads via eRPC rather than reinventing an RPC basket.
Test plan
go build ./...— green.go test ./internal/network/ -run ERPC— green (TestResolveLocalERPCRegistration,TestResolveLocalERPCRegistrationRejectsUnknownHLNetwork).obol network install hl-node --helplists the derived flags.hl-node:3001/evm) matches the eRPC alias endpoint and the metadata ConfigMap.https://claude.ai/code/session_01YUTW7NfxjUoVtyKgR6nPQC