execute_read_only_bytecode and execute_read_only_call are two endpoints that has 2 usages that collide :
Calling read_only functions to gather informations on a smart-contract
Simulate an operation gather the changes it make in the network and the gas used
Problem
This two use case causes problem of coherence issues. For example we had the issue with the minimal fees that was checked even in the usecase of just a read_only which is a non-sense, but we want to catch a too low fee in case of a simulation to be more close to a real operation.
Context
execute_read_only_bytecodeandexecute_read_only_callare two endpoints that has 2 usages that collide :Problem
This two use case causes problem of coherence issues. For example we had the issue with the minimal fees that was checked even in the usecase of just a read_only which is a non-sense, but we want to catch a too low fee in case of a simulation to be more close to a real operation.