6 Commits (2814ee0547cb49dddf182bad802f19100608d5f8)

Author	SHA1	Message	Date
Marius van der Wijden	d10a2f6ab7	tests/fuzzers: update fuzzers to be based on go-native fuzzing (#28352) ... This change modifies the fuzzers to use the native golang fuzzing framework instead of go-fuzz	1 year ago
Péter Szilágyi	8afbcf4713	eth: enforce announcement metadatas and drop peers violating the protocol (#28261) ... * eth: enforce announcement metadatas and drop peers violating the protocol * eth/fetcher: relax eth/68 validation a bit for flakey clients * tests/fuzzers/txfetcher: pull in suggestion from Marius * eth/fetcher: add tests for peer dropping * eth/fetcher: linter linter linter linter linter	1 year ago
Felix Lange	2a6beb6a39	core/types: support for optional blob sidecar in BlobTx (#27841) ... This PR removes the newly added txpool.Transaction wrapper type, and instead adds a way of keeping the blob sidecar within types.Transaction. It's better this way because most code in go-ethereum does not care about blob transactions, and probably never will. This will start mattering especially on the client side of RPC, where all APIs are based on types.Transaction. Users need to be able to use the same signing flows they already have. However, since blobs are only allowed in some places but not others, we will now need to add checks to avoid creating invalid blocks. I'm still trying to figure out the best place to do some of these. The way I have it currently is as follows: - In block validation (import), txs are verified not to have a blob sidecar. - In miner, we strip off the sidecar when committing the transaction into the block. - In TxPool validation, txs must have a sidecar to be added into the blobpool. - Note there is a special case here: when transactions are re-added because of a chain reorg, we cannot use the transactions gathered from the old chain blocks as-is, because they will be missing their blobs. This was previously handled by storing the blobs into the 'blobpool limbo'. The code has now changed to store the full transaction in the limbo instead, but it might be confusing for code readers why we're not simply adding the types.Transaction we already have. Code changes summary: - txpool.Transaction removed and all uses replaced by types.Transaction again - blobpool now stores types.Transaction instead of defining its own blobTx format for storage - the blobpool limbo now stores types.Transaction instead of storing only the blobs - checks to validate the presence/absence of the blob sidecar added in certain critical places	1 year ago
Péter Szilágyi	d40a255e97	all: move main transaction pool into a subpool (#27463) ... * all: move main transaction pool into a subpool * go.mod: remove superfluous updates * core/txpool: review fixes, handle txs rejected by all subpools * core/txpool: typos	1 year ago
Martin Holst Swende	0703c91fba	tests/fuzzers: improve the fuzzers (#21829) ... * tests/fuzzers, common/bitutil: make fuzzers use correct returnvalues + remove output * tests/fuzzers/stacktrie: fix duplicate-key insertion in stacktrie (false positive) * tests/fuzzers/stacktrie: fix compilation error * tests/fuzzers: linter nits	4 years ago
Péter Szilágyi	9938d954c8	eth: rework tx fetcher to use O(1) ops + manage network requests	5 years ago