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

Support C2D on confidential networks (need signature to decrypt files object) #692

Closed
paulo-ocean opened this issue Sep 19, 2024 · 3 comments
Assignees
Labels
Type: Enhancement New feature or request

Comments

@paulo-ocean
Copy link
Contributor

paulo-ocean commented Sep 19, 2024

Right now this is not fully supported because at least for the "initialize" and "startCompute" operations we need to decrypt the DDO files object.
When we're dealing with a confidential EVM and template 4 we need to get the files object from a smart contract call, and for that we need a consumer signature, which ATM some of these operations are not requiring

@paulo-ocean paulo-ocean added the Type: Enhancement New feature or request label Sep 19, 2024
@paulo-ocean paulo-ocean changed the title Support C2D on confidential networks Support C2D on confidential networks (need signature to decrypt files object) Sep 19, 2024
@mihaisc
Copy link
Contributor

mihaisc commented Oct 14, 2024

is this done?

@paulo-ocean
Copy link
Contributor Author

is this done?

Nope, its not. We will need to refactor some C2D APIs, node side at least.

@paulo-ocean paulo-ocean self-assigned this Oct 23, 2024
@paulo-ocean
Copy link
Contributor Author

paulo-ocean commented Nov 11, 2024

closing this one (will be part of #705 )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants