WalletConnect To DApps: "Invalid order signature" when attempting to list an NFT for auction

[0xMillz]

Overview

I've been trying to list a Polygon NFT that I hold on my KeepKey for sale on the OpenSea dApp (auction-type) via the Connect to Dapp feature in web. I am able to approve it and sign all the data messages on my KeepKey but when the final response is sent back to the OpenSea dApp, the dApp briefly displays a toast message that says "Invalid order signature" and the browser dev logs for OpenSea throw a graphql error, somethings about useHandleBlockchainActionsCreateOrderMutation (see final screenshot):

References and additional details

I'm guessing it could be a fix like this one but I really haven't dug into the code yet

Acceptance Criteria

You can sucessfully list for sale a Polygon NFT on the OpenSea dApp

Need By Date

No response

Screenshots/Mockups

No response

Estimated effort

4 - 8 hours, optimistically

[0xMillz]

Self-assigning this issue to myself. I don't have repo privileges so can't do it officially

[0xMillz]

Closing this issue as "won't do", as it appears to be related to KeepKey only and out of the domain of web. Using @metamask/eth-sig-util's recoverTypedSignature_v4, I was able to verify that the recovered address from the signatures produced from wallets like ShapeShift Native for eth_signTypedData_v4 messages are accurate, while for KeepKey they are not. Ref: https://github.com/MetaMask/eth-sig-util/blob/cf4352793a78727df8b0585190b4d39d5c166ba4/src/sign-typed-data.ts#L853C39-L853C39

[0xMillz]

Reopened because I came up with a solution. A PR to hdwallet is incoming and then a PR to web will follow with an hdwallet version bump

[0xMillz]

This is the PR in hdwallet that will fix this issue: shapeshift/hdwallet#649
Once web bumps to the version of hdwallet containing the above change, this issue should be resolved!