Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assignment Proposal: Fair and Transparent Salaries #52

Merged
merged 1 commit into from
Nov 16, 2023

Conversation

ChristoferVikstroem
Copy link
Contributor

Assignment Proposal

Title

Fair and Transparent Salaries (FaTS)

Names and KTH ID

Christofer Vikström ([email protected])
Vivi Andersson ([email protected])

Deadline

  • Task 1

Category

  • Smart Contract Protocol Development

Description

The primary objective of this project is to foster a culture of increased salary transparency. By leveraging blockchain technology, we aim to create a secure and immutable system for recording anonymized financial details related to employee salaries. This initiative seeks to empower employees, address disparities, and ultimately contribute to a fair and transparent salary system. This system will serve as a transparent ledger accessible to all relevant parties within the organization. Through this technology, employees will have the ability to confidently validate the correctness of their compensation and gain insights into the salaries of their peers without compromising individual privacy.

Relevance

In many organizations, the culture of secrecy around salaries prevails, hindering employees from validating the fairness of their compensation and creating an atmosphere of distrust. The common practice of discouraging employees from discussing their salaries exacerbates this issue. To address these challenges, we propose a solution that not only ensures employees have access to their own salary details but also facilitates a broader understanding of compensation structures within the company.

@ChristoferVikstroem ChristoferVikstroem changed the title Create README.md Assignment Proposal: Fair and Transparent Salaries Nov 14, 2023
@Deee92
Copy link
Collaborator

Deee92 commented Nov 15, 2023

Hi @ChristoferVikstroem and @anderssonvivi, interesting proposal! Do you have some ideas already about the technologies / languages / tools you might use for the implementation?
Could you also share more info, such as the kinds of data that gets pushed on the chain, who adds it, etc?

@ChristoferVikstroem
Copy link
Contributor Author

Hi @ChristoferVikstroem and @anderssonvivi, interesting proposal! Do you have some ideas already about the technologies / languages / tools you might use for the implementation? Could you also share more info, such as the kinds of data that gets pushed on the chain, who adds it, etc?

Hello Deepika!
We are exploring different languages, perhaps writing Polygon contracts in Solidity or Solana. Some technologies and tools being considered now are validation methods, verification (with asynchronous keys for the employees) so that an employee can validate that the stated amount is accurate, and fingerprint/sign correct salaries.

The data that gets pushed on the chain might look something like this:
Job title, Unique hash (for verification), Salary paid this month
Job title, Unique hash (for verification), Salary paid this month
Job title, Unique hash (for verification), Salary paid this month
-Link or function to verify that your salary is correct-

The employer (or HR) would be the person who adds the record to the chain and also the person who manages discrepancies/confirms fingerprints.

@Deee92 Deee92 self-assigned this Nov 16, 2023
@Deee92 Deee92 added the smart-contract-protocol Smart contract protocol to be presented at the Grand Oral label Nov 16, 2023
@Deee92 Deee92 merged commit 3146822 into KTH:2023 Nov 16, 2023
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
smart-contract-protocol Smart contract protocol to be presented at the Grand Oral
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants