Implement Dynamic Gas Cost Calculation for IP Graph Function Calls

[kingster-will]

Description and context

We propose to implement a dynamic gas cost calculation mechanism for different IP Graph function calls, based on memory usage, storage access, and CPU consumption. This enhancement aims to optimize the gas efficiency of our smart contracts by accurately reflecting the computational resources required for each function call.

Details

The current implementation of the IP Graph functions does not dynamically calculate gas costs based on the actual computational resources used. This can lead to inefficiencies, where some operations may consume more gas than necessary.

Implementation Steps:

1. Benchmarking: Conduct a comprehensive benchmarking of all IP Graph functions to measure memory usage, storage access patterns, and CPU consumption under various conditions.
2. Gas Cost Model: Develop a gas cost model that calculates the gas cost dynamically based on the benchmarking data. This model should consider gas pricing mechanisms and adjust for future changes in the protocol.
3. Integration: Integrate the gas cost model into the IP Graph functions, ensuring that gas costs are calculated dynamically at runtime based on the actual computational resources used.

Acceptance Criteria

• A dynamic gas cost calculation mechanism is implemented and integrated with the IP Graph functions.
• The mechanism accurately calculates gas costs based on memory usage, storage access, and CPU consumption.
• Benchmarking data is collected and used to inform the gas cost model.
• The system undergoes thorough testing to ensure accuracy and efficiency of gas cost calculations.
• Documentation is updated to reflect the new dynamic gas cost calculation mechanism.

[kingster-will]

TODO: Add EIP reference link

[LeoHChen]

A good reference for gas cost of precompile.

https://github.com/maticnetwork/Polygon-Improvement-Proposals/pull/147/files#diff-84cb2a1283c96f603aa517fbca6928bd08a918678f466fa136dd8a92afb5a58c

[Ramarti]

Some feedback after talking with auditors scoping, we should have different pricing strategies for read / write. Reads could also be a DDOS vector, but they should be cheaper.