Enter without connecting a wallet
A tiny shielded transaction carrying a private memo code proves control of a supported Zcash address. We encrypt the address and give you a random alias; public pages never show the account relationship.
Mechanics, without the fog
ZICA combines guarded image generation, shielded ZEC payments, immutable artifacts, and a signed ownership registry. Here is exactly where trust sits.
A tiny shielded transaction carrying a private memo code proves control of a supported Zcash address. We encrypt the address and give you a random alias; public pages never show the account relationship.
A unique payment request includes the exact 0.05 ZEC amount, receiver, memo, expiry, and required confirmations. The interface cannot mark it paid. A scanner sees the payment, waits through confirmation, then issues the mint entitlement.
Your prompt is screened, normalized into a structured trait intent, and checked against immutable character rules. Unsafe requests are rejected without exposing classifier internals. The raw prompt is never analytics data.
The image model receives the canonical character reference plus the approved instruction. It generates one complete image—not code-composited layers. Identity, safety, and visual checks gate every candidate you can see.
You can select any approved prior candidate. Finalization pins image and metadata, verifies their content addresses, writes a signed registry event, and publishes the collection record.
Ownership today
The ZICA protocol database enforces title and emits signed, hash-linked events. Shielded payment is on Zcash; NFT ownership is not a native transferable Zcash asset today. Native ZSA migration can come later without pretending it already exists.
Verify the modelMarketplace today
A listing is reserved before payment details appear. The buyer sends irreversible ZEC directly to the seller. ZICA never holds the funds. Registry title moves only when the seller confirms the exact payment and memo in their own wallet.
Explore market