lazy mint issue : The author's signature is invalid

[subsub-wp]

I'm currently trying out lazy mint via mobile metamask.
Here are the message data types for signing:

constant type = { part: [ {Name: 'Account', Type: 'Address'}, {name: 'value', type: 'uint96'} ], Mint721: [ {name: 'tokenId', type: 'uint256'}, {name: 'tokenURI', type: 'string'}, {name: 'maker', type: 'part[]'}, {name: 'Royalty', type: 'Part[]'} ] };

This is the data sent as metamask.

{"types":{"EIP712Domain":[{"name":"name","type":"string"},{"name":"version","type":"string"},{"name":"chainId","type":"uint256"},{"name":"verifyingContract","type":"address"}],"Part[]":[{"name":"account","type":"address"},{"name":"value","type":"uint96"}],"Mint721":[{"name":"tokenId","type":"uint256"},{"name":"tokenURI","type":"string"},{"name":"creators","type":"Part[]"},{"name":"royalties","type":"Part[]"}]},"domain":{"name":"Mint721","version":"1","chainId":4,"verifyingContract":"0x6ede7F3c26975AAd32a475e1021D8F6F39c89d82"},"message":{"tokenId":"102471026965568440470777112818969011314476974038274040562038766217833928982600","tokenURI":"/ipfs/QmXzWyJc2EXvKxqKh3nRvxHdXvoWv3Q1x821QENVU3Hs2X/33.json","royalties":[{"account":"0xE28c8Bc2E1225f50321bfba8E6B0B933C6995529","value":1000}],"creators":[{"account":"0xE28c8Bc2E1225f50321bfba8E6B0B933C6995529","value":10000}]},"primaryType":"Mint721"}

After signing, mint to https://ethereum-api-staging.rarible.org/v0.1/nft/mints and you will get:

{"code":"VALIDATION","message":"The author's signature is invalid. [0xe28c8bc2e1225f50321bfba8e6b0b933c6995529]","status":400}

I need help

[bobwith2bees]

@subsub-wp Are you using WalletConnect to send the request to MetaMask?

[subsub-wp]

Yes, I am requesting an sign via Wallet Connect.

[subsub-wp]

thank you for answering.
I have a question.

1. Do testnet also need a chainid of 1?
2. Where is the eth_sig_tools API?

When performing a signature request use chainId 1 with the eth_sig_tools API. The NFT target chainId is captured within the SignedTypedData EIP712Domain, and can be different. The validation contract must correspond to the chainId within the SignedTypedData EIP712Domain. (Each chain would a unique contract.)

[bobwith2bees]

I have not yet tried Metamask with WalletConnect. I have successfully used Trustwallet (Android) and Rainbow (Android and IOS).

Since you are using WalletConnect your call to eth_sig_tools is the "eth_signTypedData" wallet connect request. The wallets I have tested handle the API chainId of 1 for you. The wallet you are signing with should be the wallet with address 0xE28c8Bc2E1225f50321bfba8E6B0B933C6995529.

[bobwith2bees]

FYI - We got him working. But a tool that quickly validates formatting and sanity checks contents of the forms would be great to have for the next users.

[ChangeLingFox]

Hello there!
I'm having similar issue on Rarible with Metamask. It give me "wrong signature" error while trying to Lazy Mint NFTs.

Client error. Message from client: {
"status": 400,
"url": "https://ethereum-api.rarible.org/v0.1/order/orders",
"data": {
"code": "INCORRECT_SIGNATURE",
"message": "Maker's signature is not valid for V2 order",
"status": 400
},
"code": "ETHEREUM_NETWORK_ERR"
}

This thread is the best that Googling brought. I would be grateful if You'd help me too.

[AndreeaCot]

I am having same issue, I get Maker's signature is not valid for V2 order. Could you please help me as well?

[AndreeaCot]

@bobwith2bees could you help me as well?

[ChangeLingFox]

AndreeaCot
I solved the issue with Rarible support. Using Metamask browser plugin instead of mobile app solved the problem.

[Mostafamohammad428]

In the MetaMask wallet, why does this message appear about selling one of the
NFT tokens on the raribe platform?
Put on sale

Sign message to set fixed price
Client error. Message from client: {
"status": 400,
"url": "https://ethereum-api.rarible.org/v0.1/order/orders",
"data": {
"code": "INCORRECT_SIGNATURE",
"message": "Maker's signature is not valid for V2 order",
"status": 400
},
"code": "ETHEREUM_NETWORK_ERR