Starknet mainnet · STRK20

Payroll details stay private.
Accountability does not.

Distribute a three-to-five-person payroll through STRK20 without publishing individual recipients or allocations, while committing the aggregate on Starknet.

Open live product

Submission build · feature frozen

Private payments. Public accountability.

Register aggregate runs on Starknet, verify their event-backed state, then deliver AES-GCM receipts whose keys stay in private claim-link fragments.

The difference

Accountability without a salary leaderboard.

Judges and public observers see a compact aggregate record. Each recipient sees only their voluntarily disclosed line.

PUBLIC

August payroll

Token
STRK
Total
Committed
Recipients
3
Merkle root
0x…
Individual rows
Hidden
RECIPIENT

My receipt

My amount
Disclosed to me
Inclusion
✓ Valid
Payer signature
✓ Valid
Other recipients
Hidden
Other amounts
Hidden

End to end

Commit → batch → attest → verify

  1. 01Build locally

    CSV rows, salts, and proofs stay in the browser.

  2. 02Pay privately

    One simulated STRK20 action batch for 3–5 recipients.

  3. 03Finalize publicly

    The registry binds aggregate commitments to accepted pool evidence.

  4. 04Disclose selectively

    Signed receipts and audit packages verify only what is shared.

Wallet

Not connected

Network guard

Required: SN_MAIN

Privacy capability

Not checked

Shielded balance

—

Connect a privacy wallet

Connection only continues after the wallet reports Starknet mainnet. Ready X is the explicitly supported wallet for this milestone.

Scanning for Starknet wallets…

Tiny mainnet shield

Deposit public STRK into the private pool. The wallet owns note discovery and proving; this app receives no viewing key.

Safety cap: 1 STRK. Recommended first proof: 0.001 STRK. Gas also applies.

Tiny private transfer

Send one technical STRK20 payment only after the recipient independently passes the activation check. There is no public-transfer fallback.

Keep the address mapping private. The sender cannot query another account's registration through Wallet API 0.10.3.
Technical-payment cap: 0.1 STRK. The privacy action fee and gas are additional; review the complete Ready X prompt before approving.

Recipient gate

Activate and verify three demo recipients first.

Each recipient opens Ready X, enables its privacy flow, then connects to ShadowLedger for a mainnet capability and private-balance check.

Open recipient activation
  • Recipient ARequired for this transfer
  • Recipient BPrepare for payroll batch
  • Recipient CPrepare for payroll batch
Registration and every privacy action are mainnet operations. Review all fees and gas in Ready X; never expose a recovery or viewing key.