Private payroll and treasury disbursement at company scale

What this enables

• →Onchain companies that can compete for senior talent. The single largest barrier to crypto-native companies hiring senior engineers and execs is salary visibility. Today a candidate's choice is "compensation public on the internet" or "take the Web2 offer." STRK20 closes the gap - onchain payroll handled exactly as any traditional employer handles it.
• →Vesting without front-running. Token vesting unlocks are the most reliably gamed events in crypto. Markets price in the dump weeks ahead. Founders get accused of dumping before they've sold anything. Private vesting lands tokens in encrypted notes; the schedule is enforced on-chain but the amounts and timing of recipient sells aren't public.
• →DAO treasury confidentiality with public accountability. Aggregate spend is visible ($847K to 73 contributors this quarter, on-chain verifiable). Per-recipient breakdown is encrypted. A governance committee with viewing-key access can verify the split. First treasury model that doesn't force a choice between public accountability and internal cohesion.
• →Contractor and grant networks without recipient doxxing. Crypto gig platforms pay thousands of contributors in public transactions. Top earners get profiled, recruiters scrape leaderboards, phishers target high-value addresses. STRK20 keeps the rails public-accountable while taking the contributor base off the surveillance target list.
• →Compliance that tax authorities already understand. Confidential from the public, fully disclosed to the tax authority - the W-2 / P60 / T4 model. Each recipient generates a viewing-key-derived income statement; the payer generates the full payroll book. Cryptographic proof of completeness; no fabrication, no omission.

What you build

A Payroll helper contract managing recurring (payer, recipient) channels. Batched disbursement transactions (one tx, 50 recipients). Vesting schedules with on-chain enforcement and private amounts. Termination as a recorded-on-chain event with no public disclosure. Admin tooling (session-key scoped to a payroll cycle's budget) and the recipient discovery experience (paymaster-sponsored - no recipient signature ever required).

Why this isn't Sablier or Vesting.so

Both put schedules on public ledgers. Stream rate equals salary divided by duration - the math is trivial; zero privacy improvement. Vesting.so publishes cliff dates and amounts; markets dump ahead of every unlock. STRK20 inherits the channel + viewing-key model: the schedule is on-chain and enforced, but its parameters are encrypted to the parties and the auditing entity.

Why this isn't Deel-style centralized payroll

Centralized payroll services solve privacy by being the centralized intermediary. They see everything, hold the relationship, can be subpoenaed, hacked, or shut down. STRK20 splits the trust: cryptographic on the rails, cryptographic on the compliance disclosure. No intermediary holds the data.