Before funding, identify the trading network in both Cival and the official venue. This example is testnet. Its funding page names Arbitrum Sepolia and links to Hyperliquid testnet. Do not send real assets through these practice instructions. If the dashboard, wallet, and funding destination disagree about the network, stop. Resolve that mismatch with support rather than trying different networks or bridge addresses. In the dashboard, open Deposit and Withdraw, then Open Hyperliquid funding. The captured link leads to Hyperliquid's testnet deposit page. Cival says its direct funding implementation is being updated after the legacy bridge was deprecated. Use the current official interface and verify the destination domain. Do not copy a bridge address or a token contract from an old tutorial, a chat message, or this recording. For practice, use the official testnet resources linked by the dashboard and follow their current eligibility requirements. They are not real funds. For a mainnet workspace, continue only after Cival confirms that provisioning and permissions are on mainnet. Read the venue's current deposit options, required asset, supported source network, minimum, gas needs, and fees. Availability can change. This recording does not establish a mainnet funding route or a fixed minimum. Connect the same wallet you verified with Cival. On the official deposit screen, review the full destination, network, token, amount, and total expected fee. Make sure you understand any approval being requested. If anything is unexpected, reject it. Complete any transfer privately in your own wallet. No signature or deposit was performed for this video, and a picture of a confirmation screen would not by itself establish that a transfer settled. Wait for the route's completed status and check the venue's account balance. Return to Cival and refresh. Wallet token balance, trading account value, and available withdrawal balance are different measurements. A wallet signature or a falling balance is not sufficient proof of settlement. If a transfer is delayed, keep its transaction reference and inspect the official route status. Do not send it again just because Cival has not refreshed yet.