Update Magic Numbers with constants and Update public variables with private for gas-efficiency

[allwin199]

This codebase currently uses magic numbers in certain areas. Replacing these magic numbers with descriptive constants will significantly improve code readability and maintainability.

erc20-paymaster/src/ERC20Paymaster.sol

Line 79 in 8e37933

uint256 public constant PRICE_DENOMINATOR = 1e6;

1e6 magic number can be updated with PRICE_DENOMINATOR in the below line

erc20-paymaster/src/ERC20Paymaster.sol

Lines 134 to 136 in 8e37933

	if (_priceMarkup < 1e6) {
	revert PriceMarkupTooLow();
	}

erc20-paymaster/src/ERC20Paymaster.sol

Lines 140 to 142 in 8e37933

	if (_tokenOracle.decimals() != 8 || _nativeAssetOracle.decimals() != 8) {
	revert OracleDecimalsInvalid();
	}

The above lines can be updated with the below lines of code.

uint256 private constant DECIMAL_PRECISION = 8;

.
.
.

if (_tokenOracle.decimals() != DECIMAL_PRECISION || _nativeAssetOracle.decimals() != DECIMAL_PRECISION) { 
     revert OracleDecimalsInvalid(); 
 } 

some more magic numbers are used. It can be updated with constants

Also, Instead of declaring all variables as public. All variables can be declared as private and we can write external getter functions to get the values. Which can prove to be gas-efficient.

-  uint256 public constant PRICE_DENOMINATOR = 1e6; 
+ uint256 private constant PRICE_DENOMINATOR = 1e6; 

External Getter function

function getPriceDenominator() external view returns(uint256){
     return PRICE_DENOMINATOR;
}

[allwin199]

@kristofgazso Making these changes will help in code readability and gas cost.

Making these changes will break the test cases. I am willing to work on it and make sure everything works as intended.

[Narendra-Reddy1]

Hey @allwin199 are you still working on this issue??
If not I'll take up this issue