8b01284b0e
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 |
||
|---|---|---|
| .. | ||
| README.md | ||
| fork_choice.nim | ||
| fork_choice_types.nim | ||
| proto_array.nim | ||
README.md
Fork choice implementations
References: