Skip to content
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

Clarify behavior of get_*_info RPCs #272

Open
masomel opened this issue Apr 24, 2020 · 1 comment
Open

Clarify behavior of get_*_info RPCs #272

masomel opened this issue Apr 24, 2020 · 1 comment
Labels
documentation Primary component is missing or incorrect documentation

Comments

@masomel
Copy link

masomel commented Apr 24, 2020

The current semantics for these operations is to return metadata about a given enclave or contract. From several discussions about the behavior (and naming) of the get_enclave_info and get_contract_info RPCs in #259, there's a question as to whether these RPCs should also be performing additional contract or enclave verification steps.

@marcelamelara marcelamelara added the documentation Primary component is missing or incorrect documentation label Feb 3, 2023
@cmickeyb
Copy link
Contributor

cmickeyb commented Apr 4, 2023

Need more details on this. What is the behavior that you want?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Primary component is missing or incorrect documentation
Projects
None yet
Development

No branches or pull requests

3 participants