Bosul Mun 56d201b0fe eth/fetcher: add metadata validation in tx announcement (#33378) ... This PR fixes the bug reported in #33365. The impact of the bug is not catastrophic. After a transaction is ultimately fetched, validation and propagation will be performed based on the fetched body, and any response with a mismatched type is treated as a protocol violation. An attacker could only waste the limited portion of victim’s bandwidth at most. However, the reasons for submitting this PR are as follows 1. Fetching a transaction announced with an arbitrary type is a weird behavior. 2. It aligns with efforts such as EIP-8077 and #33119 to make the fetcher smarter and reduce bandwidth waste. Regarding the `FilterType` function, it could potentially be implemented by modifying the Filter function's parameter itself, but I wasn’t sure whether changing that function is acceptable, so I left it as is.		2025-12-11 12:11:52 +08:00
..
corpus	eth: rework tx fetcher to use O(1) ops + manage network requests	2020-02-13 15:27:15 +02:00
txfetcher_fuzzer.go	eth/fetcher: add metadata validation in tx announcement (#33378)	2025-12-11 12:11:52 +08:00
txfetcher_test.go	all: update license comments and AUTHORS (#31133)	2025-02-05 23:01:17 +01:00