Uppercase address in the "action" content causing signature error.

[nom4dv3]

Bug brief

When calling "spotDeploy" api, if the address list in "userAndWei" involves uppercase, it leads to signature error: L1 error: User or API Wallet 0xe62b09a760b8bd649cc678767fbb74c868b05111 does not exist., which is quite misleading.

How to reproduce

use the following to send api

action = {
        "type": "spotDeploy",
        "userGenesis":{
            "token": TOKEN_ID,
            # note: address should use lowercase, uppercase would cause signature error.
            "userAndWei": [["0xABCDEABCDEABCDEABCDEABCDEABCDEABCDEABCDE","0"]],
            "existingTokenAndWei": []
        }
    }

Suggestions

1. In the chain node side, use the original message to recover signer address from signature rather the lowercase ones
2. or, on the sdk side, either support auto toLowercase or throw error when it has uppercase.

[traderben]

The sdk already lowercases addresses that need to be lowercased. You can see similar implementation for the builder code in orders: https://github.com/hyperliquid-dex/hyperliquid-python-sdk/blob/master/hyperliquid/exchange.py#L116
The sdk does not support spotDeploy so this cannot be an existing bug in the sdk.

[nom4dv3]

Correct, although suggestion#1 would be a cleaner solution.
Btw, I've added the spotDeploy here #104 , also covered the suggestion#2.