Fix USD class transfer typed-data signing #145
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
SpotUser/ClassTransferpayload with theUsdClassTransfertyped-data schema expected by the APIsign_typed_dataand post it asActions::UsdClassTransferProblem
Running
cargo run --bin class_transfer(or callingExchangeClient::class_transfer) againstmasterreturns a 422 from Hyperliquid:Hyperliquid migrated USD class transfers away from the
SpotUserL1 action; the SDK is still sending that outdated payload, so the exchange rejects it before signature verification.Testing