Wallets and transactions
Connecting a wallet lets Akashi identify an address and request supported actions. Connecting alone does not authorise spending. Signing a message and signing a transaction are separate actions that you should review.
Prepare your wallet
Use a compatible Solana Wallet Standard wallet. Check the selected network and keep SOL for transaction fees and required account creation. Having USDC does not remove the need for SOL.
A mainnet token and a devnet token with the same symbol are different assets. Confirm the network before following a deposit guide.
Understand what you sign
A message signature can prove control of a wallet to a service, such as the curator console. Review the text and domain. A transaction can move assets or change on-chain state: inspect the action, accounts, amount and estimated outcome.
The Akashi backend builds unsigned instructions. It does not sign user transactions or ask for your private key. The separate vault executor signs only the actions its own configured role permits.
Submission is not confirmation
After you approve a transaction, it must reach the network and confirm. Save its signature. Check the explorer if the app is slow or reports an error.
A declined wallet prompt means you did not sign that request. A failed transaction is different from a submitted transaction whose result has not yet been observed. Before retrying an unclear result, check the original signature to avoid a duplicate action.
Common reasons for failure
Insufficient SOL, unavailable liquidity, stale values, exceeded slippage, incorrect network, expired blockhash or a program’s limits can stop an action. Repeatedly signing cannot remove a contract condition.
A vault can be paused or unable to preserve coverage. For direct positions, the external protocol’s own conditions apply.
Never give a recovery phrase or private key to a site or support contact. Troubleshooting explains what public information is useful when investigating a problem.