UTXOSUITE — home
VIGI WALLET / SOVEREIGN SELF-CUSTODY

The native VigiChain wallet — and a complete multichain self-custody command center.

Vigi Wallet combines native VigiChain post-quantum identity/signing with EVM networks including Cronos, native Bitcoin SegWit and Solana. The same product architecture also includes encrypted multi-wallet vaults, SafeSign/Aegis protection, swaps, dApps, NFTs, activity, recovery, air-gap signing, device sync, VigiBank Connect and the gated VigiStable surface.

SOURCE IMPLEMENTED / EXTERNAL AUDIT + STORE RELEASE PENDING
VIGI WALLET / SELF-CUSTODY SIGNERA phone beside a small hardware signer, joined by a cable.
THE WALLET ITSELF

Six screens from the build, not a mockup.

Vigi Wallet is the wallet shown inside UTXO Suite: it owns the keys, the vault and the signer. These are its own screens, captured from the source build.

Every chain in one view: native VigiChain, EVM, Bitcoin and Solana, with the vault and network chosen explicitly.
Portfolio

Every chain in one view: native VigiChain, EVM, Bitcoin and Solana, with the vault and network chosen explicitly.

A native transfer states what it spends: spendable UTXOs in, change back, fee visible before anything is signed.
Send · native VIGI

A native transfer states what it spends: spendable UTXOs in, change back, fee visible before anything is signed.

One address per network, with the node's sync state — block height and peers — shown next to it.
Receive

One address per network, with the node's sync state — block height and peers — shown next to it.

A swap route is reviewed as a route: what you pay, what you receive, and a confirmation step before signing.
Swap

A swap route is reviewed as a route: what you pay, what you receive, and a confirmation step before signing.

The SafeSign transaction firewall, auto-lock and theme live in the wallet's own settings, not in a remote profile.
Security settings

The SafeSign transaction firewall, auto-lock and theme live in the wallet's own settings, not in a remote profile.

A read-only view of external accounts, connected by explicit consent. Bank credentials never enter the wallet.
VigiBank

A read-only view of external accounts, connected by explicit consent. Bank credentials never enter the wallet.

Captured from the Vigi Wallet source build with its demo fixture. Balances, accounts and network are sample data, not a real account, and no public store release exists yet.

CURRENT SURFACE

What exists in the current product surface.

The Vigi Wallet repository reports passing TypeScript typecheck, production extension build, Capacitor mobile build/sync and 102 unit tests, with live-node tests opt-in. The Android native APK was not assembled in the isolated environment, and external security audit plus store review remain release gates.

01

Native VigiChain

Native vigi1/tvigi1/dvigi1 accounts, native UTXO transaction building/simulation/broadcast workflow and post-quantum signing identity aligned with the Vigi node RPC.

02

Multichain Vault

Encrypted multi-wallet vaults and multiple accounts per wallet across VigiChain, EVM including Cronos, Bitcoin native SegWit and Solana.

03

Aegis + SafeSign

Local-first vault protection, passkey-assisted unlock, Shamir recovery, anomaly detection, air-gap signing and SafeSign review. Policy and simulation layers are integrated by capability and must preserve their documented maturity.

04

VigiBank Connect

Consent-based read-only bank monitoring through a provider gateway. Bank passwords, PINs and TAN codes never enter Vigi Wallet; bank data is isolated from the keyring and signing core.

05

VigiStable

A dedicated stable-value surface with an explicit registry state. Conversion stays locked until wrapped-asset contracts, reserves and live bridge/router paths are deployed and independently verified.

06

Extension + Mobile

One shared product codebase currently builds the browser extension and Capacitor mobile web bundle, with synchronized Android and iOS projects. Native Android APK assembly and store distribution remain release gates outside the isolated build environment.

TWO OPINIONS, ONE OUTCOME

The most restrictive valid verdict wins.

Vigi Wallet keeps its own Aegis heuristics. UTXO Security Core adds a second, deterministic opinion. Neither layer can talk the other one down — try every combination.

Vigi Wallet · Aegis

UTXO Security Core

BLOCK
Combined verdict

The signer cannot be reached under this verdict.

  • UTXO SafeSign decision: BLOCK.

This is the published combination contract, not a live wallet session. Aegis evidence marked critical is never dropped because Security Core returned ALLOW.

THE PATH OF A SIGNATURE

Understand before you sign.

Every irreversible authorization travels the same path. UTXO Suite makes each step of that path readable — and stops at the one step it must never own: the signature itself.

  1. REQUEST

    A wallet, a dApp or an agent asks for a signature. Nothing is trusted yet.

    UTXO Suite
  2. NORMALIZE

    The request is decoded into one canonical shape: method, chain, origin, parameters.

    UTXO Suite
  3. INTENT

    What the request actually does, in plain terms: a transfer, an approval, a delegation, a permit.

    UTXO Suite
  4. CONTEXT · SIMULATION

    Counterparty, origin and expected outcome. Simulation is evidence, never an oracle.

    UTXO Suite
  5. RISK

    Weighted signals: unlimited authority, unknown code, fresh contracts, mismatched destinations.

    UTXO Suite
  6. POLICY

    Your rules, applied deterministically to that evidence — a policy, not a feeling.

    UTXO Suite
  7. DECISION

    ALLOW, WARN, REVIEW or BLOCK. A BLOCK is never softened by another layer.

    UTXO Suite
  8. AUTHORIZATION

    You authorize explicitly. Even an ALLOW is not a signature.

    You
  9. PAYLOAD INTEGRITY

    The bytes about to be signed are compared to the exact bytes you reviewed.

    UTXO Suite
  10. SIGNER

    The isolated signer runs inside the wallet. UTXO Suite never holds a key or a seed.

    Vigi Wallet
  11. BROADCAST

    Optional. A signed transaction is not automatically a broadcast one.

    Vigi Wallet
  12. VERIFICATION

    What actually happened on-chain is checked against what you were promised.

    UTXO Suite
ALLOWNothing contradicts the request. It still needs your explicit authorization.
WARNSomething deserves attention before you continue.
REVIEWThe request cannot be understood without you looking closer.
BLOCKThe request must not reach a signer under the current policy.

No decision is a signature. Authorization is always yours.

Unknown never becomes safe. Missing evidence stays missing.

APP AVAILABILITY

Real source exists. Public release still has gates.

UTXO Suite shows implementation status instead of a fake download. Vigi Wallet has browser-extension and mobile source/build surfaces, but this repository found no published GitHub Release for the wallet and the native Android APK is not yet a validated public artifact.

01

Browser Extension

SOURCE + PRODUCTION BUILD VALIDATED

Chrome/Edge/Brave extension architecture exists in the Vigi Wallet repository; external security audit and store review remain release gates.

02

Android

SOURCE + CAPACITOR SYNC VALIDATED

Android project exists and mobile web build/sync is reported passing. Native Gradle APK assembly/signing/device validation is still required before public download.

03

iOS

SOURCE + CAPACITOR SYNC VALIDATED

iOS project exists and Capacitor sync is reported passing. Xcode archive, signing and App Store validation remain external release gates.

04

Desktop

MIGRATION / RELEASE GATE

The product direction targets Tauri 2 desktop. Do not present a final Vigi Wallet desktop installer until the migration and signed artifact are actually validated.

Security boundary

Vigi Wallet

Vigi Wallet is self-custodial. Keys and seeds remain inside the wallet core; VigiBank is read-only and isolated from the keyring; VigiStable conversion is blocked until external contracts/reserves/routes are verified. UTXO Suite presents and integrates Vigi Wallet — it does not replace it with a separate UTXO Wallet product.

Next integration boundary

SafeSign

UTXO Suite's SafeSign, Security Core, Guard, Permissions, RPC evidence and Bitcoin/PSBT modules should integrate into Vigi Wallet through explicit contracts. Product identity, key custody and app delivery remain owned by Vigi Wallet.

VIGI WALLET / SELF-CUSTODY BOUNDARY

Vigi Wallet owns the keys. UTXO Suite secures the decision path.

Vigi Wallet is the canonical wallet product: native VigiChain plus EVM/Cronos, Bitcoin and Solana self-custody. SafeSign and Security Core analyze the exact final request, but private keys remain inside Vigi Wallet's vault/signing boundary.

01INTENT

User or dApp creates a send, approval, typed-data, swap, native Vigi or PSBT intent.

02FINAL PAYLOAD

Vigi Wallet builds the exact transaction/signature payload that could reach its signer.

03SAFESIGN / AEGIS

UTXO Suite security primitives decode authority, evidence, simulation and policy without receiving private keys.

04USER AUTHORIZATION

The user explicitly approves the exact reviewed payload; mutation invalidates the review.

05VIGI WALLET SIGNER

Vigi Wallet reauthenticates and signs inside its isolated vault/native signing boundary.

06BROADCAST / VERIFY

The wallet submits signed bytes through the relevant network path and records execution evidence.

COMPONENT BOUNDARIES

Vigi Wallet + UTXO Suite

Source implementation exists for extension/mobile architecture, native VigiChain, multichain vaults and protected flows. External audit, store review and final signed production artifacts remain release gates.

COMPONENT
READS
WRITES
FORBIDDEN
UTXO Security Core
request + supplied evidence
analysis + reviewed payload hash
seed / private key / silent signing
Vigi Wallet Vault
encrypted wallet state + local auth factors
unlocked signing capability
remote custody / page-world key access
Vigi Wallet Signer
exact authorized payload + isolated key material
signature / signed transaction
payload mutation / auto-sign
VigiChain RPC
unsigned/signed native transaction bytes + public chain state
simulation / acceptance / receipt evidence
wallet custody / signing for user
VigiBank
provider consent + read-only bank data
bank-data snapshots
wallet keyring / seed / signing
NATIVE VIGICHAIN PATH

Build → simulate → review → sign → broadcast.

Vigi RPC builds unsigned native UTXO transactions and broadcasts only already-signed bytes. The wallet signing boundary owns the key operation.

REQUEST / INPUT
vigi_getUtxos(address)
vigi_estimateFee(...)
vigi_buildTransaction(...)
vigi_simulateTransaction(...)
AUTHORIZED RESULT
SafeSign decision + reviewed payload
→ explicit user authorization
→ Vigi Wallet native signer
→ signed bytes
→ vigi_broadcastTransaction(...)