BillingRules currently has some differences relative to AionTransaction which seem to be either omissions or AVM-specific logic. These should be formalized, since the logic in that class seems very old and probably only a placeholder until we could more thoroughly investigate it.
I propose we make the following changes:
combine getDeploymentFee and getCodeStorageFee, since they are always used in the same cases and should capture one idea
add the 200_000 basic deployment fee which is applied to FVM contracts, within the kernel
remove the PROCESS fee
treat the number of classes distinctly from just applying some math to merge it into the logic around byte size of JAR
BillingRulescurrently has some differences relative toAionTransactionwhich seem to be either omissions or AVM-specific logic. These should be formalized, since the logic in that class seems very old and probably only a placeholder until we could more thoroughly investigate it.I propose we make the following changes:
getDeploymentFeeandgetCodeStorageFee, since they are always used in the same cases and should capture one ideaPROCESSfee