Web3Privacy now community members were present at ETHRome hackathon & decided to hack the next version of so-called “l2beat for privacy”.
They created a live demo expanding privacy market data automation, delivering stunning visual design based on the current Web3Privacy ecosystem research.
Privacy projects present internal data in different formats, so it’s hard to scrap & automate it by default.
ETHRome team selected a set of variables to distinguish the level of technology complexity in privacy projects, covering:
privacy
asset security
traceability
transaction linkability
data obfuscation
code quality.
Additionally, fundamental information in evaluating privacy projects
legal matters
identity
privacy policies
tracked data
data custody
Visualisation helped to understand data-set MVP on a preview page & broader data-set inside a separate project profile landing.
Solution
We have addressed these aspects by defining a comprehensive Data Manifest, outlining the necessary criteria for privacy-focused projects and built a validated variables dataset. Learn more about our Data Manifest
The team researched what data could be standard from project to project, meaning future automation.
Project data set has been prototyped and written down on GitHub.
An additional JSON file applying data set to DeFi privacy category has been created to simplify back-end & front-end interaction. This will help to streamline new updates & decrease the amount of micromanagement.
Each privacy project “received” dedicated YAML featuring all the necessary data related to the manifesto mentioned above. This helped to understand the missing gaps between prototype & reality (what data is available online, on-chain; in which form).
Summarising graphics covers different aspects of the prototype
Creating a user-friendly, easily navigable, and organised project research platform was our next challenge. The platform needed to offer a concise yet powerful overview, including additional scoring based on various categories.
Moreover, integrating the Web3Privacy design language was essential for consistency and user experience.
Solution
We have meticulously designed the platform's layout and structure using Figma, ensuring simplicity, clarity, and seamless integration of the Web3Privacy design language. [Explore our design file] + [Try prototype]
Privacy service profile example (1st screen)
ETHRome judge opinion (Mykola Siusko): profile data visualisation helped to understand “the best case scenario” when all the data could be filled & shared with the visitors. This also helped to relate the scoring algorithm with a new extensive dataset (think of an IMDB-alike film page with separate scoring & general information about a movie).
Prototype significantly extended data set per project needed to be collected - demanding too many manual labour hours. This led to MVP criteria consideration & solutions for projects to add their data by themselves (expanding the GitHub contributors list).
Minimum Viable Product objectives
Fetching data from an open-source database
Minimal front-end for data exploration
Filtering projects by their main aspects
Solution Web3Privacy research client
In order to collect as much relevant data for future platform developments, we would love to ask all included projects (500+) to fill up their information and send them an easy-to-use form.
Solution
Note: we already went further & welcome different projects to make Pull requests & provide information publicly: general brief + PRs from
Bonus
“Asset Router” is a visual helper simplifying privacy-journey related to transaction of the different assets. It could facilitate understanding of the cross-chain, project-2-project linkability & necessity to have wider range of privacy then related to specific application/solution.
Github
Prototype
ETHRome hackathon contribution
Full prototype