Z

Support Zero Studio privately

Pay with STRK20, explore encrypted notes, and inspect public receipt evidence while your wallet controls signing and private notes.

Start private checkout View receipt room

Local preview feedSeeded public posts plus browser-local updates

Public titlePublic post

Public posts only. Encrypted notes belong in Messages.

ZeeroAgent access brain

Private creator relationships without a public social graph.

ZeeroAgent models who can request, enter, lose, or receive creator access. ZeeroStream uses that as a product layer around receipt-bound access, while wallets keep private state, notes, and proofs.

Accepted: 1
Blocked: 1
Delivered: 1

Request

Supporter asks for Studio access

Access request exists; wallet identity stays hidden.

subscriber-8f2 -> zero-studio

Creator accepts the supporter

Accepted audience edge can unlock the creator room.

zero-studio -> subscriber-8f2

Block

Creator blocks one viewer

Blocked viewers are excluded before feed delivery.

zero-studio -> subscriber-c70

Permit

Receipt-bound Studio permission

Tier, audience, expiry, and receipt binding are enough.

zero-studio -> studio-feed

Deliver

Private drop delivered

Delivery follows the accepted edge, not a public wallet scan.

studio-feed -> subscriber-8f2

Live read-only demo using synthetic relationships from ZeeroAgentMVP z-social graph. Decisions illustrate access policy; they do not authenticate viewers, verify receipt ownership, or grant protected access.

wallet addresswallet historyprivate notesmemo plaintextproof witnessraw graph signatures

Open live read-only agent endpoint

Private creator receipt room

Public receipt evidence. Minimum-disclosure access demo.

Judges can inspect the public evidence pack, while the product demo shows the creator workflow: verified receipts, ciphertext-only memo handling, and minimum-disclosure access.

Receipt inspector

Private payment

Voyager

Status: verified-mainnet
Hash: 0x7f11f4e677a5d6d9cf939d652f5c471e081742bc6aec152491dc56e8757aca0
Visible: transaction hash, pool event, finality, timing
Hidden: sender, recipient, amount, spent notes, memo plaintext

Selective access pass

Reveal the right fact, not the wallet.

Tier to disclose

Demo only: a public receipt and self-selected tier do not prove payment ownership or grant protected access.

Select a receipt and generate a local access pass.

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

Creator wallet: shield STRK to register and create receipt 1.
Client wallet: shield enough STRK for the payment and create receipt 2.
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. Z never transfers keys, notes, balances, or proofs between participants.

1ConnectCheck capability and connect the active Mainnet wallet.
2PrepareResolve public fields, read the fee, and dry-run privately.
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

ActionAmount in STRK

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

I reviewed the network, pool, action, token, amount, recipient, and live fee.

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

Live app Demo video STRK20 manifest

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

Submission pack

Ready to score, with conservative claims.

The submitted artifact is the non-custodial checkout, encrypted memo receipt demo, selective-disclosure demo, public MP4, and three reviewed STRK20 Mainnet pool receipts.

Verifier result: READY_TO_SCORE
Wallet boundary: User wallet signs; Z keeps no keys, notes, witnesses, or balances.
Not claimed: No live subscriptions, helper contract mail storage, autonomous billing, or production creator analytics.

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