feat: jsonrpc architecture for non-EVM (HAProxy) upstreams

[snowkide]

Summary

Stacked on #20 (forwardedClientId + WS metrics) — does not modify #20.

Adds architecture: jsonrpc / type: jsonrpc so non-EVM chains can sit on erpc with upstreams pointed at HAProxy (or direct node Services), getting:

• HTTP + per-message WS metrics (erpc_network_request_received_total) via existing pipeline + feat: path /secret auth + forwardedClientId + WS event metrics #20
• Failsafe / alias / hostname routing
• No eth_chainId probe, EVM state poller, or EVM method hooks

Example (Solana via HAProxy)

networks:
  - architecture: jsonrpc
    alias: solana-mainnet
    hostname: solana-mainnet.cll.linkpool.com
    jsonRpc:
      id: solana-mainnet   # -> network id jsonrpc:solana-mainnet
upstreams:
  - id: solana-mainnet-proxy
    type: jsonrpc
    endpoint: http://solana-mainnet-proxy.solana-mainnet-proxy.svc.cluster.local:80
    jsonRpc:
      networkId: solana-mainnet
  - id: solana-mainnet-proxy-ws
    type: jsonrpc
    endpoint: ws://solana-mainnet-proxy.solana-mainnet-proxy.svc.cluster.local:81
    jsonRpc:
      networkId: solana-mainnet

Same pattern for starknet/tron/aptos/ton/sui/btc/polkadot (direct ports as needed).

Out of scope

• SVM-specific Solana integrity (upstream has full architecture: svm; this is intentionally dumb passthrough)
• JSON-RPC method cache for non-EVM
• Changing feat: path /secret auth + forwardedClientId + WS event metrics #20

Test plan

• go test ./common/ -run TestJsonRpcNetworkId
• go build ./common ./util ./erpc ./upstream
• Config load with a jsonrpc network + HAProxy upstream
• HTTP request bumps erpc_network_request_received_total{transport=\"http\"}
• WS messages bump transport=\"ws\" (via feat: path /secret auth + forwardedClientId + WS event metrics #20 path)
• Merge after feat: path /secret auth + forwardedClientId + WS event metrics #20

Made with Cursor

[github-actions]

	File	Lines	Key changes	Risk
🟠	registry.go	+7/-1	—	⚠ = fmt.Errorf
🟠	networks.go	+11/-0	—	⚠ ErrJsonRpcExceptionInternal
🟢	architecture_jsonrpc.go	+12/-0	JsonRpcNetworkConfig, JsonRpcNetworkConfig
🔵	ids.go	+8/-0	JsonRpcNetworkId
🔵	defaults.go	+21/-4	—
	1 test files	+63

_{xray — see through AI slop with deterministic architecture PR diff reviews}

[snowkide]

Supersedes the separate edge path (now closed):

• docker-images#412
• charts#342
• infra#13481

After #20 + this + image: add architecture: jsonrpc networks/upstreams on chainlink-erpc in services-argocd-deployments (HAProxy/direct endpoints). Envoy *.cll.linkpool.com already routes via erpc HTTPRoutes.

[snowkide]

Prod finding: running jsonrpc-passthrough-2 fails every non-EVM upstream with:

unsupported upstream type: jsonrpc for upstream: …

Root cause: clients/registry.go only accepted UpstreamTypeEvm. Fix pushed on this branch (8dfeb1a0) — HTTP/WS clients now created for type: jsonrpc. Publishing jsonrpc-passthrough-3 for a services image bump.

[snowkide]

Superseded by combined PR #24 (rebased onto feat/websocket-support).

[snowkide]

Closing in favor of #24.