@here This topic has now been open for a while and comes up again and again. For this reason, I’d like to start a small poll to gauge the current sentiment
- Allow canister_status to be made public with the understanding this could expose secrets and could be extended to make all code & state of the canister public, i.e, public canister status == public canister.
- Allow canister_status to be made public with a fuzzy or low-resolution cycles balance.
- Standardize a canister/app level status/metrics endpoint that includes this information.
- Don’t do anything. Black hole canister approach is good enough.
0
voters