Working Document: Privacy Requirements Survey

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 DOING

IMPORTANT

Please hold for further instructions to start providing feedback


Questionnaire Section A - Responder Categorization

QuestionsAnswersComments / Notes
Financial Market RoleSelect One from Liste.g., Asset Manager, Broker Dealer, Payment Processor, CCP, Tech Vendor, etc.
Main Flow of Interest for Use CasesSelect One from Liste.g., Asset Issuance, Asset Transfer, Asset Exchange (e.g., DvP), etc.
Active Role in Flow of Interest for Use CasesSelect One from Liste.g., Delivery Side, Payment Side
Main Client ProfileSelect One from Liste.g., Retail Investor, Institutional Investor
Private Networks vs Public NetworksSelect One from ListPrivate Networks, Public Networks
Blockchain-based Solutions in ProductionY/N
Company's years in Digital Assets SpaceSelect One from ListLess than 5 years, 5 to 7 years, More than 7 years







Questionnaire Section B - Privacy Feature Relevance

QuestionsAnswersComments / Notes
Relevance of Transaction Data Privacy1 to 41 (Very Low) to 4 (Very High)
Relevance of Transaction Sender Privacy1 to 41 (Very Low) to 4 (Very High)
Relevance of Transaction Receiver Privacy1 to 41 (Very Low) to 4 (Very High)
Relevance of Asset-holder Balance Privacy1 to 41 (Very Low) to 4 (Very High)
Relevance of Asset-holder Activity Records Privacy1 to 41 (Very Low) to 4 (Very High)
Relevance of Retail / Individual Data Privacy1 to 41 (Very Low) to 4 (Very High)
Relevance of Institutional / Organization Data Privacy1 to 41 (Very Low) to 4 (Very High)




Questionnaire Section C - Privacy Features Attributes

QuestionsAnswersComments / Notes
Data Confidentiality vs Data Masking (Obscuring)Select One from ListData Confidentiality, Data Masking (Obscuring)
Identity Anonymity vs Identity Masking (Obscuring)Select One from ListIdentity Anonymity, Identity Masking (Obscuring)




Questionnaire Section D - Privacy Features Trade-Offs

QuestionsAnswersComments / Notes
Data Composability vs Data PrivacySelect One from ListComposability, Privacy
Data Historical Records vs Data PrivacySelect One from ListHistorical Records, Privacy
Data Off-Chain vs Data On-ChainSelect One from ListOn-Chain, Off-Chain
Data Self-Verification vs Delegated Data VerificationSelect One from ListData Self-Verification, Delegated Data Verification
Centralized Data Access vs Distributed DataSelect One from ListCentralized Data Access, Distributed Data
Asset Interoperability vs Data PrivacySelect One from ListAsset Interoperability, Data Privacy
Real-Time Reconciliation vs T+X ReconciliationSelect One from ListReal-Time Reconciliation, T+X Reconciliation
Peer-to-Peer Data Exchange vs Multi-Party Data ExchangeSelect One from ListPeer-to-Peer Data Exchange, Multi-Party Data Exchange
On-Chain Data Proofs vs On-Chain Privacy-Preserving DataSelect One from ListOn-Chain Data Proofs, On-Chain Privacy-Preserving Data




Questionnaire Section E - Privacy Features Requirements

QuestionsAnswersComments / 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

QuestionsAnswersComments / Notes
Main concern regarding existing Privacy SolutionsSelect One / Two from ListPerformance, Cost, Complexity, Maturity, Adoption, Integration
Main challenge for your main use cases to get to productionSelect One / Two from ListPerformance, Privacy, Standards, Regulatory Clarity, Tech Adoption
Main risks to your on-chain dataSelect One / Two from ListQuantum, Data Leaks, Regulatory Requirement