Skip to main content

Understanding Obscura

Obscura is built on the Zano blockchain using its native Confidential Asset protocol. This ensures every NFT created through Obscura is inherently private by design.

Key Privacy Features
  • Ownership is not visible on-chain
  • Transfers are hidden from public view
  • No external party can determine which wallet holds which token

How It Works​

🔐 Confidential Assets​

Each Obscura NFT is a native Confidential Asset on the Zano blockchain. The metadata is embedded into the asset itself and stored securely using IPFS, avoiding centralized storage systems.

Traditional NFT:          Obscura NFT:
├─ Public ownership  →    ├─ Hidden ownership ✓
├─ Visible transfers →    ├─ Private transfers ✓  
├─ On-chain metadata →    ├─ IPFS storage ✓
└─ Centralized APIs  →    └─ No APIs needed ✓

🛡️ Privacy Technologies​

All transfers and balances are shielded by default through Zano's privacy technologies:

  • Stealth Addresses - Hide recipient wallet addresses
  • Confidential Amounts - Obscure transaction amounts
  • Ring Signatures - Make transactions untraceable

⚙️ No Smart Contracts​

Technical Advantage

There are no smart contracts or centralized APIs involved. Instead, Obscura uses native Zano wallet functions.

Obscura leverages built-in Zano features for secure, private verification:

  • Alias-based messaging - Communicate securely between wallets
  • View key sharing - Selectively prove ownership without exposing balances
  • Asset signature requests - Verify NFT ownership privately

These features allow creators to confirm whether someone holds a specific NFT without ever needing to see their wallet balance or identity.

Why Privacy Matters​

Obscura provides the foundation for a new kind of NFT experience where digital ownership, distribution, and interaction are:

  • ✅ Fully private by default
  • ✅ User-controlled at all times
  • ✅ Censorship-resistant and permissionless
  • ✅ Decentralized without reliance on external services

More specific use cases are detailed in the Use Cases section.