- Please Provide Explanation Thank You 1 (439.65 KiB) Viewed 48 times
Please provide explanation. Thank you.
-
answerhappygod
- Site Admin
- Posts: 899604
- Joined: Mon Aug 02, 2021 8:13 am
Please provide explanation. Thank you.
Please provide explanation. Thank you.
BLS Aggregate Signatures (1.5 marks). The BLS signature scheme supports aggregation. That is, given a set of messages m... m, public keys K... Kn, and signatures 01... O, there is an efficient O(n) function 0+ = AggregateSigs(01... on) such that VerifyAggregate Sig(Kı... Kn, m... mm, 0+) returns true if and only if for all 1 sis n, VerifySig(ki, mi, 0) returns true. The aggregated signature (like all BLS signatures) is just 256 bits. This can be useful in a cryptocurrency context. a. Suppose Bitcoin wanted to add this feature to compress blocks. Each miner will now take all of the signatures in each block and aggregate them, producing a single aggregate signature for the block which is broadcast. Provide an estimate of how much bandwidth this would save for a full client verifying Block #735273 in the Bitcoin blockchain. How much would the cost savings vary for different blocks if different Bitcoin features are used more or less often? b. Perform the same calculation for the cost savings possible from using aggregate signatures in Ethereum, using Block #14728204 as a case study. Again, how much would the savings vary as different features of Ethereum are used more or less often? C. How could this be used to improve the efficiency of the Bitcoin-NG proposal? You don't need to look at concrete numbers in this case (since this isn't implemented anywhere yet).
BLS Aggregate Signatures (1.5 marks). The BLS signature scheme supports aggregation. That is, given a set of messages m... m, public keys K... Kn, and signatures 01... O, there is an efficient O(n) function 0+ = AggregateSigs(01... on) such that VerifyAggregate Sig(Kı... Kn, m... mm, 0+) returns true if and only if for all 1 sis n, VerifySig(ki, mi, 0) returns true. The aggregated signature (like all BLS signatures) is just 256 bits. This can be useful in a cryptocurrency context. a. Suppose Bitcoin wanted to add this feature to compress blocks. Each miner will now take all of the signatures in each block and aggregate them, producing a single aggregate signature for the block which is broadcast. Provide an estimate of how much bandwidth this would save for a full client verifying Block #735273 in the Bitcoin blockchain. How much would the cost savings vary for different blocks if different Bitcoin features are used more or less often? b. Perform the same calculation for the cost savings possible from using aggregate signatures in Ethereum, using Block #14728204 as a case study. Again, how much would the savings vary as different features of Ethereum are used more or less often? C. How could this be used to improve the efficiency of the Bitcoin-NG proposal? You don't need to look at concrete numbers in this case (since this isn't implemented anywhere yet).
Join a community of subject matter experts. Register for FREE to view solutions, replies, and use search function. Request answer by replying!