How Luke can help you get a test DAC set up

testdac.md

1. Fork and clone https://github.com/eosdac/eosdac-client-extension
2. Add lukestokes as a collaborator to the repo (luke.stokes@gmail.com)
3. Overwrite the logos here with your own: https://github.com/eosdac/eosdac-client-extension/tree/master/branding/images/logo (the main one you need is logo-main.svg)
4. Add a color file here: https://github.com/eosdac/eosdac-client-extension/tree/master/branding/colors/color_schemes and modify https://github.com/eosdac/eosdac-client-extension/blob/master/branding/colors/default.colors.styl to import it.
5. Fork and clone https://github.com/eosdac/eosdac-constitution
6. Add lukestokes as a collaborator.
7. Find and replace eosDAC with your DAC and/or replace the whole document with your own user agreement and terms of service.
8. Let Luke know when you're done with the above things and he'll start the process of creating a test DAC for your on the Jungle Testnetwork.
9. Let Luke know what values you want for the following (remember, this is all just for the Jungle Testnetwork so these things can all change at any time).
   1. Human readable DAC name
   2. 8-character code for your DAC (just using letters and the numbers 1 through 5)
   3. Token Symbol
   4. Number of tokens to create
   5. Number of tokens to issue
   6. Number of custodians to run your DAC (default for a test DAC is 5)
   7. How many votes should each member get (default for a test DAC is 3)
   8. The length of each voting period (default is 7 days)
   9. The amount of EOS to pay each custodian per pay period (eventually this will be payable in your native token)
   10. Voting thresholds for various actions (I'll pick defaults for high, med, and low. Example, with our 12 custodians, high permission is 10, medium is 9, and low is 7 as you can see here.
   11. Number of tokens a custodian candidate has to lock up in order to run as a custodian (eosDAC uses 35,000)
   12. Number of days the tokens remain locked even after a custodian is no longer an active custodian (we use 90 days)
   13. Percentage of tokens that need to vote before the DAC can launch (we used 15%)
   14. Percentage of tokens that need to be voting for the DAC to stay active (we used 10%)
10. With that information, Luke can go ahead and use the DAC Factory to set up a test DAC for you on the Jungle Testnet. If you don't already have it configured, install and get comfortable with Scatter: https://get-scatter.com/
11. Luke will temporarily run MongoDB, RabbitMQ, the member client front end, the member client API, the chain processor and the chain filler on his own server so you can play around with it.
12. Luke will create test custodians and transfer tokens to them to vote for themselves and unlock the DAC. He'll give you those private keys so you can import them into your Scatter and use them to vote as well.
13. At this point, you have a functioning DAC on the Jungle Testnet and you can create your own multsignature proposals and customize the front end further to your needs.