Below is an explanation of who the document blockchain_privacy_leaks is for and its intention
core-contributor: The IFT needs to understand the entire problem scope that we aim to work to fix. Each CC needs to be intimately aware of the part of that problem that they work with and how the decisions they make impact things. It helps by mapping out all the areas that information leaks across the txn lifecycle.
developer: developers need to understand how information flows and where it can be leaked so that when they’re building they can make decisions appropriately.
non-tech-enthusiast: This document serves as education to the larger privacy and surveillance situation as well as helps build confidence that the IFT and the Logos project is serious about applying solutions to fix those problems.
layman: Same as above with non-tech enthusiast, general education. This audience is not a core demographic, but can be useful to them even if some of the technicals are beyond their reach.
officiant-regulator: TBD
web3-enthusiast: The current privacy narrative and focus is too narrow. It is mostly focused on application layer solutions. This article aims to expose the larger problem and the importance of applying attention and focus to it. Particularly, that only focusing on application layer privacy is insufficient. It also works to serve the purpose of showcasing that the IFT/Logos isn’t just following the meta, but contributing and working on actual problems.
investor: It’s important that investors understand the entire problem space such that they can identify a project’s potential to affect them and how to apply their investment.
researcher: This article aims at exposing the academic community to the breadth of problems at hand which require effort to fix. Real hard problems. It also helps to expose that audience to the fact that Logos is serious at solving them and we need their help in doing so.