Troubleshooting
Start with the wallet address, network, product and transaction signature. A slow or failed interface response is not proof that an on-chain transaction failed.
A deposit seems to have failed
If you declined the wallet prompt, that request was not signed. If you signed, check the transaction signature in an explorer. Confirm whether it succeeded before submitting again.
For a confirmed vault deposit, look for the correct vault and tranche shares. For a direct deposit, identify the external position or receipt. Data can take time to refresh.
I have USDC but cannot submit
Check SOL for fees and account creation, the network, token mint and wallet support. A token’s symbol is not enough to establish that it is the expected asset.
If the program refused the action, inspect its reason. Coverage, caps, pauses, fresh valuation requirements and external liquidity are conditions, not errors fixed by repeated signing.
The withdrawal timer ended, but I cannot claim everything
Distinguish eligibility from funding. The notice period can be complete while the vault lacks cash, coverage or another funding condition. Check whether part is already funded and claimable.
Unfunded shares remain exposed to results. Cancelling an unfunded portion returns shares, not a historical USDC price. See withdrawals.
My withdrawal is partly completed
A claimable USDC amount and pending shares can coexist. Claiming funded USDC does not complete the remaining request. Read the request’s current state and avoid opening duplicate requests because the full expected amount has not arrived.
The position is missing or its value looks wrong
Check address and network. Compare with the confirmed transaction and the relevant protocol’s official interface. Akashi’s portfolio can lag or omit unsupported types. A wallet’s token price can also differ from a vault’s share valuation.
The site is unavailable
For a direct position, an external interface may support your operation under that protocol’s rules. For a vault, shares exit through the vault, with the same permissions and limits. A different interface cannot bypass coverage, pauses or invested funds waiting to return.
An alert did not arrive
Check opt-in, linked account, alert type and delivery frequency. Detection and delivery can lag. The absence of a message does not establish the absence of risk or a state change.
Report a reproducible problem
Use the feedback form with the public address, transaction signature, network, expected action and observed result. Screenshots should not include credentials. For security issues, follow security reporting.
Never send a recovery phrase or private key, and never sign a supposed support transaction without understanding its effect.