Community Consideration: Explore Query Charging

Hi Jordan

We are currently re-scoping this feature and are now proposing to:

  1. Build a feature that allows developers to get access to query-related statistics via the canister status API. This is basically the entire mechanism that we envision a possible solution for query charging (a way to deterministically aggregate per-node query statistics), without actually charging for anything.

  2. Hold back query charging for now.

Step 1. will hopefully help developers to learn something about the usage of query calls in their canisters and help optimize code, also in preparation for query charging.

Does this make sense?

We are planning to put up a motion proposal for voting soon.