Difference between revisions of "Proxyd"
Jump to navigation
Jump to search
| Line 21: | Line 21: | ||
| − | * Applies [[rate limiting]] 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]]) | + | * Applies [[rate limiting]] (<code>[[SenderRateLimitConfig]]</code>) 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]]) |
== Logs == | == Logs == | ||
Latest revision as of 14:07, 20 September 2024
proxyd /etc/proxyd/proxyd.toml ws_method_whitelist
- Changelog: https://github.com/ethereum-optimism/infra/blob/main/proxyd/CHANGELOG.md
- Config: https://github.com/ethereum-optimism/infra/blob/main/proxyd/config.go
Features:
- Whitelists RPC methods (ws_method_whitelist)
- Routes RPC methods to groups of backend services
- 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)
Contents
Logs[edit]
ERROR
error forwarding request to backendError forwarding RPC batcherror serving requestserror proxying websocketerror writing clientConn message
WARN
backend request failed, trying againbackend banned - not healthybackend banned - unexpected block tagsproxied requests' XFF header will not contain the proxyd ip addresspeer count responded with 200 and 0 peersfailed requesterror updating backendbackend broke consensus
INFO
Activities[edit]
Related[edit]
See also[edit]
Advertising:
