I am using the OZ defender relayer and want to sign an EIP-712 message. My first thought was to use the ._signTypedData method from ethers, but it seems that the defender relayer signer doesn't adhere to the TypedDataSigner ethers interface. Next I tried to make a raw RPC call, but it seems the pro…

Hi @Jason_Maier , thanks for reporting this. I tried to provide you an easy script to do it with our current infra but it is not possible since EIP712 requires to sign a message with a prefix different to the standard “Ethereum Signed Message”, and the “eth_signTypedData_v4” is a wallet-specific JSO…

Ernesto, Thanks so much for your reply. Do you have a sense about the timeline of the next release? One thought I had was the possibility of wrapping the defender relayer in another wallet specific relayer. Do you think this is a possible solution? Thanks again! Jason

Thanks Ernesto! For some context, the reason this suddenly became important is that Open Sea just migrated to a new contract, and requires 712 signatures. We've been using Defender for automated market maker bots, and it's been really great, but need this feature to get them back online.

Thanks to both for waiting. This is the current status to support this endpoint: defender: I've already sent a PR (private repo), it's already merged so it should be released within this week. I'll update you defender-relay-client: I still need to start working on this one. In any case, if we happ…

There you go guys Added _signTypedData method OpenZeppelin:master ← OpenZeppelin:feature/sign-typed-data-endpoint opened 07:07PM - 01 Mar 22 UTC (UTC) [ernestognw] ernestognw …

Ernesto, This is great. Thanks for the quick turn around. Always impressed by the OpenZeppelin team. Cheers, Jason

@ernestognw In response to this note above, I have been able to now use the signTypedData method in local development using the apiRelayer, but when I upload the script to an autotask the method no longer runs with the autotask relayer. I am getting the following error "signer._signTypedData is not…

Hey Jason, thanks for reporting. Indeed it's that the Autotask Runtime doesn't have the newest version of the defender relay client. I've sent a PR to update it so it should be out by the next release (during the week). In the meantime I'd recommend using the Open Source code we have for the client…

Awesome. Thanks for this! Will keep you updated and check in later this week

Eip-712 signature with DefenderRelayerProvider

Support Defender

ernestognw June 3, 2022, 7:04pm 11

Just for reference, the Autotask issue has been addressed.

Best to all

Topic		Replies	Views
signer._signTypedData no working in autotask for injected Relayer Defender erc721 , autotasks	2	1752	June 3, 2022
Using OpenZeppelin Defender's relayerSigner in place of ethers signer Defender	1	65	November 20, 2024
Defender Relay Client Ethers Issue Defender	3	982	August 5, 2022
Enable legacy signatures for Defender relayers (v == 27 \|\| 28) Support defender	0	106	June 6, 2024
Cannot verify Defender Relayer signatures on OZs ECDSA Solidity library Support defender , etherscan-verify	0	239	April 2, 2024

Eip-712 signature with DefenderRelayerProvider

Related topics