Every vote in a Dusk validation or ratification step gets signed individually then compressed into exactly one signature covering the whole committee's decision.
BLS makes that compression possible specifically. Per the white paper individual signatures from committee members aggregate into a single combined signature not stored side by side genuinely merged into one cryptographic object representing the group's vote.
A bites then tracks who's actually included in that aggregate a compact yes/no map showing which specific committee members' votes went into the combined signature without needing every individual signature stored separately alongside it.
What doesn't change: the aggregate signature still proves each included member genuinely voted cryptographically the same guarantee individual signatures would provide separately.
My own read: BLS aggregation is doing real work here turning what could be dozens of separate signature verifications into one without weakening what gets proven.
@Dusk_Foundation $DUSK #dusk $RE $ETH #BTC #ETH
BLS makes that compression possible specifically. Per the white paper individual signatures from committee members aggregate into a single combined signature not stored side by side genuinely merged into one cryptographic object representing the group's vote.
A bites then tracks who's actually included in that aggregate a compact yes/no map showing which specific committee members' votes went into the combined signature without needing every individual signature stored separately alongside it.
What doesn't change: the aggregate signature still proves each included member genuinely voted cryptographically the same guarantee individual signatures would provide separately.
My own read: BLS aggregation is doing real work here turning what could be dozens of separate signature verifications into one without weakening what gets proven.
@Dusk_Foundation $DUSK #dusk $RE $ETH #BTC #ETH