Privacy Model
INVSBL is designed around fixed protocol constraints that define how transactions behave under all conditions. These constraints are enforced cryptographically and do not depend on configuration, trusted parties, or user behavior.
1. No Identity Leakage
Transaction execution must not expose identity-linked data.
No reusable sender or receiver identifiers
Address reuse is prevented at the protocol level
Transactions cannot be clustered or associated with wallets
This holds against block explorers, analytics platforms, infrastructure providers, and large-scale observers.
2. No Historical Reconstruction
Transaction activity must not become linkable over time.
Transactions do not form linkable graphs
Balance changes cannot be tracked across time
Past and future transactions remain isolated
Time, volume, repeated use, or improved analytics do not enable retrospective linkage.
3. No Trusted Intermediaries
Objective: Confidentiality must not rely on trusted operators.
No party can observe identities, balances, relationships, or history
This includes infrastructure providers and the protocol operator
Transaction validity is verified using zero-knowledge proofs without revealing transaction data.
4. Native Asset Compatibility
Assets remain standard and native.
No wrapped, synthetic, or modified assets
Tokens retain their original behavior and settlement properties
Confidentiality is achieved through protocol design, not asset transformation.
5. Operational Usability
Confidential transactions must be practical to use.
Works for individuals, organizations, developers, and operators
Supports automation and programmatic access
No manual coordination or cryptographic expertise required
Last updated