Our gRPC client (responsible for serving query methods like eth_getLogs quickly) was incorrectly dropping null wildcards in the middle of eth_getLogs topic filters, which silently misaligned subsequent positions. Our HTTP client behaved correctly, but most eth_getLogs requests are served via the gRPC client.
A request was affected if its topics array contained a null followed by another non-null filter — for example topics: [selector, null, recipient], which is the standard shape viem.getLogs({ event, args: { to: [...] } }) produces. Requests without a mid-array null were unaffected.
If you ran an indexer that filtered logs by a non-first indexed topic against Base between 2026-05-19 and 2026-05-27, you may have missed events. Re-run the affected query range against Edge RPC again.
