Premium creator payments · Starknet Mainnet

ZEEROSTREAM

ZeeroStream gives paid creator pages a private checkout lane. Subscribers can send a STRK20 payment with an encrypted memo receipt while wallet keys, notes, and proofs stay inside their own wallet.

View creator pageUnderstand privacyWallet-signed · Mainnet pool V2 · no custody

Featured creator page

Zero Studio

Private drops, paid replies, encrypted payment memos, and receipts a creator can read locally.

Subscribe privately

Latest posts

Subscriber feed

3 locked drops

Creator checkout

Support without exposing the relationship.

10 STRKprivate payment
  • Encrypted memo receipt
  • Creator-local inbox demo
  • Receipt hash for verification
Start checkout

Creator inbox

Memo receipt ready

Only the intended creator key can decrypt the attached note. ZeeroStream stores ciphertext and payment binding only.

Payment hashverified
Memo contentencrypted

1 · Shield

Enter the pool.

The deposit edge is public and screened. Your wallet creates the private note.

2 · Wait

Let the note mature.

New notes generally need about ten blocks before they can be spent.

3 · Pay

Transfer privately.

The wallet discovers notes, proves the transfer, signs, and submits without exposing private state to ZeeroStream.

Live Mainnet MVP

One private payment flow. Three verifiable pool receipts.

Wallet connection proves account control. A resolved .stark name is a public recipient alias—not a private-pool identity claim.

SN_MAIN · POOL V2
  1. Creator wallet: shield STRK to register and create receipt 1.
  2. Client wallet: shield enough STRK for the payment and create receipt 2.
  3. Client wallet: pay the registered creator privately and create receipt 3.

Two-user demo route

Hand off a public recipient. Keep private state in each wallet.

Switch wallets only at the marked handoff. ZeeroStream never transfers keys, notes, balances, or proofs between participants.

  1. 1ConnectCheck capability and connect the active Mainnet wallet.
  2. 2PrepareResolve public fields, read the fee, and dry-run privately.
  3. 3Sign & verifyApprove in the wallet, then verify the public pool receipt.

Creator handoff

Share a recipient, never a secret.

After shielding, give the client your public .stark alias or address.

Client preflight

One exact review before signing.

Wallet
Not connected
Recipient
Resolved during payment dry run
Notes
Maturity is checked by the wallet; note data stays private.
Next
Prepare an exact action.

Step 01

Connect safely

Capability checks do not request private balances or note data.

0 installed wallet(s) discovered

Step 02

Prepare privately

Your wallet may ask twice: first for ERC-20 approval, then for the pool deposit. Only the pool deposit is qualifying evidence.

Step 03

Review and sign

Network
Starknet Mainnet
Pool
0x040337b1af3c663e86e333bab5a4b28da8d4652a15a69beee2b677776ffe812a
Action
Shield STRK
Token
STRK · 0x04718f5a0fc34cc1af16a1cdee98ffb20c31f5cd61d6ab07201858f4287c938d
Amount
— STRK
Pool fee
Available after dry run

Check a wallet, connect on Mainnet, then prepare one exact action.

Encrypted memo receipt

Attach a private note without changing the pool transaction.

The memo is encrypted before signing and bound to the returned payment hash after submission. The stored receipt contains ciphertext, a commitment, a replay nullifier, and a local recipient label.

Demo keys

Session-only keys model creator import/decrypt. They are not wallet viewing keys.

Creator inbox demo

Optional memo receipts are encrypted locally and stored only as ciphertext.

Verified Mainnet evidence

Three public receipts. One private payment relationship.

Each committed hash was checked through two independent RPC providers for accepted finality, successful execution, and a reviewed-pool event.

3 / 3 receipts verified
  1. 1
    Creator shieldCreator registration and public pool-entry receipt.View on Voyager 0x016301b8…337f3217
  2. 2
    Client shieldClient pool-entry receipt before the private payment.View on Voyager 0x03334787…31b59f29
  3. 3
    Private paymentSuccessful pool payment receipt; recipient and amount remain private in the pool.View on Voyager 0x7f11f4e6…8757aca0

Wallet-only boundary: signing keys, viewing keys, notes, witnesses, proofs, and private balances never enter ZeeroStream. Deposits and withdrawals are public; private transfers hide pool-side sender, recipient, and amount, while timing remains observable.

Explicit privacy boundary

Private where it matters. Honest at the edges.

Hidden inside the pool: sender, recipient, token amount, and which private notes were spent.

Public: deposits, withdrawals, transaction timing, registration events, and the fact that the pool was used.

Never enters ZeeroStream: signing keys, viewing keys, seed phrases, private notes, proof witnesses, or private balances without separate consent.

After the sprint

Advanced infrastructure remains preserved—not advertised as live.

Reviewed escrow, subscriptions, Passport policies, custom ZK settlement, encrypted-message transport, tier gates, and a real Oyster workload with verified Nitro attestation remain post-hackathon work. TEE evidence will stay optional and non-authoritative.