Private payroll · Starknet mainnet

Salaries in the dark.
Proof in the open.

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.

PAYSLIP PROOF№ 0042FACTINCOME ≥ 4,200 STRK / MOVERIFIER0x07d3…e91aEXPIRY2026-09-30NULLIFIER0x8f4a…c2VALID ONCEONE VERIFIER · ONE REDEMPTION
The problem

A wallet address is a financial strip-search.

When a bank asks for proof of income, an employee paid on-chain has two options today. Both of them cost something.

Path A — complyHand over the wallet address. The entire financial history walks out with it: every deposit, every counterpart, every balance.
Path B — refuseProve nothing. No loan, no lease, no visa, no job.
Path C — zkPayslipProve the one fact the verifier needs. Keep the rest in the dark.
Mechanism

Four moves. No leaks.

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.

Step 01
Shield

The employer funds a treasury in the pool. One public deposit; everything after it stays dark.

Step 02
Pay

Each cycle, salary moves channel-to-channel inside the pool. No amounts, no counterparties on-chain.

Step 03
Prove

An employee mints a payslip proof: one fact, one verifier, an expiry, a nullifier.

Step 04
Verify

The verifier checks it in one click. No wallet, no history, no second read.

Honesty

What the pool hides. What stays public.

We state it plainly, because the honesty is the product. Only movement inside the pool is private — the edges are public by design.

AspectStays in the darkPublic by design
CounterpartiesWho paid whomThe shield deposit names the treasury, nobody else
AmountsEach employee's salaryTotal budget at shield; amounts that unshield out
ActivityWhich notes were spentThat the pool is used, and when
ProofsThe payslip's single factA payroll run's size (action count)
Why a new disclosure layer

Why not just hand over the auditor key?

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.

AspectViewing-key escrowzkPayslip proof
ScopeOne user's entire historyOne fact, chosen per proof
AudienceThe auditor named by governanceAny verifier the employee picks
AccessStanding while key access persistsOne redemption — then the nullifier burns
ExpiryNoneSet per proof
Where the build stands

Live facts only.

Everything below reflects the repository as it is right now.

Live

Public repo, MIT license — registered for the Private Sprint hackathon (RFP-11, Payments).

Live

Wallet-API actions — shield, private transfer, unshield, shielded balances through the user's own wallet.

Pending

Mainnet transactions — the first pool-touching hashes land in strk20.json as they happen.

Pending

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.

Common questions

Asked, answered.

Can my employer see my balance?

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.

Can a verifier reuse or forward my proof?

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.

Is this a mixer?

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.

What happens on August 31?

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.

Pay the team.
Prove the salary.
Nothing else.

Open the app