jferrant

Very minor comments on my part :D Great to see this update!

- If DKG has timed out due to waiting on other signers, start a new DKG key round without those signers. (This should be done by WSTS but we need...

This will require changes on the signer's end to not abort signing blocks if their tenure is expired (i.e. a to be signed stacks block could arrive after the burn...

Thanks for your PR! This should be reopened against the `develop` branch though.

I have no problem with it :)

This is not technically done. We only have addressed the coordinator issue for signing and not DKG.

When a new coordinator is selected by a signer, they may need to reread stackerdb slots to catch up their view point to be the same as other signers (i.e....

> > Sure, that's a good point. I'd prefer then to also have the `SignerDB::in_memory()` constructor to make it explicit for users who don't know the ":memory:" [special file name](https://www.sqlite.org/inmemorydb.html)....

You need to update the construction of the signer file to include the database name. i.e. add `db_path = ":memory:"`. See build_signer_config_tomls

Whenever I try to run the integration tests I get complaints about too many open files. I thought maybe you would need to reduce the number of signers, but I...