Vaults, wallets & accounts

1. Vault profiles: one identity, many pockets

Every actor on ProteonX is modelled as a Vault Profile. Think of it as a single legal/operational identity:

• Display name and basic contact details
• Compliance status and access permissions
• Role-based access depending on the actor and permitted services

The public wallet UI is simply a clean view on top of this: “your ProteonX account” = one vault profile, not dozens of random blockchain addresses.

2. Vault pockets: assets & rails inside a vault

Inside each vault profile, ProteonX tracks multiple Vault Pockets. Each pocket is:

• a specific asset code (PXN, INV, USDT, EUR, USD…)
• a specific rail (PXN core, IW internal, bank, card, external chain, etc.)
• an on-ledger balance for that combination

Publicly, the important point is simple: one vault can group multiple asset and settlement channels in a single interface.

• Digital assets
• Fiat accounts
• Cards
• External rails
• Other approved partner channels

For a normal member, a single vault profile might expose pockets like:

• PXN Wallet — PXN on the ProteonX rail
• INV Wallet — INV issued by Invescorp World
• USDT Wallet — resident stablecoin balance
• EUR Bank (SEPA) — linked EUR bank account
• USD Bank (SWIFT) — linked USD bank account
• Visa Card (EUR / USD) — card rails mapped to the vault

The UI shows this as “one wallet with many balances”. Under the hood, it is a single vault profile with multiple typed pockets.

3. No private keys in wallets

ProteonX wallets are not key stores. They never hold, export or see private keys.

• All signing keys live in external, hardened security vaults.
• The core only sees signed envelopes and evidence, never raw keys.
• Wallet actions (send, receive, OTC, convert, settle) are requests that must be validated and co-signed by multiple vaults under Guardian policy.

Result: if someone compromises a user device, they do not get a raw private key to drain assets. They at best compromise a front-end, while the real signing power remains in segregated vaults.

4. What the user actually sees

The public wallet interface is a clean projection of vaults & pockets into normal human language:

• “Wallet” → your vault profile
• “Balance line” → one vault pocket
• “Send / receive / pay” → a sequence of core operations that adjust balances across pockets and rails

For example, a single user screen might show:

• PXN – 12,500.00
• INV – 430.00
• USDT – 5,000.00
• EUR Bank (SEPA) – linked account
• USD Bank (SWIFT) – linked account
• Visa Card (EUR / USD) – linked cards

Behind that, ProteonX keeps every movement deterministic, auditable and aligned with journal operations and vault evidence.

5. External chains & system pools (high level)

For public users, ProteonX focuses on their balances: PXN, INV, stables, and linked fiat rails. Some additional pockets exist only for system/institutional vaults and are not shown in user wallets.

• External pools – system vaults hold BTC, ETH, XLM, SOL and other approved external assets in dedicated pool pockets.
• When a user pays with such an asset, the system records the inflow to the pool and transfers existing PXN from the treasury vault into the user’s PXN pocket.
• The user sees “I sent BTC, I received PXN”. The underlying BTC sits in ProteonX / IW system pools; it does not appear as a retail wallet balance.

This keeps the user experience simple, while allowing IW/ProteonX to manage external asset pools and liquidity behind the scenes.