Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely: What characteristics of an object determine its consensus number? Here  analyze how the consensus por of various objects changes without changing their functionality, but by placing certain restrictions on the object usage. For example it is shown that the consensus number of either a bounded-use queue or stack is 3 while the consensus number of the long-lived bounded-size and unbounded-size versions of either is 2. Similarly  show that the consensus number of restricted versions of Fetch & Add, Swap and Set are infinite (n) while for the unrestricted counterparts it is 2.  thus underlines the fact that the consensus number of an object reflects the amount of coordination required in the object implementation and not by its capacity. That is, the more corners, broken edges, and other hard limitations placed on an object, the higher its consensus number tends to be.
['Yehuda Afek', 'Eran Shalom']
I am writing a research paper on a idea Less is more : Consensus gaps between restricted and unrestricted objects
[{"from": "human", "value": "I am writing a research paper on a idea Less is more : Consensus gaps between restricted and unrestricted objects"}, {"from": "gpt", "value": "Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely: What characteristics of an object determine its consensus number? Here  analyze how the consensus por of various objects changes without changing their functionality, but by placing certain restrictions on the object usage. For example it is shown that the consensus number of either a bounded-use queue or stack is 3 while the consensus number of the long-lived bounded-size and unbounded-size versions of either is 2. Similarly  show that the consensus number of restricted versions of Fetch & Add, Swap and Set are infinite (n) while for the unrestricted counterparts it is 2.  thus underlines the fact that the consensus number of an object reflects the amount of coordination required in the object implementation and not by its capacity. That is, the more corners, broken edges, and other hard limitations placed on an object, the higher its consensus number tends to be."}]