Can MPC shares generated using Alice be used for Signing on homomorphically encrypted Transactions.

[mechanicals]

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?:

[cychuang0924]

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:

1. A person generates an encrypted message and sends it to signers.
2. The signers get the encrypted message, work together to generate a signature, and send it to the person.
3. The person gets the signature, which can be verified successfully respect to the original message.

Is it correct ?
In this case, how does each participant know the coming encrypted message, which is correct ?
Thanks a lot!

[mechanicals]

@cychuang0924 : Thank you for the quick response.

1. Yes, we want a signature which can be verified with the plain message.
2. Yes, each participant will get the encrypted message.

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.

[cychuang0924]

@mechanicals Could you send an email in private to me (i.e. [email protected])? Developing this feature is possible, but we need to discuss more with you. Thanks a lot!

[mechanicals]

@cychuang0924 : thank you for the response. I will get in touch with over email.

[cychuang0924]

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: 1. Qubic wallet (i.e. A TSS Wallet): "A non-custodial, multi-chain and multi-platform (ios, android and web) wallet, featured by user friendly social logins. The security is projected by AMIS's proprietary Hierarchical Threshold Signature Scheme algorithm. Qubic Wallet not only supports general crypto wallet features, such as crypto/NFT wallets and DeFi capabilbities, but also enable users to buy NFTs directly with credit cards on OpenSea, Lootex, and Qubic Creator merchants." ref. https://www.qubic.app 2. Qubic Creator Service : "Backed by the core technologies of AMIS, Qubic Creator is a one stop NFT shop with creator services and an NFT marketplace. Qubic Creator strives to provide NFT as a Service, and bridges the traditional and the decentralized world, so that enterprises and users will not be held back by the complexity of blockchain technology and can enter the decentralized world without difficulty. The platform had 60+ clients, across various industries, who have signed up contracts or are in pipeline, by Jan 2022. ref. https://creator.qubic.market 3. Qubic Pass ： A decentralized passport service that allows Qubic and other crypto wallets to log in. It provides online and offline verification methods to prove NFT holding. In addition, merchants or enterprises can integrate Qubic Pass ERC20 points system with their loyalty points for web3 applications. 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 <#182 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK4AJBHP4WEWZEZTFKVXNADVUWJQBANCNFSM52J4KCPA> . You are receiving this because you were mentioned.Message ID: ***@***.***>