Skip to content

Bradbury deploy fails: RPC proxies to unreachable internal cluster hostname (sequencer-leader.testnet-genlayer.svc.cluster.local) #425

Open

Description

@anaraydinli55

Summary

genlayer deploy fails on Testnet Bradbury with an internal Kubernetes
cluster hostname leaking through the public RPC gateway — the request
never reaches gas estimation or consensus, it fails at the HTTP layer.

Environment

  • genlayer CLI version: 10.9.7
  • Network: testnet-bradbury (chain ID 4221)
  • RPC (from genlayer network info): https://rpc-bradbury.genlayer.com
  • Contract size: ~13.3 KB (well under the known 20KB/16,777,216-gas ceiling)
  • OS: WSL2 (Ubuntu) on Windows 11

Steps to reproduce

  1. genlayer network set testnet-bradbury
  2. genlayer deploy --contract ModerationGuard.py

Observed error

GenLayer RPC error (eth_sendRawTransaction): error sending request for url
(http://sequencer-leader.testnet-genlayer.svc.cluster.local:3050/)

_InternalRpcError: An internal error was received.
Details: error sending request for url
(http://sequencer-leader.testnet-genlayer.svc.cluster.local:3050/)
code: -32603

Why this looks like a backend bug, not a client/config issue

sequencer-leader.testnet-genlayer.svc.cluster.local is an internal
Kubernetes service DNS name — it should never be reachable or referenced
outside the cluster. The public RPC gateway (rpc-bradbury.genlayer.com)
appears to be proxying to this internal address and failing, rather than
reaching a routable sequencer endpoint. genlayer network info reports a
correct, public RPC URL, so this isn't a local misconfiguration.

Impact

Cannot deploy any Intelligent Contract to Bradbury at all right now —
blocks a GenLayer Builder contribution resubmission that specifically
requires a working Bradbury deployment.

Activity

  1. ygd58 commented on Nov 6, 2026

    @ygd58

    I cannot reproduce the internal-hostname error today. Retest on 2026-11-06, from a server in Europe, plain JSON-RPC over HTTPS to the same endpoint as in this report (https://rpc-bradbury.genlayer.com), with a signed zero-value transfer (chainId 4221) from a freshly created account with zero balance:

    gasPrice Response
    1 -32000, max fee per gas less than block base fee: address 0x757B…6C17, maxFeePerGas: 1 baseFee: 10000000
    100000000 -32000, insufficient funds for gas * price + value: address 0xC046…80f3 have 0 want 2100000000000

    The second one matters for this report: the transaction got past the fee check and reached the balance check, so it is handled by something that has the account state, and I did not see error sending request for url (http://sequencer-leader…). eth_chainId, eth_blockNumber and net_version on the same endpoint answer normally.

    Limits of this check: these are plain transfers from an unfunded account, not a GenLayer deploy (addTransaction on the consensus contract) and not the CLI, so it does not prove that genlayer deploy works now. The networks page also now describes a Bradbury Phase 2, so the setup behind this URL may have changed since 2026-10-01.

    @anaraydinli55 if you retry genlayer deploy and it still fails, the exact error and the output of genlayer --version would let the maintainers tell whether it is still this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions