Ethereum Proposal Relativistic Penalties for Code that is not Machine Cycle optimized for efficiency.

Ethereum Proposal Relativistic Penalties for Code that is not Machine Cycle or Storage/Memory optimized for efficiency.

The gist of this post is that if your Algorithms get priority based on time in terms of their resource hogging you are more incentivized to streamline them as it will affect user experience and your efforts on frontend. As frontend and user experience is the main metric of success of an Ethereum Project.

I believe that the current model of charging higher gas fees for your inefficient EVM code to be prioritized over much simpler code which provides miners less gas fees but is simple to execute and actually efficiently manage the Transactions Per Seconds should be punished in Priority of execution. I mean if your code is computationally heavy it should be run last not first irrespective of what Gas fees you are willing to pay.

The Ethereum EVM should be treated as an 8 bit computer rather than a datacenter server.

Eth developers should work with mentality of an ASSEMBLY developer rather than a blockchain developer.

For example for/while loops in Solidity can be limited to 256 iterations.

Another solidity example would be

First Function

mapping(address => uint256) private userIndex;

function setUserIndex(address UsrAddress) private returns(uint256){if(userIndex[address(UsrAddress)] < 2){currIndex += 1;userIndex[address(msg.sender)] = currIndex;}return userIndex[address(UsrAddress)];}

function getUserIndex(address UsrAddress) private view returns(uint256){if(userIndex[address(UsrAddress)] > 1){return userIndex[address(UsrAddress)];}return 0;}

mapping(uint256 => someProperty) someProperty;

instead of

Second Function

mapping(address => someProperty) someProperty;

that simple function saves storage and memory but lazy devs will go for second function

Vitalik himself is proposing Calldata Limit per Block to Lower Ethereum Gas Costs.

The problem is we are attacking a problem in a way where higher gas spending is rewarded for computationally intense transaction while it should be that computationally intense transaction should have be pushed to the back of queue as it is hogging resources most importantly as all calculations need to be propogated across all nodes.

Again the philosophy of my post is "Let excel do the heavy lifting. Let Ethereum record and validate the Heavy Lifting amongst peers."

Again I want to encourage Blockchain Devs to take a moment and streamline their code.