The Lord bless thee and keep thee; the Lord make his face shine upon thee, and be gracious unto thee.
HOM3 // vault
LOCAL :: qwen3:4b CLOUD :: qwen3-coder:480b-cloud RAM 92% BTC --- VAULT $--- ● LIVE 🎙 listening: off

VAULT · WATCH-ONLY HOLDINGS i

this field cannot accept a private key
Public addresses across chains; balances via known public endpoints (Bitcoin reads via the Neutrino watch-only client). Watch-only by construction — the input physically rejects any private key or seed phrase. Keep secrets cold, off this machine.
⛓ Bitcoin · Neutrino watch-only i checking…
Trust-minimized, watch-only — holds no keys. Add a Bitcoin address or xpub below to track it.
Reads the Bitcoin chain by peering with nodes and verifying locally (PoW headers + filter commitments + cross-peer agreement) — no block-explorer to trust, no 600GB chain (headers only, ~65MB). Filters are matched on this machine, so peers never learn which addresses you watch.
Add a WATCH-ONLY public address or xpub — never a private key or seed phrase. i
Supported: Bitcoin (1.../3.../bc1.../xpub, read via Neutrino above), Ethereum, and the EVM L2s (Polygon, Arbitrum, Base, Optimism — one 0x address checked across all), plus Solana. Secrets stay cold, off this machine — the field structurally rejects a private key or seed.
Sovereign by default: this viewer stores + displays your addresses as your own ledger and queries nothing — zero egress. Fetching live balances calls a public block-explorer/RPC, which logs which addresses you asked about (linking holdings to you). That's an explicit opt-in below. The fully-sovereign live path (Neutrino/BIP158 for Bitcoin, a verifying client + Tor for EVM) is a separate build — it reads from the chain's peer network with local verification, so no single service learns what you hold.
No watched addresses yet. Add a public address above to start tracking holdings across chains.