BLS Signature Aggregate and Rogue-Key Attacks
BLS Signature
There are , , , four parties.
: secret key , message , public key , signature
: secret key , message , public key , signature
: secret key , message , public key , signature
: secret key , message , public key , signature
one by one:
and so on.
, hash to curve, result is a point.
Use aggregated signature, we can compute less expensive pairings. ( vs )
Rogue-Key Attacks
if , for example, in consensus, different nodes sign the same block.
There are 5 parties: 4 validators and 1 leader.
Normal Process
- The leader broadcasts block() to all the validators
- The validators send back signatures .
- The leader broadcasts the aggregated signature
- The validators validate with , as .
As a malicious leader
The malicious leader want to change the block, such as he want to double-spend.
- The leader new a secret key , with public key
- The leader sign the new block():
- The leader public new public key
- The leader public new signature
- Other validators aggregate: , , , So validators think the new block( is legal.
Reference