Weikeng Chen

following up on the previous response from @yelhousni So, as long as we work on a prime-order subgroup, the issue is gone?

And it seems that, even if two backends support u64 natively, whether or not they have "carry" would make things different.

Let me know if we want to move ahead with it.

ADD: one can also bypass this limitation by preprocessing the data, e.g., perform a bit reversal to cancel the other bit reversal implemented in arkworks-rs.

I think we will leave it for the release after v0.4.0

The goal is to refresh the EIP-1962 implementation and reduce its maintenance cost.

It would be great if this can be approved soon.

Actually, this is a good idea.

Do you already have a script that generates the parameters? or we can work together on this. I just feel that the BW6 method has a higher entry bar, but...

Let me check how to replace the HashMap in stream_pippenger. (there should be other ways to get no-std hash map). For the other two, easy.