the root cause is that when `inMemoryExecution` lambda gets created in
the `eth/backend.go`, it captures the reference of
`backend.notifications`, and so the execution of side-forks actually
adds notifications to there, and it all gets sent out to tx pool (and
RPC daemon) at the end of the stage loop (regardless of whether there
was forkchoice update or not)
so we can create a separate notification, but then somehow flush it to
the "main" nofitications when the in-memory exec state is flushed
Co-authored-by: Alexey Sharp <alexeysharp@Alexeys-iMac.local>
Co-authored-by: Alex Sharp <alexsharp@Alexs-MacBook-Pro.local>
* Test GnosisGenesisStateRoot
* Delete obsolete allocations
* SysCallContract shouldn't increase nonce of SystemAddress
* Max gas limit in SysCallContract
* Restore error swallowing for Bor
* separated the encoding
* picking random peer node
* sending ping request
* updated enconding and reading
* requesting ping interval and more verbose vars
* disconnecting from unresponsive peers
* penalizing instead of disconnecting for irresponsiveness
* closing stream for streamCodec
* solved meged issues
* changed back
* separated const values
* requesting ping interval to 1 sec
* added closing of read and write stream && receiving responses!
* fixecd typo
* general sending request function
* added constants of resqresp topics
* fixed uncorrect name
* refactored sending requests
* added todo
* little detail
* moved to main
* no need to sleep
* sending request retries until timeout
* type
* lint
* Rebuilding the devnet tool for better quality
* Added README
* deleted former devnettest folder
* Correction changes
* Implementation node connection through enode for two nodes
* synced two nodes, moving to logging
* Fixed lint
* added subscription to gossip
* added all handlers with logs
* disconnecting from peers with goodbye message received
* added time out for stream
* wip
* Remove unused
* remove extra structs
* status handler
* minor clean up
* add structs for altair light client
* begin writing out altair light client sync protocol to figure out what other structs are needed
* remove sszgen
* cleanup pt 1
* cleanup pt 2
* remove go 1.19 function
* less ambigious variable name
* run go fmt
* rename snappy_ssz to ssz_snappy to better align with wire name
* move more structs over
* poof set deadline
Co-authored-by: Enrique Jose Avila Asapche <eavilaasapche@gmail.com>
Co-authored-by: a <a@a.a>
* added subscription to topics
* keeping track of topic subscription
* subscribing to beaconBlock
* listening to messages
* ops
* not processing our own messages
* ops
* Fail newPayload if execution is unsuccessful
* fix linter
* fix message
* no self-hosted
* try force ci
* back to unbuntu
* Remove unnecessary unwinds
* Fix canonicalising
* Quiet logs for in-memory exec
* Remove experimental overlay flag
* Fix sync test
* Fix test
* Fix lint
* Print hash in the end of the cycle
* Not notify headers if list is empty
* Supress timings and tables logs when no change in progress
* Reduce logging
* fix
* better log for pos download
* Better newPayload and forkChoice messages
* Fix lint
* simplify
* No duplication of download messages
* Reverse log for extension
Co-authored-by: Alexey Sharp <alexeysharp@Alexeys-iMac.local>
Co-authored-by: Igor Mandrigin <i@mandrigin.ru>
