jferrant

This might already be done by the WSTS logic timeout. Make sure this timeout is used and add testing for what happens in this case. Does a new coordinator get...

> @kantai is the assumption that the signer will rely on disk (ie SQLite) for state? That is kind of what I was thinking, but you can choose what you...

So right now we just store block info in a Hashmap and it grows almost indefinitely (only being removed following a successful broadcast of the signature) This garbage collection needs...

Have not seen since activating signer v0. Closing.

> Something like this? [stacks-network/stacks-blockchain#3989](https://github.com/stacks-network/stacks-blockchain/pull/3989) > > Where is the sdk hosted eventually? Here or on stacks-blockchain? Yeah, pretty much exactly like that. I think we don't want stacks-blockchain to...

> I think it could potentially cause more harm (or at least worry) than good if we're being strict about this warning with non-localhost setups. IMO it's probably best practice...

A bit unrelated to this PR, but it would be nice if you updated the internal call to get_node_epoch in process_dkg to go away (this was done in a sep...

> I think this should be closed given the v0/v1 changes, yeah? If not, I think it'd be best to rebase on top of #4778 . @jferrant what do you...

Thanks for finding this Aaron. Is this at all related to the change I made that had to do with how to select the parent to build atop of in...

> @wileyj, sure! @jferrant, please feel free to let me know how I can help (or if I'm needed). I'll be looking at logging in general to see how it...