Nicolas Gailly

A way to improve would be to have a unified way, in core/ package, in the daemon logic itself to automatically detects if a protocol is already supposed to run...

I think we can go with (1)++ where we force nodes to sync before joining a network (via the command to reshare also syncs before) and (4) . (4) can...

I'm a bit afraid to even more give powers/assumptions to the coordinator though - now he can basically run a resharing whenever he wants. Before we only trusted him to...

Let's imagine we want to do this, how would this work: Idea 1: * up to t nodes manually set their node to resharing and contact the leader * Once...

For me it's a matter of best engineering practices. I'd like to decouple as much as possible the logic of each beacon between themselves and the "coordination" logic of the...

I dont quite remember the full context of this issue, should have written more. Looking at the current codebase now what can happen is: * Leader start a setup session...

I think it is one way to solve the problem but it can also open to more complexity - like how do we prevent nodes to "always be regenerating" -...

> Forced to use a certain field. I can think of some situations where you would like to have constraints on one field acting as the "scalar field", for operations...

Bumping this issue because a relevant work has been out recently CurveTree ([paper](https://eprint.iacr.org/2022/756.pdf)). This accumulator would fit **perfectly** inside Halo2 proof system assuming we can: 1. inject user defined polynomials...

I am surely lacking some context so please bear with me :pray: * Isn't it a problem if you allow to have different implementations that can be 10x slower with...