秋田预测市场 · Discord 审计

jt17参与话题 0消息总数 2

该用户的聊天记录定位。

Reset

聊天记录

共 2 条,显示第 1-2 条
jt17 2026-06-07 00:31:33 Hyperliquid

To Hyperliquid team: I have deployed a HyperliquidAdapter contract on Arbitrum that implements EIP-1271 isValidSignature. I want to use the contract address itself as the HL master account (directDepositMode=false). When I send approveAgent (or any action) signed by the owner EOA with signatureChainId: "0xa4b1", the API returns status: ok, but the agent is registered under the owner EOA’s HL account instead of the adapter contract’s HL account (extraAgents(adapter) stays []). On-chain EIP-1271 probe passes. Is contract-as-master + EIP-1271 supported for approveAgent / trading actions? If yes, is there a different signing format (EIP-712 typed data vs raw hash) or extra field I need?

To Hyperliquid team: I have deployed a HyperliquidAdapter contract on Arbitrum that implements EIP-1271 isValidSignature. I want to use the contract address itself as the HL master account (directDepositMode=false). When I send approveAgent (or any action) signed by the owner EOA with signatureChainId: "0xa4b1", the API returns status: ok, but the agent is registered under the owner EOA’s HL account instead of the adapter contract’s HL account (extraAgents(adapter) stays []). On-chain EIP-1271 probe passes. Is contract-as-master + EIP-1271 supported for approveAgent / trading actions? If yes, is there a different signing format (EIP-712 typed data vs raw hash) or extra field I need?

jt17 2026-05-31 16:40:45 Hyperliquid

Is there a Hyperliquid developer here who I can talk to about this?

Is there a Hyperliquid developer here who I can talk to about this?