Piers Powlesland e44cfeeaa2 core/txpool: Improve error responses ... I noticed that these two responses can make their way back to the transaction submitter when submitting unsupported tx types. Adding the extra context makes it easier for the submitter to understand what went wrong. Particularly in the case of the invalid sender response, which is returned when an unsupported transaction type is encountered.		2024-11-01 20:02:32 +00:00
..
blobpool	core/txpool/blobpool: fix error message (#30247)	2024-08-13 19:49:31 +08:00
legacypool	core/txpool/legacypool: use maps.Keys and maps.Copy (#30091)	2024-07-16 13:42:30 +02:00
errors.go	core/txpool: elevate the 'already reserved' error into a constant (#29095)	2024-02-27 13:27:50 +02:00
subpool.go	core/txpool, eth, miner: retrieve plain and blob txs separately (#29026)	2024-02-20 11:37:23 +02:00
txpool.go	core/txpool: Improve error responses	2024-11-01 20:02:32 +00:00
validation.go	core/txpool: Improve error responses	2024-11-01 20:02:32 +00:00