Andy Polyakov

> Can you run this locally to confirm I'm not crazy? I can run it, but I can't confirm you're not crazy:-):-):-) Not qualified, you know...:-):-):-) But on serious note!...

Just in case for reference, I used node v14.16. No, it doesn't mean that I know if there were some relevant improvements, or if prior versions were "bad." It was...

Have you seen [blsttc](https://github.com/maidsafe/blsttc)? Just in case, I haven't looked into it myself, so it's not like I'm saying that it will actually solve your problem.

It seems that verify_multiple_aggregate_signatures could accept something less "rigid" than blst_scalar. At least blst_scalar is quite wasteful, because rand_bits would be significantly smaller than blst_scalar bit width, right? It might...

> on big-endian "randomness" would be "applied" in reverse byte order, which is arguably as random. Just in case, this is naturally assuming that if rand_bits is not divisible by...

Incidentally we've got a somewhat similar question even in Python context. Yes, favouring the "Builder Pattern" is the reason for returning the same object, yet one can make a case...

> "take one for the team." In essence it boils down to following simple rule. Whenever there is assignment, first method ought to be `dup()`. For example, equivalent of `a...

Yes, the subroutines in question facilitate [multiple aggregated signature verifiction](https://ethresear.ch/t/fast-verification-of-multiple-bls-signatures/5407). Its usage pattern is not finalized, because straightforward/naive one is not optimal. In other words it will change. As for...

I've opened #758 and marked this one draft, as it would require a re-adjustment once #758 is merged.

Back from draft, now as wasm-only thing. Just in case for reference. As it stands now, the linking procedure (on non-emscripten wasm targets) fails with "archive has no index" in...