Execution across the Wasm interface between the host node and the guest application costs resources in terms of execution time, but it is currently not charged for any fees.
Proposal
Update the TransactionTracker to track system API calls and charge a fee (even if zero) on each and every one of them.
I suspect the only design decision is whether the fees are specified as "dense" struct (continuing the existing code) or as a sparse map (say by using strings as keys or defining an enum of system-api names).
Motivation
Execution across the Wasm interface between the host node and the guest application costs resources in terms of execution time, but it is currently not charged for any fees.
Proposal
Update the
TransactionTracker
to track system API calls and charge a fee (even if zero) on each and every one of them.