Why Polygon eth_getLogs costs more CU
Polygon produces more aggressive block payloads than Ethereum mainnet in many epochs. To keep log-heavy workloads
from starving other tenants, etox applies a higher CU weight for eth_getLogs on Polygon than on
Ethereum. The numeric table is published on our docs page and enforced consistently at
the gateway — no surprise invoices after the fact.
Bor method coverage
Validators and analytics pipelines sometimes rely on bor_getAuthor,
bor_getCurrentValidators, and related calls. Our Redis weight map reserves entries for these
methods so metered billing matches actual CPU and I/O pressure on the Erigon instance.
Authentication and dashboards
As with every etox chain, authenticated calls require an API key from dashboard.etox.io, embedded in the URL path. Until Polygon routing is enabled, monitor status via operator announcements; the public site will stay updated as subnets go live.
Cross-links
Compare metering philosophy with Ethereum and Base, and read how rpcfree.com differs from keyed tiers on etox.io.