"do you have any reason why nodes can't set a parameter to avoid relaying excessive transactions, or only relay transactions of a cretin size on condition the fee complies with xyz rules."
No. In fact, right now nodes won't relay transactions greater than 100 kB by default (but they will accept any size TX if mined into a valid-to-them block).
"miners obviously would want to avoid transactions that don't propagate through the network efficiently when using Xthin"
Yes, good point. If a miner's block is composed of all normal regular sized transactions, then probably Xthin will reduce the size of his block by factor of 24X or so. However, if a miner's block is composed exclusively of non-standard transactions that nodes don't relay, then Xthin won't reduce the size of his block at all. This means he'll pay 24X more in orphaning risk by including "weird" transactions [weird being defined as transactions the majority of nodes prefer not to relay].
"I can see applications for excessively sized transactions but it looks like they degrade the primary function of the network and should be avoided the exception being the user or service that benefits from such transactions. I would prefer to see a fee table that increases exponentially relative to transaction size. the net benefit is to penalize those who use the blockchain to do work and encourage other decentralized solutions to carry the cost and risk."
I think this will happen naturally as nodes and miners fine-tune their relay and mempool policies.
[doublepost=1478657566][/doublepost]By the way, @AdrianX: Are you implying that you'd prefer NOT to define a new TX type that removes the quadratic hashing issue, so as to naturally deter large/complex transactions?
No. In fact, right now nodes won't relay transactions greater than 100 kB by default (but they will accept any size TX if mined into a valid-to-them block).
"miners obviously would want to avoid transactions that don't propagate through the network efficiently when using Xthin"
Yes, good point. If a miner's block is composed of all normal regular sized transactions, then probably Xthin will reduce the size of his block by factor of 24X or so. However, if a miner's block is composed exclusively of non-standard transactions that nodes don't relay, then Xthin won't reduce the size of his block at all. This means he'll pay 24X more in orphaning risk by including "weird" transactions [weird being defined as transactions the majority of nodes prefer not to relay].
"I can see applications for excessively sized transactions but it looks like they degrade the primary function of the network and should be avoided the exception being the user or service that benefits from such transactions. I would prefer to see a fee table that increases exponentially relative to transaction size. the net benefit is to penalize those who use the blockchain to do work and encourage other decentralized solutions to carry the cost and risk."
I think this will happen naturally as nodes and miners fine-tune their relay and mempool policies.
[doublepost=1478657566][/doublepost]By the way, @AdrianX: Are you implying that you'd prefer NOT to define a new TX type that removes the quadratic hashing issue, so as to naturally deter large/complex transactions?