proxyd
Jump to navigation
Jump to search
proxyd /etc/proxyd/proxyd.toml: ws_method_whitelist, response_timeout_seconds, out_of_service_seconds, max_latency_threshold
- Changelog: https://github.com/ethereum-optimism/infra/blob/main/proxyd/CHANGELOG.md
- Config: https://github.com/ethereum-optimism/infra/blob/main/proxyd/config.go
- Releases: https://github.com/ethereum-optimism/infra/tags
Features:
- Whitelists RPC methods (
ws_method_whitelist) - Routes RPC methods to groups of backend services
- Round-robin Load balance requests across backend services
- Automatically retries failed backend requests
- Cache immutable responses from backends
- Provides metrics to measure request latency, error rates
Consensus related:
- Track backend consensus (latest, safe, finalized blocks), peer count and sync state
- Re-write requests and responses to enforce consensus
- Applies rate limiting (
SenderRateLimitConfig) on a per-sender basis to avoid being bombarded with signed transactions causing a DOS (Denial of Service) of the sequencer (Optimism Censorship Bug Disclosure)
Proxyd backend healthy
Errors examples
Failed sync attempt to a7eaa64c50083f1xxxxxfd96eaabffd1c8f: one or more objects failed to apply, reason: error when patching "/dev/shm/396xxxxx68": Deployment.apps "your-service" is invalid: spec.template.spec.containers[0].env[1].valueFrom: Invalid value: "": may not be specified when `value` is not empty (retried 1 times).
Proxyd logs
Activities
Related
- Consensus
- Emerald Dshackle load balancer
- dRPC
- Total number of primary candidates
- RedisConfig
- Fallback
See also
proxyd, proxyd logs, config, routing_strategy, consensus_aware (deprecated), SenderRateLimitConfig, Consensus awareness,ws_method_whitelist, backend healthy, Proxyd logs- OP Stack:
op-, op-geth, op-node, op-proposer, op-batcher, op-contracts, op-challenger, op-heartbeat, op-ufm, op-service, Snap Sync, op-conductor, op-dispute-mon
Advertising:
