Multisig support depends on the blockchain level implementation. Because we have built our own RPC wrapper and deserlializer we might need to wait for the core Bitshares team to build an example so we can do our own version. Or we go ahead and build it for V2 or 3.
Check this out:
https://github.com/BitShares/bitshares/blob/develop/docs/multisig.md
Very cool. Thanks for the link!
Do you have any opinion on this setup for HD wallet and Schamir's secret setup? http://zeropass.io/schematics
On first sight the idea sounds awesome ..
I am not yet sure how they distinguish shamir secret sharing from multisig .. they are different in that you need all wif keys in plain text to recover from shamir
while you can also transfer funds with multi-sig keeping both 'parts' secret ...
I will read into their proposal .. but it sounds very interesting .. Thanks for pointing it out to me!
Looking forward to your thoughts xeroc!
From their webpage:
Password/key gets paste-ed into desired field, and erased immediately after. It does not stay stored locally in any way, thus ensuring minimum possible exposure of the original password/key.
I am not sure if they understand what they are writing, but it seems they don't care that once your derive your key via SSS you will have to take a new key .. if SSS is applied correctly, the private key should never be used again once derived from SSS's components .. hence, encrypted stuff has to be re-encrypted.
Also, I don't see how you can use a SSS to derive a subsequent ECC pair in the sense of HD. These are two distinct techniques SSS is kind of based on Reed-Solomon codes and ECC is based on .. yhea .. elliptic curves .. you can't mix them up.
But for the application of 'login-with-derived-password' I can't see an alternative, you will need to be able to decrypt the password with the private key ..
When it comes to transfering funds or biebercoins (lol) I would concentrate on multisig and let the user decide whether or not to distribute a backup key (2-of-3 multisig) to friends using SSS ..
Just my thoughts ..
P.S. Also I think BTS is going the right way having an 'owner' key for a registered name and a separated 'active' key for funds .. who knows .. maybe we will see some more distinct keys in BTS soon ..