WEBVTT

1
00:00:00.600 --> 00:00:02.541
Cival separates three steps.

2
00:00:02.741 --> 00:00:06.240
A connection identifies the selected wallet account.

3
00:00:06.440 --> 00:00:09.363
An ownership signature proves you control it.

4
00:00:09.563 --> 00:00:14.048
An agent approval gives a separate trading key permission to act on the

5
00:00:14.048 --> 00:00:14.427
venue.

6
00:00:14.627 --> 00:00:16.632
Those are not interchangeable.

7
00:00:16.832 --> 00:00:18.880
Funding is another separate step.

8
00:00:19.080 --> 00:00:24.048
Do not assume that a saved verified status means the browser is connected

9
00:00:24.048 --> 00:00:28.607
now, that the current network is mainnet, or that an agent has been

10
00:00:28.607 --> 00:00:29.832
configured safely.

11
00:00:30.682 --> 00:00:35.221
Open Wallet and funding and scroll to Step three, Approve your trading

12
00:00:35.221 --> 00:00:35.610
agent.

13
00:00:35.810 --> 00:00:40.183
Reconnect the same verified account if the controls are disabled.

14
00:00:40.383 --> 00:00:45.698
In this capture, Cival reports a saved Hyperliquid approval, but the browser

15
00:00:45.698 --> 00:00:48.426
is not connected to a wallet extension.

16
00:00:48.626 --> 00:00:52.509
That saved status belongs to this example and its network.

17
00:00:52.709 --> 00:00:57.274
It is not evidence that your own wallet, a new workspace, or mainnet

18
00:00:57.274 --> 00:00:59.087
has the same authorization.

19
00:00:59.937 --> 00:01:04.366
When you choose to approve, inspect the wallet's complete authorization

20
00:01:04.366 --> 00:01:04.865
request.

21
00:01:05.065 --> 00:01:09.577
Confirm the site, your account, the network, and the intended agent key

22
00:01:09.577 --> 00:01:10.975
against the workspace.

23
00:01:11.175 --> 00:01:16.253
The funding page describes Hyperliquid's approve agent permission as trade

24
00:01:16.253 --> 00:01:18.449
capable, not withdrawal capable.

25
00:01:18.649 --> 00:01:23.258
Stop if the actual prompt asks for an unexpected transfer or broader

26
00:01:23.258 --> 00:01:24.004
permission.

27
00:01:24.204 --> 00:01:29.004
The wallet owner must make this security decision and complete it privately.

28
00:01:29.204 --> 00:01:32.361
We have not issued a new approval in this recording.

29
00:01:33.211 --> 00:01:38.004
A key that cannot withdraw can still place orders that lose money or

30
00:01:38.004 --> 00:01:38.779
incur fees.

31
00:01:38.979 --> 00:01:44.124
Review your strategy, allowed market, capital allocation, and effective risk

32
00:01:44.124 --> 00:01:46.019
controls before enabling it.

33
00:01:46.219 --> 00:01:49.270
An approval badge is not a risk assessment.

34
00:01:49.470 --> 00:01:54.654
This series does not recommend a market, leverage setting, or position size.

35
00:01:54.854 --> 00:01:59.949
Start with practice and verify the actual limits enforced by your workspace

36
00:01:59.949 --> 00:02:03.686
rather than copying the example's balances or settings.

37
00:02:04.536 --> 00:02:06.883
Keep a recovery path outside Cival.

38
00:02:07.083 --> 00:02:12.056
The dashboard explains that the approved trading key can be revoked through

39
00:02:12.056 --> 00:02:14.443
Hyperliquid's official API controls.

40
00:02:14.643 --> 00:02:19.629
Use the same owner wallet and the correct network, then verify the resulting

41
00:02:19.629 --> 00:02:20.744
permission state.

42
00:02:20.944 --> 00:02:25.844
Revoking a key is not evidence that existing orders were canceled or

43
00:02:25.844 --> 00:02:27.429
positions were closed.

44
00:02:27.629 --> 00:02:29.677
Review those separately at the venue.

45
00:02:29.877 --> 00:02:34.891
Next, install a strategy and inspect a paused agent before making an

46
00:02:34.891 --> 00:02:37.472
independent decision to operate it.