To extract the random coins used in BLS witness encryption.

[smallfrog]

I wish to use BLS witness encryption as a commitment tool in cut-and-choose-style proofs, similar to the approach in the paper: Madathil V, Thyagarajan S A K, Vasilopoulos D, et al. Cryptographic oracle-based conditional payments[J]. Cryptology ePrint Archive, 2022.

However, the current python bindings library does not allow the extraction and use of random coins (corresponding to r1 and r2 inside the function Encrypt in the file https://github.com/kofi-dalvik/bls-witness-encryption/blob/main/src/witenc.cpp) outside the encryption algorithm (corresponding to the function Scheme.encrypt in the file https://github.com/kofi-dalvik/bls-witness-encryption/blob/main/bindings/python/witencpy.cpp). Could you please inform me if and when this issue will be addressed? Thank you.

[lokingdav]

Unfortunately, the current implementation does not support the cut-and-choose style out of the box.

Due to my current workload, I won't be able to implement this feature for you. If all you need is r1 and r2 then it should be straightforward. You might need to develop the cut-and-choose style yourself and submit a pull request. The Python bindings can always be updated accordingly.

[smallfrog]

Unfortunately, the current implementation does not support the cut-and-choose style out of the box.

Due to my current workload, I won't be able to implement this feature for you. If all you need is r1 and r2 then it should be straightforward. You might need to develop the cut-and-choose style yourself and submit a pull request. The Python bindings can always be updated accordingly.

Yeah, I just need this code library to provide an additional function with r1 and r2 as additional formal parameters rather than local variable compared to existing function, i.e., Scheme.encrypt in the file https://github.com/kofi-dalvik/bls-witness-encryption/blob/main/bindings/python/witencpy.cpp. But I am unfamiliar with C++ Code and how to bind it with Python code. I think I can wait for a while if you solve this issue in the near future.