Blizkperseblizkperse

Organizer deposits. Payee claims.Books stay in the app.

Stablecoin grants and bounties. The organizer keeps the payroll. The chain sees a deposit into a pool, and a claim. Live on Monad, Celo, and Robinhood Chain.

3chains live
100%on-chain
0network fee for claims
OSSopen source

What the explorer sees

Same payout. One is a public transfer to each member. The other is a deposit into a pool, and a claim.

public ledger
transfer(organizer to member A)
amount: 8,500.00 USDC
transfer(organizer to member B)
amount: 12,200.00 USDC
transfer(organizer to member C)
amount: 6,750.00 USDC
shielded pool
deposit(organizer to pool)
token transfer: the total, plus the fee
claim(pool to member)
private bucket: that bucket size
standard note: the leftover amount
payroll list
stays in the app

The explorer sees the deposit and each claim. It does not see the payroll list.

The blockchain made money transparent.
Too transparent.

A direct on-chain transfer publishes the payer, the recipient, and the amount. Blizkperse is the last mile: the organizer deposits into a pool, and each payee claims. The payroll stays in the app. A private bucket exit still shows that bucket size. A standard note shows its amount.

How it works

01

Create a payout

Pick recipients and set amounts. No CSV files, no middleware. Just a wallet and a list.

02

Deposit with ZK proof

Funds enter a shielded pool. The proof commits each note. A private bucket later withdraws by bucket id, so many exits of that size look the same. A standard note shows its amount.

03

Recipients claim

Recipients sign in with email or social login. No existing wallet needed. Funds arrive in seconds.

Under the hood

Zero-knowledge privacy

Noir circuits generate proofs client-side. Amounts are committed as Poseidon2 hashes. Nobody, not even the contract, sees plaintext values.

Non-custodial by design

Funds sit in an auditable smart contract, not a multisig or a mixer. Only verified recipients can withdraw their share.

Three chains live

Same shielded pools and proofs on Monad, Celo, and Robinhood Chain.

Zero friction onboarding

Recipients sign in with email or social login and get an embedded wallet instantly. No MetaMask. No seed phrases.

Real use cases

The organizer keeps the payroll. Payees claim from the pool.

Grants & bounties

An organizer deposits into a pool. Each payee claims their note. The payroll list stays in the app. The explorer shows the claim.

Built on

NoirZK circuits
MonadEVM L1
CeloEVM L1
RobinhoodEVM chain

What's next

Building in public

Blizkperse is live today. Private buckets are on Monad, Celo, and Robinhood. What follows is still ahead.

1
Now
2
Next
3
Later
Live on mainnet

Private payouts

ZK-shielded on Monad, Celo & Robinhood

Multi-token pools

COPm, USDT, USDC, USDG. One pool per token

Private buckets

Private buckets first. Leftover stays a standard note

On-chain proofs

Noir circuits + Honk verifiers

Social login

Email or Google, instant wallet

Sponsored claims

The recipient does not pay the network fee

In development

Hardened core

  • Security audit
  • Stronger root trust model
  • Formal verification

Treasury access

  • Safe multisig
  • Multi-approver flows
  • Org spending policies

Open API

  • REST endpoints
  • Webhooks
  • Keys for agents & partners
On the horizon

Identity layer

Pluggable KYC with Self Protocol & vlayer for LATAM

FHE research

Exploring fully homomorphic encryption for enhanced confidentiality

More networks

Expand shielded payouts across additional EVM ecosystems

Claimable disbursement

Ready to pay the last mile?

The organizer deposits. Payees claim. The payroll stays in the app.
No setup fees. No KYC for recipients.