Because 'find' is insufficient. As I have stated in my prior posts (which again you seem to ignore or lack reading comprehension), there must also be a way to enforce that all participants agree on that global ordering. Since I (and user 'enet') have explained that any global (i.e. total) ordering will be arbitrary, then the only way to force all participants to agree is the longest chain rule.

You can try to dream up other methods such as voting, but when you work through it you will realize there is no unambiguous enforcement mechanism (there is always some game theory around the assumptions made). And this lack of enforcement mechanism on the rule that participants must use, is the reason a DAG is inconsistent and I conjecture will diverge (unless there are centralized servers implementing consistent rules and thus it is no longer decentralized).

Please don't make me explain this again. Every since we started discussing Iota, you have continued to repeat this same myopia over and over and over and over and over and over again. It is very redundant and it is cluttering the thread with noise. Whoever can't understand this very simple concept by now, isn't likely to ever understand it.


Incorrect. You completely failed to comprehend the explanation I made in my prior post. Try reading it again and again and again until you can comprehend.

The payers must send a PoW with their transaction. They will selfishly choose to sign the block which will include their transactions. To double-spend (other than Finney attack which is an error of payees) requires more PoW hashrate than the hashrate of the selfishly-honest payers. And the attacker won't be able to sustain this mining equipment with any profit or even recover significant income, because mining is unprofitable.


You have shown no such weakness in my current design. Yeah I found flaws in my prior designs. So what. I made it very clear in the past that those designs were still under study and that I was not announcing the details until I was satisfied with my internal review.

This thread is not for FUD based on uninformed guessing. If you have a concrete flaw, then discuss. Spilling FUD about my design before a white paper is even released will degrade this thread into a pissing match.

I know very well what the weaknesses are in my design and I will be explaining those shortly.

---

No you have not! Damn it, you make me repeat the same explanations over and over and over and over again. My time is very limited. Please be respectful of the fact that I have too much to do and not enough time. I am in a desperate financial condition, and we need to implement solutions for crypto asap because time is slipping away. Please try to upgrade the level of your comprehension. This post consumed 30 - 40 minutes of my time,

What you showed is that if you had some master in charge of the entire DAG then he could identify an ordering in the data structure, That master would benefit from a master clock and order the transactions chronologically. But I have already explained that the universe can't be synchronous (even if you built that centralized master funnel, it wouldn't interopt with the world and scale and be trustless). Thus you completely fail to consider that you also need an unambiguous rule which enforces your graphed ordering on all participants.

Since there is no (there can't be a) master clock in a DAG, then the only way to order the transactions is with a probabilistic assessment, but this assessment can't even be forced on all the participants. Thus the chaos and divergence will result. In other words, a DAG is Partition tolerant, therefore the Consistency is lost. The CAP theorem has so held.