In case proposal is approved, it can execute any code. Most business proposals, for example, will call some kind of contract tailored along the template of SampleOffer.sol. The curators will take care that the bytecode of this contract does what it should - thats one of their duties.
But a proposal can contain other code. Especially, it can call any function of the DAO itself. If a proposals recipient is the DAO itself, the proposal will not be checked by the curators. People voting for a proposal should therefore not only rely on the plain text description of the proposal, but also verify that the code the proposal will execute will do what the plain text description promises.
Example
Proposal #17 of the DAO claims to rise the Proposal deposit to 11 ETH.
We will provide a step-by-step description how you can prove that the proposals code actually will set the Proposal Deposit to 11 ETH.
I've provided a step-by-step-instruction on https://daowiki.atlassian.net/wiki/display/DAO/How+to+verify+a+Proposals+bytecode how to verify this proposals bytecode.
First, we will determin the bytecode of the function call which is promised to be executed in case the proposal is executed.
Second, we prove that the proposal, which is engraved in the blockchain for eternity, itself contains exactly this bytecode.
Feedback is welcome!
The DAO