You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
Activity
ygd58 commentedon Nov 6, 2026
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 (chainId4221) from a freshly created account with zero balance:gasPrice1-32000,max fee per gas less than block base fee: address 0x757B…6C17, maxFeePerGas: 1 baseFee: 10000000100000000-32000,insufficient funds for gas * price + value: address 0xC046…80f3 have 0 want 2100000000000The 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_blockNumberandnet_versionon the same endpoint answer normally.Limits of this check: these are plain transfers from an unfunded account, not a GenLayer deploy (
addTransactionon the consensus contract) and not the CLI, so it does not prove thatgenlayer deployworks 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 deployand it still fails, the exact error and the output ofgenlayer --versionwould let the maintainers tell whether it is still this problem.