Supported Assets and Networks

INVSBL operates directly on existing blockchains without changing how assets are defined, issued, or settled.

The protocol introduces confidentiality at the transaction layer while preserving the native asset standards and execution environments of each supported network.

Assets entering and exiting INVSBL remain fully compatible with their native ecosystems.

---

What INVSBL Does Not Introduce

INVSBL does not rely on:

• Wrapped tokens

• Synthetic assets

• Modified token standards

• Derivative or intermediary representations

Assets remain native from initiation through settlement.

---

1. Solana

1.1 Supported Assets

INVSBL supports private transfers for all SPL tokens on Solana, including tokens used for:

• Payments

• Treasury operations

• Incentives

• Application-level flows

Confidential execution applies uniformly, regardless of token type or use case.

1.2 Asset Compatibility

Assets routed through INVSBL remain standard SPL tokens throughout execution.

From the Solana network’s perspective:

• Transactions remain valid

• Token standards are unchanged

• Ecosystem tools continue to function normally

• No special handling is required

---

2. EVM Networks (Base & Ethereum)

2.1 Supported Assets

INVSBL supports private transfers for ERC-20 tokens on EVM-compatible networks, including Base and Ethereum.

2.2 Asset Compatibility

Assets remain native ERC-20 tokens at all stages.

INVSBL does not:

• Wrap or transform tokens

• Alter contract semantics

• Introduce parallel asset representations

Settlement occurs using standard EVM execution rules.

---

3. Asset Flow

3.1 How Assets Move Through INVSBL

1. User initiates private transfer
   ↓
2. Assets enter INVSBL privacy layer (remain native)
   ↓
3. Transaction is validated with zero-knowledge proofs
   ↓
4. Assets exit privacy layer (still native)
   ↓
5. Recipient receives standard native assets

At no point in this process are assets:

• Wrapped or modified

• Converted to synthetic representations

• Changed from their native format

• Made incompatible with existing tools

---

4. Ecosystem Compatibility

4.1 Both Networks Maintain

Compatibility	Details
Native asset format	Assets remain in their original standard throughout
Ecosystem tools	Full compatibility with wallets, explorers, and infrastructure
Token standards	No deviation from SPL (Solana) or native ERC-20 standards
Settlement guarantees	Inherit security and finality from underlying blockchain

4.2 What This Means for Users

Users can:

• ✓ Use existing wallets

• ✓ Interact with standard blockchain tools

• ✓ Maintain compatibility with accounting systems

• ✓ Integrate with existing infrastructure

• ✓ Trust the same security mechanisms as the underlying network