zkPayslip runs payroll inside the STRK20 privacy pool. Nobody sees who was paid what — and any employee can still prove their income to exactly one verifier, exactly once.
When a bank asks for proof of income, an employee paid on-chain has two options today. Both of them cost something.
The payment rail already exists — STRK20 hides amounts and counterparties inside the pool. zkPayslip adds the missing piece: scoped, single-use income proofs on top.
The employer funds a treasury in the pool. One public deposit; everything after it stays dark.
Each cycle, salary moves channel-to-channel inside the pool. No amounts, no counterparties on-chain.
An employee mints a payslip proof: one fact, one verifier, an expiry, a nullifier.
The verifier checks it in one click. No wallet, no history, no second read.
We state it plainly, because the honesty is the product. Only movement inside the pool is private — the edges are public by design.
| Aspect | Stays in the dark | Public by design |
|---|---|---|
| Counterparties | Who paid whom | The shield deposit names the treasury, nobody else |
| Amounts | Each employee's salary | Total budget at shield; amounts that unshield out |
| Activity | Which notes were spent | That the pool is used, and when |
| Proofs | The payslip's single fact | A payroll run's size (action count) |
STRK20 ships a viewing-key escrow: at registration, each user's key is encrypted to an auditor, who can then decrypt that user's entire history. That is the right tool for lawful process — and the wrong tool for a bank loan.
| Aspect | Viewing-key escrow | zkPayslip proof |
|---|---|---|
| Scope | One user's entire history | One fact, chosen per proof |
| Audience | The auditor named by governance | Any verifier the employee picks |
| Access | Standing while key access persists | One redemption — then the nullifier burns |
| Expiry | None | Set per proof |
Everything below reflects the repository as it is right now.
Public repo, MIT license — registered for the Private Sprint hackathon (RFP-11, Payments).
Wallet-API actions — shield, private transfer, unshield, shielded balances through the user's own wallet.
Mainnet transactions — the first pool-touching hashes land in strk20.json as they happen.
Batch benchmark — recipients-per-transaction will be our own measured number, not a quoted one.
Nothing on this page is a placeholder for a claim we cannot back. Numbers appear when measured; hashes appear when confirmed.
No. Pool notes decrypt only with your viewing key, which never leaves your wallet — not even this application sees it. The employer sees their own treasury and commitments, nothing else.
Redemption is single-use and bound to one verifier address; a second attempt fails on-chain. What a legitimate verifier retains after reading it is inherent to any disclosure — we say that plainly rather than overclaim.
No. STRK20 is a note-based pool with on-chain STARK proof verification and mandatory deposit screening, enforced on-chain. Private from the public — not from lawful oversight.
The hackathon submission closes at 23:59 UTC. Whatever the repository shows at that moment is the entry: the app, the mainnet hashes, the demo video, the documentation.