Quote from: bitacer on March 15, 2016, 09:13:28 PM
whats the max number of multisigs possible ?


    "maximum_authority_membership": 10,
    "max_authority_depth": 2,

So maybe 10*10 = 100. I may be wrong.

Anyway you can try it on testnet: http://testnet.bitshares.eu/

whats the max number of multisigs possible ?

I think this is a great idea.  If you need a US based individual to put stuff on a credit card let me know.

Quote from: roadscape on March 15, 2016, 03:05:26 PM
Also one or more people will need to be selected as account managers.. so they pay for the service with a credit card, and this multisig account will compensate them via BitUSD?

Very good point!

As for proposed transactions .. I think they are currently halted (although the code is finished) because the backend lacks a patch ..
https://github.com/cryptonomex/graphene/issues/442

Great idea..

Quote from: xeroc on March 15, 2016, 09:46:18 AM
So then, we need:

1) A large set of people that hold fractional permissions of the funds
2) A separated committee that manages manages funds and deals with the actual proposals
3) A campaign to let shareholders know about this

Would we want to go via flat hierarchy .. in the sense of a 10 out of 20 multisig
or would we want to use the full power of hierarchical multisig accounts .. such as
worker account/funds are controlled 50%/50% by committee-account (multisig of 11 or more) and a community-account (11 or more)?

How long until GUI wallet supports proposed transactions? That's the main obstacle in making multisig easy to use, correct?

If it will be a while, I say use a simpler flat hierarchy and maybe 6-of-11 multisig (possibly overkill).

Also one or more people will need to be selected as account managers.. so they pay for the service with a credit card, and this multisig account will compensate them via BitUSD?

So then, we need:

1) A large set of people that hold fractional permissions of the funds
2) A separated committee that manages manages funds and deals with the actual proposals
3) A campaign to let shareholders know about this

Would we want to go via flat hierarchy .. in the sense of a 10 out of 20 multisig
or would we want to use the full power of hierarchical multisig accounts .. such as
worker account/funds are controlled 50%/50% by committee-account (multisig of 11 or more) and a community-account (11 or more)?

Quote from: xeroc on March 14, 2016, 05:22:53 PM
There is plenty of reasons to have a community/shareholder managed fund available already!

Multisig is magic, let's use it! +5%

 +5%

Absolutely  +5%

 +5%

How about we setup a multi signature account that gets a worker and pays for services like

- basecamp3: https://bitsharestalk.org/index.php/topic,21910.msg285536/topicseen.html#new
- Slack Pro for a bigger message archive
- Docker Pro to be able to compile witness nodes in docker containers (maybe even windows executables)
- coveralls.io: for testing coverage of test cases
- jenkins build server

what else could be needed? There is plenty of reasons to have a community/shareholder managed fund available already!