-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add sections for new subnet_stats endpoint #351
base: master
Are you sure you want to change the base?
Conversation
🤖 Here's your preview: https://pjpim-riaaa-aaaak-qckja-cai.icp0.io/docs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
If a canister wants to get the information for it's own subnet, how is it supposed to figure out which subnet it is on? |
The registry has an endpoint that serves this information. |
…lable to execution environment (#2248) This is an alternative to #2248 and #2082 This PR passes the running replica version to the execution environment, from where it can be used [in a future management canister call.](dfinity/interface-spec#351): #2202 --------- Co-authored-by: Michael Weigelt <michael.weigelt@dfinity.com>
…lable to execution environment (#2248) This is an alternative to #2248 and #2082 This PR passes the running replica version to the execution environment, from where it can be used [in a future management canister call.](dfinity/interface-spec#351): #2202 --------- Co-authored-by: Michael Weigelt <michael.weigelt@dfinity.com>
In certain circumstances, canisters wish to learn about subnet-specific data or metadata. This endpoint enables these use cases, starting with exposing the replica version a subnet is currently running.
Open questions: