Please add one of your many awesome Question marks with tool tip. No need for a Manual with armory. These things explain almost everything and you learn a lot about the Bitcoin protocol and more.
Yeah, that's one of those things that should be under super-expert feature. There limited uses for using regular multisig over P2SH, but they do exist (having transparent public keys in the blockchain can assist with automated tools that are tracking multisig addresses they are signers for). I'll add a (?) thingy
"Cannot be signed by you" However, both watching-only wallets are marked as "mine". Therefore the comment should rather be that the signature cannot be given from this instance of Armory, and then explain the conditions (keys are not here or not your wallet). Whatever, doesn't seem 100% correct. Maybe a "light" green would be good in case you can even cover it with the architecture.
Yeah, I don't use the "is mine" or "belongs to someone else" distinction here. If we can come up with something clean to say, I'll change it. Otherwise, I'm sure the user will figure it out
What about Simulfunding of normal single key addresses? What about if I want to set up a 10 party 0.1 BTC simulfund to give to Armory?
I struggled with simulfunding of regular addresses -- there's no reason the same code can't be used for it, but it didn't fit cleanly into the lockbox dashboard. So I added a "Multisig" menu to the main window, and you can do arbitrary simulfunding from there. I want to unify the interface somehow, but not quite sure yet how to do it. Either way, feel free to try out all the same features from that menu instead. (by the way, "arbitrary" means arbitrary recipients. But not arbitrary inputs: I still haven't found a good way to build into the UI the ability to simulfund with Lockboxes... shouldn't be too hard though)
