Vault not visible
A vault you expect to see isn't showing up in the dashboard — here's how to work out why.
Symptom
A vault you know exists (you created it, or you're an agent/approver on it) isn't appearing when you connect your wallet.
Most common cause: wrong wallet account
Vault visibility is derived directly from the covenant's own owner/agent/approver identities matched against your currently connected wallet account. If a different account than the one actually associated with the vault is active in your wallet, the vault correctly won't show — see Wrong wallet connected.
Second most common cause: wrong network
A vault that exists on testnet-10 will never appear while connected to a deployment configured for mainnet, or vice versa — see Wrong network.
On a hosted, multi-tenant deployment
Hosted deployments enforce tenancy: a wallet only sees hosted objects it actually participates in on-chain (as owner, agent, or approver). This is by design (see Tenant isolation) — it is not a bug if a vault you have no on-chain role in doesn't appear, even if someone else added you as an "organization member" for bookkeeping purposes. That kind of application-level membership never grants visibility on its own — see Owner/agent/approver authority boundaries.
If none of the above explains it
- Confirm the vault's creation transaction actually confirmed on-chain — a vault stuck in
PENDING_CREATE(see Vault states) because its genesis transaction hasn't confirmed yet is expected to be temporarily incomplete, not fully "not visible." - If you have another way to check the vault's on-chain state (a block explorer, or the SDK's own state-verification tools), compare what it shows against what the dashboard reports — a genuine mismatch between proven chain state and what a server displays is exactly the kind of thing local intent verification and independent reconciliation exist to catch.
- If a hosted platform bug is suspected, this is a real, specific, reportable class of issue — see Responsible disclosure. A precedent exists: a 2026-08-27 hosted-tenancy defect briefly caused exactly this symptom for external approvers specifically — see Approval not visible.
See also: Vault states, Tenant isolation.