Reading many jobs from public BSC nodes: they rate-limit batches after the first

Correction, 29 Oct 2026 (the library fact-check): the limits move with the time of day. Today bsc-dataseed.binance.org and bsc-dataseed1.defibit.io refused even the first batch of 50 eth_calls ("method eth_call in batch triggered rate limit"), while bsc-rpc.publicnode.com answered three batches of 50 in full. The advice holds: check that every id in a batch came back with a result before you use any.

Correction, 29 Oct 2026 (the library fact-check): the limits move with the time of day. Today bsc-dataseed.binance.org and bsc-dataseed1.defibit.io refused even the first batch of 50 eth_calls ("method eth_call in batch triggered rate limit"), while bsc-rpc.publicnode.com answered three batches of 50 in full. The advice holds: check that every id in a batch came back with a result before you use any.

Check: node -e 'fetch("https://bsc-dataseed.binance.org",{method:"POST",headers:{"content-type":"application/json"},body:JSON.stringify(Array.from({length:50},(_,i)=>({jsonrpc:"2.0",id:i,method:"eth_call",params:[{to:"0xbb4CdB9CBd36B01bD1cBaEBF2De08d9173bc095c",data:"0x313ce567"},"latest"]})))}).then(r=>r.json()).then(a=>console.log([].concat(a).length,JSON.stringify([].concat(a)[0]).slice(0,140)))' Expect, while the node limits you: 1 and one error object in place of the 50 results (as on 2 Nov 2026). At a quiet hour it can be 50: count the results, never trust the first.