2
I am developing a wallet API, but I don't want custodial control of the user's funds. For reasons I won't explain here, I don't want to use multisig.
But I want the advantages of a 2 of 2 multisig. I want the client to sign a transaction, and then send that signed transaction to the server. The server will then finish signing the transaction and push it to the network.
Is this theoretically possible? Does something like this exist yet in practice?
In summary, I want a way for the client and the server to sign a transaction together without either one having the private key.
If the transactions has more than one input and one (or more) of those is yours. But I doubt that's what you are looking for. For example: it doesn't protect the user against malware or key-theft/loss. And it also doesn't protect you against the user double-spending or sending the funds somewhere where you don't approve (if that was your goal). – Jannes – 2015-10-08T17:35:38.220