Loops HousePayslip Proof

NEAR HACKATHON
Links
Team
1 member- LEOwner
Lev
Overview
People paid across borders have to prove income to landlords, banks and consulates, but a PDF payslip is easy to forge, and a payroll that settles in stablecoins leaves no bank statement. Putting the payroll on a public chain would expose every colleague's salary.
Payslip Proof lets an employer commit a payroll run to NEAR as one Merkle root while every pay line stays private. Leaves are salted and domain-separated, the tree has no sums, it is padded with random leaves to hide headcount, and leaf order is shuffled. Each employee gets a payslip file: their own line, a salt and four sibling hashes. A landlord drops it into the web page or runs verify-payslip. The verifier recomputes the root, reads the commitment from the NEAR contract and prints "VERIFIED: 5,800.00 USD for 2026-10, paid by ", or fails. Auditors get disclosure packs for a subset (one department) or, by revealing every line, a full audit. This is not zero-knowledge and the README says so.
How NEAR fits in: our own Rust contract, payroll-commit (near-sdk-rs), stores employer-owned, immutable, revocable commitments with caller-paid storage. The employer's NEAR account is the identity and the access control, and is bound inside every leaf. It is deployed on testnet and tested on a real local sandbox (14 Rust tests, 65 Node tests, tamper cases). NEAR Intents 1Click dry-run quotes show what each person would receive in the asset and chain they prefer (Base, Ethereum, Solana, Bitcoin, NEAR); nothing is ever executed.
Runs from a clean clone with npm run demo, no keys and no network. Recorded and live data are labelled. Not run on mainnet.