chriseth

I remember that we discussed this, but thinking about it for a minute, I cannot see a reason why this should not be allowed. @ekpyron what do you think?

I would say it's the same as in the case of non-view/view/pure: If a contract strengthens the requirement in the inheritance graph, all derived contracts must also implement the stronger...

You currently need the nightly version of solidity. We will release a new version 0.3.3 which will included that feature shortly.

This now uses the evaluator to determine if some branches cannot be reached at all (and then it does not encode them). This is a trace of the encoded opcodes...

Got this working now without the hack: ``` =========== SETUP =================== mstore(40, 80) mstore(0, 4e487b7100000000000000000000000000000000000000000000000000000000) mstore(4, 41) datacopy(80, dataoffset(dataref("oTest_15")), datasize(dataref("oTest_15"))) _54 := create(0, 80, sub(add(add(80, datasize(dataref("oTest_15"))), 0), 80)) - _54...

The daily limit feature is not really useful once we have currency abstraction. I agree that with a daily limit of 0, every call (including send) should require multisig.

I would prefer this change to be more modular. Would it be a possibility to create a "confirmation" module that handles the actual confirmations - which can be done using...

I would prefer a full rewrite of the wallet contract. I have seen a pretty simple rewrite, but I'm not sure if it is published yet.

Can you combine than with the other math library? And perhaps we could use this sqrt function: ``` contract c { uint bla; /// @why3 ensures { to_int result *...

Why did you indent the whole file?