Will

``` ERRROR: rpc error: code = Unknown desc = drand: err during DKG: drand: error from dkg: process-justifications: only 0/2 valid deals - dkg abort panic: runtime error: invalid memory...

mac release binary is unsigned

2

should either not generate, or should have goreleaser perform mac codesigning

investigate non c-go builds

1

github.com/DataDog/zstd is in the dependency tree and includes cgo code. would be great if the go binary didn't need this (likely related to standard web server stuff, but not entirely...

cancel current follow on subsequent command

1

after a failed follow, a subsequent attempt will fail with "sync already in progress"

when a node is joining a chain via `share --connect` it would be useful to have it implicitly run a `follow` up to current head before doing so, so that...

Groups can end up in a mode where they don't catch-up

2

It looks like there can be recovery situations where the group has ended up behind the expected round, but hasn't realized it should be in catch-up mode

Pubsub relay / client can end up with persistent context issues after fail-over

2

reproduction: * temporary disconnect of drand node that a pubsub relay is pointed against * "they experience a context cancellation in the client watch" - The requests are hanging probably...

Drand nodes may end up generating beacons delayed from start of round

10

observed by @alanshaw * setup DKG between 3 local nodes without specifying a `beacon-delay` * observed beacon generation was consistently 5-6 seconds off from when the `NextRound` would expect it...

``` ./drand-client --watch --relay /dnsaddr/pl-us.testnet.drand.sh --insecure panic: No chain supplied for joining ``` We shouldn't panic, and should print an error that either a full chain info.json or an http/grpc...

current re-export of peer metrics is a bit unwieldy, as peer addresses need to be manually programmed in. In addition, we should have a single endpoint that fetches metrics from...