The DKG implementation in #708 does not specify restart safety. A likely implementation based on the chainsync client will not backfill DKG message events (but will backfill DKG successes since they are persisted in the contract state). Therefore, a keyper that starts only once a DKG is already in progress or restarts during a DKG process might miss some messages. This may result in them disagreeing on the resulting eon key and/or success of the DKG. To avoid this, keypers should backfill DKG events.
The DKG implementation in #708 does not specify restart safety. A likely implementation based on the chainsync client will not backfill DKG message events (but will backfill DKG successes since they are persisted in the contract state). Therefore, a keyper that starts only once a DKG is already in progress or restarts during a DKG process might miss some messages. This may result in them disagreeing on the resulting eon key and/or success of the DKG. To avoid this, keypers should backfill DKG events.