WEBVTT

1
00:00:00.600 --> 00:00:02.627
Begin each session in Hosting.

2
00:00:02.827 --> 00:00:07.698
Review runtime, service health, recent cycle outcomes, and any customer

3
00:00:07.698 --> 00:00:08.864
visible incident.

4
00:00:09.064 --> 00:00:12.371
Then open your dashboard and read its network banner.

5
00:00:12.571 --> 00:00:17.825
Running infrastructure and an enabled scheduler do not guarantee a trade,

6
00:00:17.825 --> 00:00:20.848
profitable behavior, or mainnet readiness.

7
00:00:21.048 --> 00:00:25.699
This example remains on testnet even where other badges say live.

8
00:00:25.899 --> 00:00:31.217
Use the explicit network indication, not the most optimistic sounding status

9
00:00:31.217 --> 00:00:31.637
label.

10
00:00:32.487 --> 00:00:37.878
In Agents, open View Details and review the decision stream, recent cycle

11
00:00:37.878 --> 00:00:40.167
result, and any reported error.

12
00:00:40.367 --> 00:00:44.890
A strategy may be standing aside because its conditions are not met.

13
00:00:45.090 --> 00:00:48.119
That is not automatically a broken scheduler.

14
00:00:48.319 --> 00:00:53.024
Compare the decision with the configured market and timeframe before asking

15
00:00:53.024 --> 00:00:53.589
for help.

16
00:00:53.789 --> 00:00:58.761
Do not repeatedly press Analyze, Run cycle, or Run all to try to

17
00:00:58.761 --> 00:01:00.082
force a position.

18
00:01:00.932 --> 00:01:05.847
Review open positions, orders, fills, and fees at the venue as well as

19
00:01:05.847 --> 00:01:06.479
in Cival.

20
00:01:06.679 --> 00:01:12.229
Distinguish allocated budget, account value, unrealized profit or loss, and

21
00:01:12.229 --> 00:01:13.783
withdrawable balance.

22
00:01:13.983 --> 00:01:15.924
They answer different questions.

23
00:01:16.124 --> 00:01:20.928
The numbers in this recording are test activity, not performance evidence

24
00:01:20.928 --> 00:01:23.100
and not a recommended allocation.

25
00:01:23.300 --> 00:01:28.445
If the records disagree, preserve a redacted error and transaction reference

26
00:01:28.445 --> 00:01:31.492
and investigate before placing another order.

27
00:01:32.342 --> 00:01:37.605
Know the difference between pausing an agent, halting new entries, canceling

28
00:01:37.605 --> 00:01:41.345
orders, closing positions, and revoking a trading key.

29
00:01:41.545 --> 00:01:44.361
Do not assume one button performs all five.

30
00:01:44.561 --> 00:01:47.441
We show the controls without operating them.

31
00:01:47.641 --> 00:01:52.804
After any action you choose, verify orders, positions, and permission state

32
00:01:52.804 --> 00:01:53.699
at the venue.

33
00:01:53.899 --> 00:01:58.744
For support, share the affected page, timestamp, network, and a redacted

34
00:01:58.744 --> 00:01:59.147
error.

35
00:01:59.347 --> 00:02:04.354
Never send a recovery phrase, private key, password, or wallet approval as

36
00:02:04.354 --> 00:02:06.046
troubleshooting evidence.

37
00:02:06.896 --> 00:02:11.916
To withdraw, open Deposit and Withdraw and follow the official Hyperliquid

38
00:02:11.916 --> 00:02:14.427
funding link for the correct network.

39
00:02:14.627 --> 00:02:19.437
Review current withdrawable funds, any open exposure or collateral

40
00:02:19.437 --> 00:02:23.373
restriction, destination, token, route, and total fee.

41
00:02:23.573 --> 00:02:26.432
Complete the transaction privately in your wallet.

42
00:02:26.632 --> 00:02:31.102
Wait for the full route to finish and verify receipt at the destination

43
00:02:31.102 --> 00:02:33.053
before treating it as complete.

44
00:02:33.253 --> 00:02:37.541
A ledger entry can be only one leg of a cross chain transfer.

45
00:02:37.741 --> 00:02:39.960
This video performs no withdrawal.
