hash_tree_root was turning up when running beacon_node, turns out to be
repeated hash_tree_root invocations - this pr brings them back down to
normal.
this PR caches the root of a block in the SignedBeaconBlock object -
this has the potential downside that even invalid blocks will be hashed
(as part of deserialization) - later, one could imagine delaying this
until checks have passed
there's also some cleanup of the `cat=` logs which were applied randomly
and haphazardly, and to a large degree are duplicated by other
information in the log statements - in particular, topics fulfill the
same role
* Move BeaconNode type to its own file (fewer imports)
* disentangle sync protocol/request manager
* fix some old nimisms
* de-fear some logs
* simplify eth1 data production
* add stack tracing to release builds
* drop release compile flag for testnet
* Fixed getBeaconBlocks() and getRecentBeaconBlocks() to use BlockPool, not db.
* Got the sync_protocol to compiling state; Removed all obsolete RPC calls
* Proto changes to facilitate backward sync
* Update to latest spec types in sync proto
* Use blockpool for more straightforward block headers collection
* Added BlockPool.getRef
* Update beacon_chain/sync_protocol.nim
Co-Authored-By: Jacek Sieka <arnetheduck@gmail.com>
cheatfate
Jacek Sieka
Zahary Karadjov
Dustin Brody
Yuriy Glukhov
Yuriy Glukhov