Quote from: TPTB_need_war on February 12, 2016, 12:21:51 PM

Quote from: YarkoL on February 12, 2016, 11:39:06 AM

Quote from: TPTB_need_war on February 12, 2016, 10:29:14 AM

Laymen let me attempt to explain this to you.

Putting Smart Contract data on a global block chain means that as those contracts interact, it is impossible to prove that the order that the contracts are run is commutative and that the contracts will halt.

I'm not sure where commutativity applies here. Contracts call public methods of
other contracts, so it is an ordered sequence.

You've admitted to me before that your knowledge of Computer Science is limited. And your reply here makes that obvious.

It would be more truthful to yourself and others if you phrased your lack of knowledge as a question than as a statement. I am more respectful when answering questions than when n00bs effectively are slandering the facts I have written when they write false statements as you have done.

Well... I don't think I was "slandering facts" or that either of the sentences
I wrote was false. The first one of them simply expresses my uncertainity of where
the commutativity problem comes from, and the execution of the calls does happen
in order.

But never mind. I'll promise that next time when I dare to open my mouth
in your presence it will be in a trembling, hushed voice with my garments rent
and covered with dust.

Quote from: monsterer on February 12, 2016, 11:43:25 AM

Right. That's not why Ethereum is indeterminate - within one single block things are fine. The problem is across multiple blocks - if execution is dependant on block order, orphans and re-orgs can cause big problems.

Thanks. I think I now see where the potential problem
is and so I have guidelines for further investigation.