Goal & Background
Per discussions during the WG General Meetings (on Aug 29th and 30th), it was decided to pivot to use a survey to try to collect insights from the group. The goal is to define a survey that helps define and identify privacy requirements from enterprise users of Besu. This information will shed light on limitations of existing privacy features of Besu, as well as kick-off discussions about whether or not some requirements are to be solved from the network / infrastructure layer of the web3 stack.
There are several challenges to conducting this survey. These were discussed during the Aug 30th meeting (recording available at: 07 - WG General Meeting | August 29th & 30th)
Co-Chairs will open the survey design to the group. This is why this document has been created. Members will use comments to share suggestions and recommendations.
Survey Questionnaire TO-DO
IMPORTANT
Please hold for further instructions to start providing feedback
Questionnaire Section A - Responder Categorization
Questions | Answers | Comments / Notes |
---|---|---|
Market Role | Select One from List | e.g., Asset Manager, Broker Dealer, CCP, etc. |
Main Flow of Interest for Use Cases | Select One from List | e.g., Asset Issuance, Asset Transfer, Asset Exchange (e.g., DvP), etc. |
Active Role in Flow of Interest for Use Cases | Select One from List | e.g., Delivery Side, Payment Side |
Main Client Profile | Select One from List | e.g., Retail Investor, Institutional Investor |
Private Networks vs Public Networks | Select One from List | Private Networks, Public Networks |
Blockchain-based Solutions in Production | Y/N | |
Company's years in Digital Assets Space | Select One from List | Less than 5 years, 5 to 7 years, More than 7 years |
Questionnaire Section B - Privacy Feature Relevance
Questions | Answers | Comments / Notes |
---|---|---|
Relevance of Transaction Data Privacy | 1 to 4 | 1 (Very Low) to 4 (Very High) |
Relevance of Transaction Sender Privacy | 1 to 4 | 1 (Very Low) to 4 (Very High) |
Relevance of Transaction Receiver Privacy | 1 to 4 | 1 (Very Low) to 4 (Very High) |
Relevance of Asset-holder Balance Privacy | 1 to 4 | 1 (Very Low) to 4 (Very High) |
Relevance of Asset-holder Activity Records Privacy | 1 to 4 | 1 (Very Low) to 4 (Very High) |
Relevance of Retail Investor Data Privacy | 1 to 4 | 1 (Very Low) to 4 (Very High) |
Relevance of Institutional Investor Data Privacy | 1 to 4 | 1 (Very Low) to 4 (Very High) |
Questionnaire Section C - Privacy Features Attributes
Questions | Answers | Comments / Notes |
---|---|---|
Data Confidentiality vs Data Masking (Obscuring) | Select One from List | Data Confidentiality, Data Masking (Obscuring) |
Identity Anonymity vs Identity Masking (Obscuring) | Select One from List | Identity Anonymity, Identity Masking (Obscuring) |
Questionnaire Section D - Privacy Features Trade-Offs
Questions | Answers | Comments / Notes |
---|---|---|
Data Composability vs Data Privacy | Select One from List | Composability, Privacy |
Data Historical Records vs Data Privacy | Select One from List | Historical Records, Privacy |
Data Off-Chain vs Data On-Chain | Select One from List | On-Chain, Off-Chain |
Data Self-Verification vs Delegated Data Verification | Select One from List | Data Self-Verification, Delegated Data Verification |
Centralized Data Access vs Distributed Data | Select One from List | Centralized Data Access, Distributed Data |
Asset Interoperability vs Data Privacy | Select One from List | Asset Interoperability, Data Privacy |
Real-Time Reconciliation vs T+X Reconciliation | Select One from List | Real-Time Reconciliation, T+X Reconciliation |
Peer-to-Peer Data Exchange vs Multi-Party Data Exchange | Select One from List | Peer-to-Peer Data Exchange, Multi-Party Data Exchange |
Questionnaire Section E - Privacy Features Requirements
Questions | Answers | Comments / Notes |
---|---|---|
Asset-holder's Identity Privacy regulatorily required for your main Use Cases? | Y/N | |
Asset-holder's Balance Privacy regulatorily required for your main Use Cases? | Y/N | |
Asset-holder's Asset Portfolio Privacy regulatorily required for your main Use Cases? | Y/N | |
Asset-holder's Activity Privacy regulatorily required for your main Use Cases? | Y/N | |
Questionnaire Section F - Privacy Solutions Assessment
Questions | Answers | Comments / Notes |
---|---|---|
Main concern regarding existing Privacy Solutions | Select One from List | Performance, Cost, Complexity, Maturity, Adoption, Integration |
Main challenge for your main use cases | Select One from List | Performance, Privacy, Standards, Regulatory Clarity, Tech Adoption |