Will
would be preferable if the release task ran on the PR merge, as a way to wait for approval
when started with args like e.g. ``` --hash ... \ --grpc-connect "drand:4444" \ --insecure \ ``` the insecure + grpc-connect seems to cause relay-gossip to not complain when the hash...
We can see individual partials but it would be to track which members have sent partials that contributed in recent rounds and create a warning log if a specific member...
releases provide binary versions of the main drand binary, but not of drand-relay
provide a readme in the `client/` folder explaining the different clients and composition options
during a DKG transition, a node failed to make the transition. the only relevant error log observed was ``` rpc error: code = Internal desc = grpc: error while marshaling:...
If the leader initiating a reshare indicates which of the current group members should and should not make it into the target group, all new members who are not part...
If a group member runs `drand share` to a coordinator before the coordinator has done so, the command will fail, as there is no dkg board setup on the coordinator...
``` all=drand_control.go:263 level=info dkg_setup=already_in_progress restart=dkg panic: runtime error: invalid memory address or nil pointer dereference panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1...