add dictator.sol

[orenyodfat]

No description provided.

[ben-kaufman]

why not register the owner as admin right away in the initialize and then unregister self?

[orenyodfat]

because the initialize function is called as the process of instance the scheme before the scheme is registered .

[ben-kaufman]

oh right, so nevermind

[jellegerbrandy]

The contract and tests seem fine, but I am not completely clear about the intended usage here.

So the idea here is that we have a daostack account called 0xdaosstack, and to execute any type of function we:

• deploy our daos with the dictator scheme registered, and with dictator.owner set to 0xdaostack
• call dictator.registerScheme(0xdaostack)
• and now we can do everything the controller allows us to do from the 0xdaostack account

Changing ownership would then be a 3-step process:

• call Dictator.setOwner(0xnewOnwer)
• call Dicator.registerScheme(0xnewOwner)
• unregister the 0xdaostack account (the old backdoor ccount) as a scheme

[dkent600]

@orenyodfat @jellegerbrandy Would be great if docs like this could be in the code:

#752 (review)

[orenyodfat]

• deploy our daos with the dictator scheme registered, and with dictator.owner set to 0xdaostack
• call dictator.registerScheme(0xdaostack)
• and now we can do everything the controller allows us to do from the 0xdaostack account

not exactly :

• The owner of dictator is 0xdaostack .
• 0xdaostack can register any arbitrary scheme or account with full permission to the dao by calling call dictator.registerScheme(0xanyarbitraryschemeoraccount)

0xanyarbitraryschemeoraccount can do what ever.

changing ownership of Dictator will be 1 step :

• dictator.transferOwnership(0xnewOwner)

Such a contract is needed to register 0xanyarbitraryschemeoraccount due to the fact that daoFactory can register contracts only.