Looking at Dusk's consensus lately, one small thing changed how I think about it: the hard part isn't getting provisioners to agree. It's carrying proof that they agreed without that proof becoming its own burden.
A committee can throw off a lot of individual signatures. More of them can mean stronger evidence, sure, but it also means more data the network has to push around and check. This is where BLS12-381 actually earns its place in Dusk's design it lets many valid signatures fold into one compact proof, so the network isn't stuck paying a bigger bill every time more provisioners show up to vote.
But it's not as clean as it sounds. Votes still have to be valid. Signers still have to be eligible. Someone still has to manage keys properly, verify signatures, and deal with the boring stuff serialization, CPU cycles, all of it. Dusk has apparently spent time caching BLS public-key conversions, which tells you where these systems actually get hard. Not the cryptography itself the plumbing around it.
So I don't think of this as Dusk making signatures smaller. I think of it as Dusk changing how agreement moves through the system at all. Whether that holds up as committees and activity grow is the part I'm still not sure about.
#dusk @Dusk $DUSK
A committee can throw off a lot of individual signatures. More of them can mean stronger evidence, sure, but it also means more data the network has to push around and check. This is where BLS12-381 actually earns its place in Dusk's design it lets many valid signatures fold into one compact proof, so the network isn't stuck paying a bigger bill every time more provisioners show up to vote.
But it's not as clean as it sounds. Votes still have to be valid. Signers still have to be eligible. Someone still has to manage keys properly, verify signatures, and deal with the boring stuff serialization, CPU cycles, all of it. Dusk has apparently spent time caching BLS public-key conversions, which tells you where these systems actually get hard. Not the cryptography itself the plumbing around it.
So I don't think of this as Dusk making signatures smaller. I think of it as Dusk changing how agreement moves through the system at all. Whether that holds up as committees and activity grow is the part I'm still not sure about.
#dusk @Dusk $DUSK