Pruxel
Payroll by Proof of Contribution, not Politics
Created on 21st September 2025
•
Pruxel
Payroll by Proof of Contribution, not Politics
The problem Pruxel solves
Problem: Paying fairly is hard
Developers pour hours, nights, weekends, their creative energy, into writing code, fixing bugs, reviewing pull requests, mentoring juniors.
But when payday comes, what happens?
Their effort is invisible. Managers can’t see the unseen hours spent debugging or reviewing.
Pay feels unfair. Some voices get rewarded, others get left behind. (Workplace Politics)
The Gap
This isn’t just about money. It’s about trust.
When contributions don’t match recognition, people feel:
- Overlooked.
- Underappreciated.
- Replaced instead of valued.
At the heart of it: there’s a massive disconnect between contribution and compensation.
And this disconnect isn’t just unfair, it’s demoralizing. It kills innovation before it even starts.
Why Now
-
Engineering has gone global + async. Contributions live in GitHub activity streams.
-
Crypto/payments matured (streams, stablecoins) → instant programmable payouts.
-
Trust is a feature. Teams and DAOs demand verifiable, fair allocation.
Solution: Contribution‑Indexed Payroll (CIP)
-
Pruxel converts objective repo signals into payout shares, then pays automatically.
-
Connect GitHub → Score contributions with a published rubric → Allocate shares → Pay (stream/instant) → Audit every rupee/USDC to events.
5‑step flow graphic (Connect → Score → Allocate → Pay → Audit).
Challenges we ran into
A big hurdle was measuring quality vs. quantity of GitHub contributions. Commits alone were misleading. We solved it with a weighted scoring system (PRs, reviews, issues, tests) and fixed data/visualization bugs with normalization. This made payouts fair and explainable.
Technologies used
Cheer Project
Cheering for a project means supporting a project you like with as little as 0.0025 ETH. Right now, you can Cheer using ETH on Arbitrum, Optimism and Base.
