commit 12e0dba

@gtwototoo noticed that some Pairs reported error Vault not registered: 0x2abcb7a797a853f143b177a42261692dc6f124cc’
when crosschecked on latest development branch created order successfully

• connect hyperliquid
  • Select connection mode (wallet/vault/api_wallet) >>> api_wallet
    • Enter your main Arbitrum wallet address: ok (Metamask address 0x2ABcb7a797A853f143B177a42261692DC6F124cc)
    • Enter your API wallet private key: ok
    • connected successfully
    • balance: ok
    • created/started pureMM strategy
    • got error Vault not registered: 0x2abcb7a797a853f143b177a42261692dc6f124cc’ ❌
      • 19:48:50 - client_order_tracker - Order 0x3f3eeff422721dcdbe91d4c83ac8e67
        c has failed. Order Update: OrderUpdate(trading_pair='PURR-USDC', update_
        timestamp=1762372130.0, new_state=<OrderState.FAILED: 6>, client_order_id
        ='0x3f3eeff422721dcdbe91d4c83ac8e67c', exchange_order_id=None, misc_updat
        es={'error_message': 'Error submitting order 0x3f3eeff422721dcdbe91d4c83a
        c8e67c: Vault not registered: 0x2abcb7a797a853f143b177a42261692dc6f124cc'
        , 'error_type': 'OSError'})

PR7837 (api_wallet)

development: (wallet)

hi @gtwototoo could you please comment with the progress here

@nikspz Sorry for the delay, I'm currently testing code changes. The problem is caused by a discrepancy between the documentation and the HyperLiquid code. I'm currently trying to figure out why this is happening.