This is the third and final post on a series on how to use the Ethereum Wallet to create your own autonomous organisations. On the first post we detailed how to create a token<\/a>, and on the second we shown how to generate a digital democracy controlled by these tokens<\/a>. Now we will do the full circle and create a token controlled<\/em> by the Organisation!<\/p>\n We are going to modify the token contract to allow it to be minted by your DAO. So save the address of your current DAO in a note pad (pay attention to the icon) and grab this source code<\/a> and you know the drill: contracts > deploy new contract > solidity source code > pick contract<\/strong><\/p>\n You can fill the parameters any way you want (yes, emojis are permitted on the string fields) but you’ll notice one new field that didn’t exist before: Central Minter. Here add the address of your newly created democracy contract.<\/p>\n \u00a0<\/p>\n Click Deploy and let’s wait for the transaction to be picked up. After it has at least two confirmations, go to your democracy contract and you’ll notice that now it owns a million of your new coins. Now if you go to the Contracts tab you’ll see that there is a new DAO dollar (admin page)<\/strong> contract on your collection.<\/p>\n Select the “mintToken” function to your right and then put any address you own as the “target”, and then the amount of new mints you want to create from thin air in their account. Press “execute<\/strong>” but don’t press send<\/strong>! You’ll notice that there is a warning saying that the transaction can’t be executed. This happens because only the Minter <\/strong>(which is currently set to the DAO address) can call that function and you are calling it with your main account. But the calling code is the same, which is why you can simply copy it.<\/p>\n Instead, copy the contract execution code from the “data” field<\/strong> and put it aside on a notepad. Also get the address of your new “Mint” contract and save it somewhere.<\/p>\n Now go back to the democracy contract and create a new proposal with these parameters:<\/p>\n \u00a0<\/p>\n \u00a0<\/p>\n In a few seconds you should be able to see that the details on the proposal. Unlike the other fields, transactionBytecode can be extremely lengthy and therefore expensive to store on the blockchain. So instead of archiving it, the person executing the call later will provide the bytecode.<\/p>\n But that of course creates a security hole: how can a proposal be voted without the actual code being there? And what prevents a user from executing a different code after the proposal has been voted on? That’s why we keep the hash of the bytecode. Scroll a bit on the “read from contract” function list and you’ll see a proposal checker function, where anyone can put all the function parameters and check if they match the one being voted on. This also guarantees that proposals don’t get executed unless the hash of the bytecode matches exactly the one on the provided code.<\/p>\n \u00a0<\/p>\n \u00a0<\/a><\/p>\n Now everyone can vote on the proposal and after the voting period has passed, anyone with the correct bytecode can ask the votes to be tallied up and the contract to be executed. If the proposal has enough support then the newly minted coins should appear on Alice’s account, as if it was a transfer from address Zero.<\/p>\n \u00a0<\/p>\n \u00a0<\/p>\n And now you have a central minter contract that exists solely on the blockchain, completelly fraud-proof as all their activities are logged transparently. The mint can also take coins from circulation by simply sending the coins it has to address Zero, or by freezing the funds on any account, but it’s mathematically impossible<\/strong> for the Mint to do any of those actions or generate more coins without the support of enough shareholders of the mint.<\/p>\n Possible uses of this DAO:<\/p>\n![\"Ethereum](\"https:\/\/blog.ethereum.org\/images\/posts\/2015\/12\/Screen-Shot-2015-12-01-at-7.09.11-PM.png\")
<\/a><\/p>\n![\"Ethereum](\"https:\/\/blog.ethereum.org\/images\/posts\/2015\/12\/Screen-Shot-2015-12-01-at-7.17.06-PM.png\")
<\/a><\/p>\n\n
![\"Ethereum](\"https:\/\/blog.ethereum.org\/images\/posts\/2015\/12\/Screen-Shot-2015-12-01-at-7.22.48-PM.png\")
<\/a><\/p>\n![\"It's](\"https:\/\/blog.ethereum.org\/images\/posts\/2015\/12\/Screen-Shot-2015-12-02-at-11.51.50-AM.png\")
<\/a>
\nIt’s an older code, but it checks out<\/a><\/p>\n![\"Why](\"https:\/\/blog.ethereum.org\/images\/posts\/2015\/12\/Screen-Shot-2015-12-02-at-12.02.43-PM.png\")
<\/a> Why a transfer from address\u00a0zero? Because doing the opposite, sending a coin to 0x00 is a way to effectively destroy it, but more importantly, because it says so on the contract code. You can change that as you\u00a0prefer.<\/p>\n\n