CipherBillCipherBill
CipherBillPrivate commerce on Starknet

Your money,
your business.

Invoice, shield and settle on Starknet. A payment shouldn't give the world a map of your business.

Built for the STRK20 Private Sprint. Mainnet-targeted prototype.
CipherBillCipherBillNot connected

A little more discretion.

Shielded payments start with a compatible wallet.

Shielded STRK balance--Connect a wallet in the workspace to load your balance.
Recipient address
0x...
Amount
Amount in STRK
Asset
STRK
Memo (optional)
Invoice reference
Both parties must be registered with STRK20. Nothing moves until your wallet signs.
Illustrative preview / no real balance, invoice or transaction
Wallet adapter Built

Discovery and capability checks implemented.

Payment UI Built

Shield, balance and private transfer surfaces.

Mainnet acceptance

Manual wallet testing and transaction evidence pending.

Selective receipts Built

Metadata exports implemented. Verified settlement evidence pending.

Built for how you actually get paid.

Less exposure inside the pool. Clear boundaries outside it.
A working interface, not a completed privacy guarantee.

01

Shield your STRK.

Move public STRK into a shielded balance. Deposit address and amount remain public. Approval and deposit use separate wallet prompts.

02

Settle privately.

Pay a registered STRK20 recipient through a compatible wallet. In-pool details are designed to stay hidden. Withdrawals remain public.

03

Share less evidence.

Choose which application receipt fields to disclose. Encrypt a bundle for an auditor. These exports are not ZK proofs or protocol viewing keys.

Verified mainnet evidence pending
Privacy / honest boundaries

Private inside.
Observable at the edges.

The STRK20 design model, not a claim of completed CipherBill mainnet verification.

Designed to stay hidden

  • In-pool sender, recipient, token, and amount
  • Which encrypted notes were spent and their linkage
  • Ordinary encrypted note values and undisclosed receipt fields

Public or observable

  • Shielding deposits and withdrawals, including public addresses and amounts
  • Timing, fees, and published nullifiers (unlinkable without a viewing key)
  • Open-note amounts, app metadata, and correlation risks from distinctive activity

Anyone holding a standard invoice URL can read its fields. Never put private keys, seed phrases, viewing keys, notes or wallet history in invoice fields.

Evidence / inspect the implementation

A working interface.
Not a finished promise.

Built by Yeluru Nitish. Next.js, TypeScript and the Starknet Wallet API.

Implementation

Inspect the source.

Wallet action adapter, guarded submission and local invoice tooling. A delayed confirmation preserves the submitted hash.

Open the repository ↗
Mainnet acceptance

Evidence pending.

No verified transactions or demo video are listed in the current repository manifest. Interface code is not proof of successful settlement.

Awaiting manually verified evidence
Selective disclosure

Application metadata.

Receipt selectors and encrypted bundles are implemented. An auditor must independently verify any disclosed settlement hash.

Open the auditor viewer →
The workspace

One focused flow.
Room to inspect the rest.

Private payments plus all 20 existing console modules. Wallet-integrated prototypes and local proof tools, not 20 verified financial services.

Private paymentWallet-integrated prototype / mainnet evidence pending
Private transfer

Pay without publishing your financial graph.

Shielded STRK balance--

Shielding requires two wallet prompts: ERC-20 approval, then the private deposit.

Shielded balance unavailable until a wallet is connected.

Private transfers require both sender and recipient to be registered with STRK20. Only the recipient can register their wallet.

Connect a privacy-enabled Starknet wallet to begin.

Unshield to a public address

Warning: unshielding makes the recipient, token, amount and timing public on Starknet.

No public withdrawal submitted.