“For signatures that will be used onchain, such as with Permit2 or Seaport developers will need to inspect the signature offchain and remove unneeded ERC-6492 data, if it is present” 

non dev: annoying, trivial, standard?

“For signatures that will be used onchain, such as with Permit2 or Seaport developers will need to inspect the signature offchain and remove unneeded ERC-6492 data, if it is present” 

non dev: annoying, trivial, standard?
https://www.smartwallet.dev/guides/signature-verification

Data privacy on the web. Keeper of the fabric @privy.

Fmr Protocol Labs consensus work. Before that YC S14 🇫🇷🌐🍊

🖖| via sequence. pimlico. poap. polygon. consensys. paxful. flipside crypto. dash. bridgewater associates. darpa. secdef. navy. dia | linktr.ee/alexanderchopan

Looks like potentially a huge PITA. @henri @pw might have more in depth knowledge about ERC-6492, permit2 and Seaport.

Head of Engineering at Courtyard.io, bringing physical collectibles onchain. nf.td/joe /courtyard /backend

I think it's manageable. 6492 signatures pretty easy to detect and strip back to regular signatures

https://x.com/WilsonCusack/status/1787207639534907631