Protocol Design

[vivi365]

New Protocol Design

After consulting with Mojtaba, we have decided to change the design of the protocol. To enhance privacy without involving zk solutions (which Mojtaba through would be a whole another project), we will move the view from one company and individual "comparison" of salaries within the company, to a more sector-wide view. In this model, a company submits its data, and an assumption is that this data is already "verified".

We will use two contracts for this:

Company contract

• The contract owner is the person who created it using company factory contract.

• Modifies the company's list of employees, including their digital wallet, title and salary (add, remove, contains)

• Allows employees to verify the authenticity of their stated salary

• Functionality of the company contract:

1. Add, remove and update employee data
2. Verify the salary
3. A lookup function: a. Query digital wallet b. Returns Title, Salary and if salary is verified by employee.

Company factory contract

• Built on Company Contract
• Creates a company contract, tied to the wallet of the person who invokes it
• Can be used to query other contracts to get details about salaries
• Requirements for creating a company contract:

1. Digital Wallet to connect the company to
2. Writing what sector the company operates in

• Functionality of the company factory contract:

1. Company Contract creation
2. Storing companies based on sector
3. Allowing queries for look-ups a. Specific companies in a sector b. Bigger picture queries (average salary of the sector)
4. See total number of verified salaries for specific companies and the entire sector.

[vivi365]

Frontend

In the front end, we would like to:

• Be able to aggregate some average view of a sector
• Perhaps view a specific (anonymous) company
• ..