Joey Yandle
Joey Yandle
Hi @nerdrew @tafia, I'm thinking about taking this branch, removing the arrayvec code, and using the alloc collections when in no_std mode. This removes the need for the length annotations...
In the short to medium term, I will be occupied by responding to the `wsts` audit, including writing the security proofs, which is tracked by this issue: https://github.com/stacks-network/wsts/issues/8 If this...
Regarding the TODO comment in the code, I don't think iserve should monitor the new process; returning the pid to the caller is sufficient. The caller is free to link/1...
> 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...
The threshold is a function of the number of reward slots/key_ids, not the number of signers. It's curious that a single signer would only have 1 reward slot. What is...
We should definitely fix both the `stacks-signer` and `clarity` code to round up in those calculations.
> * Does a DKG signing round correspond to a 2 week stacking cycle where we generate a new list of public keys to act as signers? > > A...
Nakamoto will not sign with taproot, but sBTC will. It seems more forward looking to fix signer DB to support this.
Did you end up doing an audit of `p256` @SilentCicero ?
> `p256` was audited recently. The README.md should probably be updated to reflect it: Yeah I found that once I started looking. Very clean audit report!