The idea is along these lines: the problem with batch verification is that it entangles the execution of verifications of different items, requiring a second set of “transposed” logic. But by using futures, we can decouple the verification semantics from the execution:https://twitter.com/hdevalence/status/1207421089892069376 …
-
-
Prikaži ovu nit
-
Also, there’s a cute optimization to automatically coalesce terms in the batch verification check when multiple signatures in the batch are from the same public key, giving up to a 2x speedup in the limiting case:pic.twitter.com/C6Jff4wnrR
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.