秋田预测市场 · Discord 审计

Tien Nam Pham参与话题 1消息总数 7

该用户的聊天记录定位。

Reset

聊天记录

共 7 条,显示第 1-7 条
Tien Nam Pham 2026-06-22 16:11:27 Hyperliquid

how about the pricing

how about the pricing

Tien Nam Pham 2026-06-22 11:13:12 Hyperliquid

ah i see, thats my assumption

ah i see, thats my assumption

Tien Nam Pham 2026-06-22 11:09:16 Hyperliquid

So, just in case i want to track the orders via the specificed builder address. Can i do it? Now, i can get the userFills by user address -> get txDetails for each order by the hash to get the builder address + fee. But seems like its not correct. I know HL provides the api to get the historical trades for the builder, but it is delayed 2 days. I want to track in the realtime.

So, just in case i want to track the orders via the specificed builder address. Can i do it? Now, i can get the userFills by user address -> get txDetails for each order by the hash to get the builder address + fee. But seems like its not correct. I know HL provides the api to get the historical trades for the builder, but it is delayed 2 days. I want to track in the realtime.

Tien Nam Pham 2026-06-19 11:52:19 Hyperliquid

could u explain more?

could u explain more?

Tien Nam Pham 2026-06-18 10:49:39 Hyperliquid

gm, i have a question. When i get the userFills, the api https://api.hyperliquid.xyz/info returns the wrong tx_hash in the orders. For example curl --location 'https://api.hyperliquid.xyz/info' \ --header 'Content-Type: application/json' \ --data '{ "user": "0x916e6648257c075799776434196262524ace8369", "type": "userFills" }' return the transaction 0xc87cb7d114ddc37bc9f6043ddb0cc90000b7cfb6afd0e24d6c456323d3d19d66. But the details of this transaction are { "type": "txDetails", "tx": { "time": 1781618418831, "user": "0x58e1b0e63c905d5982324fcd9108582623b8132e", "action": { "type": "SetGlobalAction", .... The user is different and the action.type is different as well. <@393306224185180161>

gm, i have a question. When i get the userFills, the api https://api.hyperliquid.xyz/info returns the wrong tx_hash in the orders. For example curl --location 'https://api.hyperliquid.xyz/info' \ --header 'Content-Type: application/json' \ --data '{ "user": "0x916e6648257c075799776434196262524ace8369", "type": "userFills" }' return the transaction 0xc87cb7d114ddc37bc9f6043ddb0cc90000b7cfb6afd0e24d6c456323d3d19d66. But the details of this transaction are { "type": "txDetails", "tx": { "time": 1781618418831, "user": "0x58e1b0e63c905d5982324fcd9108582623b8132e", "action": { "type": "SetGlobalAction", .... The user is different and the action.type is different as well. <@393306224185180161>

Tien Nam Pham 2026-06-18 10:48:53 Hyperliquid API userFills接口返回错误tx_hash问题

gm, i have a question. When i get the userFills, the api https://api.hyperliquid.xyz/info returns the wrong `tx_hash` in the orders. For example ``` curl --location 'https://api.hyperliquid.xyz/info' \ --header 'Content-Type: application/json' \ --data '{ "user": "0x916e6648257c075799776434196262524ace8369", "type": "userFills" }' ``` return the transaction `0xc87cb7d114ddc37bc9f6043ddb0cc90000b7cfb6afd0e24d6c456323d3d19d66`. But the details of this transaction are ``` { "type": "txDetails", "tx": { "time": 1781618418831, "user": "0x58e1b0e63c905d5982324fcd9108582623b8132e", "action": { "type": "SetGlobalAction", .... ``` The user is different and the action.type is different as well.

gm, i have a question. When i get the userFills, the api https://api.hyperliquid.xyz/info returns the wrong `tx_hash` in the orders. For example ``` curl --location 'https://api.hyperliquid.xyz/info' \ --header 'Content-Type: application/json' \ --data '{ "user": "0x916e6648257c075799776434196262524ace8369", "type": "userFills" }' ``` return the transaction `0xc87cb7d114ddc37bc9f6043ddb0cc90000b7cfb6afd0e24d6c456323d3d19d66`. But the details of this transaction are ``` { "type": "txDetails", "tx": { "time": 1781618418831, "user": "0x58e1b0e63c905d5982324fcd9108582623b8132e", "action": { "type": "SetGlobalAction", .... ``` The user is different and the action.type is different as well.