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

Consortium-level privacy #3109

Closed
RafaelAPB opened this issue Mar 15, 2024 · 2 comments
Closed

Consortium-level privacy #3109

RafaelAPB opened this issue Mar 15, 2024 · 2 comments
Assignees
Labels
IETF-SATP-Hermes Related to the Secure Asset Transfer Protocol as defined by the Internet Engineering Task Force.

Comments

@RafaelAPB
Copy link
Contributor

RafaelAPB commented Mar 15, 2024

Provide the option for gateways to assign privacy levels on view generation and processing, within the context of SATP.

Requirements:

  1. Define processes for consortium members to agree on privacy properties for view creation, processing, merging, and transfer.
  2. Negotiation phase at consortium creation to define desirable privacy properties
  3. Extend Consortium schema to have (an optional) BUNGEE privacy config (e.g., which processing algorithm, how to merge views, refer to the paper): packages/cactus-core-api/src/main/json/openapi.json and packages/cactus-core-api/src/main/typescript/generated/openapi/typescript-axios/api.ts)
  4. Pass those arguments from the Cacti node to the SATP instance. Pass such options from the SATP instance to the BUNGEE instance.
  5. Update Prometheus metrics to track privacy properties chosen
@RafaelAPB RafaelAPB added the IETF-SATP-Hermes Related to the Secure Asset Transfer Protocol as defined by the Internet Engineering Task Force. label Mar 15, 2024
@eduv09
Copy link
Contributor

eduv09 commented Mar 19, 2024

@RafaelAPB please assign me this one

@RafaelAPB
Copy link
Contributor Author

replaced by #3122

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
IETF-SATP-Hermes Related to the Secure Asset Transfer Protocol as defined by the Internet Engineering Task Force.
Development

No branches or pull requests

2 participants