hyperliquid-python-sdk
pypi:hyperliquid-python-sdk · v0.24.0 · sha256:b3fba7c53f4f · as of 2026-11-10
- Does it take your key? traced
- No private-key read found in what we read of its setup and published code — the limits say how much that was.
- Our static read of the published artifact found it.
- Does your key leave? no evidence
- Not yet run — we have not run this version with planted test keys.
- No evidence line on file for this question yet.
- Can it move funds on its own? declared
- Unknown — we could not read what it exposes.
- The project says so — README, config, env list or tool description.
- What changed? no evidence
- First profile of this subject — nothing to compare yet.
- No evidence line on file for this question yet.
Is this your project? Respond →Dispute this reading
Hosts contacted
| Host | When | Role | Evidence |
|---|---|---|---|
| api.hyperliquid-testnet.xyz | code | other | traced |
| api.hyperliquid.xyz | code | vendor | traced |
Evidence (5 lines)
- tracedT-hosts2026-11-10
api.hyperliquid-testnet.xyz appears in shipped code (other).
hyperliquid/utils/constants.py
- tracedT-hosts2026-11-10
api.hyperliquid.xyz appears in shipped code (vendor).
hyperliquid/utils/constants.py
- tracedT-key-handling2026-11-10
Turns key material it is GIVEN into an account or signer (eth_account.Account.from_key()); no read of a key from the environment or a key file was found. A signing library does this.
hyperliquid/exchange.py:637
- declaredD-doc-funds2026-11-10
The project's own text says it carries out transactions: "3. The trading logic tasks send orders and cancels to the batching task."
https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/nonces-and-api-wallets.md (line 37)
- declaredD-doc-funds2026-11-10
The project's own text says it carries out transactions: "Note that nonces are stored per signer, which is the address of the private key used to sign the transaction. Therefore, it's recommended that each trading process or frontend session use a separate private key for sign…"
https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/nonces-and-api-wallets.md (line 44)
Limits
- The observed lane has not run on this version: not yet run on this version
- Traced analysis follows flows inside one module and one hop across a relative import; a longer chain is not followed.
- The observed lane has not run on this version.
- No tool inventory was available, so fund actions were not read.
- Traced: Python read line by line, not parsed.
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
sato.custody/v1 · custody-3
Maintain this project? Respond to this reading
Loading sign-in…