ceremonyclient/node/consensus/ceremony
Cassandra Heart f0c71b2d40
some various fixes ahead of 1.4.7 (#119)
* experimental: switch mutex to RW to see if it alleviates backpressure on peer info

* relax mutex req

* reject unknown messages

* open the floodgates

* adjust message handler to use goroutine, i'll probably regret this

* switch that back, it was regret

* further discovery

* log more data

* forcibly block channel when unbounded

* else

* make it configurable so bootstrap peers are the only ones putting up with this.

* ok, non-starter, let's try a different route

* further tweaking

* let the peer info flow uninhibited

* final burn off on master

* final adjustments
2024-03-12 20:28:48 -05:00
..
broadcast_messaging.go some various fixes ahead of 1.4.7 (#119) 2024-03-12 20:28:48 -05:00
ceremony_data_clock_consensus_engine.go some various fixes ahead of 1.4.7 (#119) 2024-03-12 20:28:48 -05:00
consensus_frames.go some various fixes ahead of 1.4.7 (#119) 2024-03-12 20:28:48 -05:00
execution_registration.go v1.2.4 (#43) 2024-02-13 01:04:56 -06:00
peer_messaging.go v1.4.6 (#115) 2024-03-12 02:45:20 -05:00
prover_lookup.go 1.0.0 – Dawn 2023-09-24 21:43:35 -05:00