Author: Weiji Guo 2023-05-01 12:46:30
Published on: 2023-05-01T12:46:30+00:00
In this email exchange, Weiji and ZmnSCPxj discuss the issue of verification keys potentially exceeding the MAX_SCRIPT_ELEMENT_SIZE (520 bytes) and the need to consider system limitations. ZmnSCPxj highlights that `scriptPubKey` is consensus-critical and any new P2P messages regarding verification keys would also have to be consensus-critical as all nodes need to learn the new verification keys. Thus, there is a need to adjust weight units for propagation of verification keys, similar to how `scriptPubKey`s and amounts are included in block data and weighted accordingly. ZmnSCPxj suggests that if verification keys are permanent, they should be weighted heavier than `scriptPubKey`s and amounts as UTXOs can theoretically be deleted later by spending them while any data that must be permanently stored in a database must correspondingly be weighted higher. Additionally, if ZKP witnesses translate to higher resource consumption compared to ECC signatures, the weighting of ZKP witnesses should also be higher. Weiji agrees with ZmnSCPxj's insights and mentions that they will carry out some benchmarking to recommend a reasonable weight when they start to develop a GitHub PR. They also note that as they can potentially aggregate many proofs or recursively verify even more, the average cost might still be manageable.
Updated on: 2023-06-16T18:03:40.255735+00:00