Multi sig support?

[evanrolfe]

Now that monero has multi sig support merged to master in the monero codebase, I'm thinking it would be very beneficial to have a browser based js wallet which can handle multi sig wallet creation and management, since currently the process for creating multi sig wallets its fairly complicated, if we could do this in the browser then perhaps this could be done in a more user friendly way?

Would this codebase be the right place to code browser based multi sig support? Do you have any tips on how this could be implemented?

Any help would be much appreciated, thanks.

[paulshapiro]

Just realized I forgot to reply to this for a long time. We'll definitely support multisig and have some interesting plans around it but we won't be able to prioritize implementing it ourselves in the very near term. If you would like to collaborate with us, please keep in touch.

[paulshapiro]

@evanrolfe hey there, just want to let you know that the new cpp branch is hooking into the same code which sends multisig txs. We would just need to modify the bridge code slightly to prepare the data in the right format and I think we'd be able to fully support such multisig txs.

[ctrlshp]

@paulshapiro So with the release of the MMS comes the realization that there is a need for a whole protocol for negotiating the Monero multisig wallet. Personally, I'm not interested in relying on BitMessage. The use case that makes sense for me is a 2/3 multisig protocol with the 3 usual parties : market (moderator/arbiter), merchant and customer, where the market provides, over plain HTTP, the async messaging service between everybody, and where both the merchant and the customer can use a normal wallet, such as MyMonero, that would support this protocol. The exchange could be bootstrapped with QR codes and then everything else would occur automatically, non-interactively, between the merchant and customer's wallets via the market-hosted (and wallet-supported) API.

For now, I will call this the MyMonero Multisig Protocol (MMP) and I would like CTRL SHP to be one of the first, if not the first, to support the MMP.

Should you be interested, I can post my ideas here and work, slowly for now, towards first a full-blown protocol specification, and then an implementation both on the market server-side (TypeScript Serverless, you know me) and on the wallet side. I can contribute JavaScript code to MyMonero, but I don't do UI, and I suspect the UI to be a big part of the multisig solution. So am I making sense at all ? Does it makes sense for you and your MyMonero business ?

[paulshapiro]

Hi @ctrlshp yes actually we have some plans to add support to the lightwallet server to make them into a message layer. The designs we have been discussing with MRL involve server-blinding such that the server cannot know the contents of the message (encrypted by spend key) - only that it's intended for a user with a view key that's on their server. We've been looking at systems like saltpack (compatible with ECC keys). Since the official lightwallet server is written in C++, I would suggest using C++, not TypeScript. I do not think Node.JS is a viable solution in this situation. However, nothing wrong with multiple implementations, and the specification we establish can be shared across all of them. There's huge potential for a system like this. Imagine sending MyMonero Funds Requests out into the ether (broadcast) to be picked up by any server who has the user with that public address. The applications go further than that.

[paulshapiro]

So, I'd be very happy to establish a collaboration with you on that front. I've been thinking about this for the past year or two.

[paulshapiro]

Maybe contact me at paul@mymonero.com and we can set up a time to chat.

[ctrlshp]

Email sent.

[meow464]

Hello, is multi sig (2/3) already working? Are the necessary javascript bindings there?

[xplsek03]

Maybe contact me at paul@mymonero.com and we can set up a time to chat.

Well, how did it go? Curious.