Approval not visible
An approver can't see a vault or pending request it should be able to see — including a known, fixed 2026-08-27 defect.
Symptom
An external approver's connected wallet doesn't show the vault it's an approver on, or doesn't show a specific request awaiting its approval.
A known, fixed defect (v1.0.0)
On 2026-08-27, a production defect in hosted tenancy's participant derivation was found and fixed: the server was reading the wrong internal field name when determining a hosted request's participants, so external-approver wallet keys never entered the participant set an approver's own access was checked against. The practical symptom was exactly this page's topic — an approver-only wallet could not see its vault, the open request, the request by id, or reach the approvals route.
This was classified as a strictly fail-closed availability defect: no funds, authority, or cross-tenant exposure occurred. Approval authority itself (the actual cryptographic signature verification for an approval slot) was never affected — the bug only prevented an otherwise-legitimate approver from seeing what it should have been able to act on. The fix is deployed in the current production source (v1.0.0), with dedicated regression tests, and an additional request-mutation guard now pins sensitive actions to the actual signer/ owner/agent/delegate principals so an approver's access stays narrow — see Owner/agent/approver authority boundaries.
If you are running against the current hosted production deployment or a build at or after v1.0.0, this specific issue should not recur. If you are self-hosting from an older commit, update.
Other causes to check first
- Wrong wallet account — confirm the approver's specific wallet account is active; see Wrong wallet connected.
- Wrong network — see Wrong network.
- The approver was never actually added to the vault's approver set — confirm with the vault owner that the add-an-external-approver operation actually confirmed on-chain, and that the address/key used matches the wallet the approver is connecting with.
- The request doesn't actually require this approver's signature — confirm the request is above the vault's approval threshold and that this approver is one of the configured slots.
See also: Approval states, Tenant isolation, Responsible disclosure.