Open mechanicals opened 2 years ago
Hi, mechanicals: There are a question, which need to be clarified: In your application, do you want a signature, which can be verified with the plain message? However, in the stage of signature, does each participant get an encrypted message and unknow the plain message of this ciphertext? In my imaginary, the flow is:
Is it correct ? In this case, how does each participant know the coming encrypted message, which is correct ? Thanks a lot!
@cychuang0924 : Thank you for the quick response.
With our permissioned Blockchain Infrastructure, we can verify that the incoming encrypted message is correct. Let me know if this answers your questions or any other clarifications are needed.
@mechanicals Could you send an email in private to me (i.e. chihyun@am.is)? Developing this feature is possible, but we need to discuss more with you. Thanks a lot!
@cychuang0924 : thank you for the response. I will get in touch with over email.
Hi Shubham,
Sorry for late to reply! Could you introduce your company please ? Our
team is interested in your team.
We introduce our products briefly:
We also offers some other products: https://www.amis.com
If you have any questions, let me know please! Thanks a lot!
Sincerely,
Chih Yun
Shubham @.***> 於 2022年7月19日 週二 凌晨1:42寫道:
@cychuang0924 https://github.com/cychuang0924 : thank you for the response. I will get in touch with over email.
— Reply to this email directly, view it on GitHub https://github.com/getamis/alice/issues/182#issuecomment-1187910558, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK4AJBHP4WEWZEZTFKVXNADVUWJQBANCNFSM52J4KCPA . You are receiving this because you were mentioned.Message ID: @.***>
Is this a BUG REPORT or FEATURE REQUEST?: Feature Request
What happened: We have our own blockchain, and We are using Alice to generate MPC Shares needed for signatures for different blockchains (BTC, ETH). Currently we can smoothly generate Signatures on non-encrypted transaction data. But our Transaction data would be actually be in an encrypted form for Production release and therein lies our blocker.
What you expected to happen: We are trying to achieve the same result when generating Signatures for encrypted transaction data. Any support or direction along these lines would be really helpful.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?: