A place for talking about the Ethereum Virtual Machine on Farcaster.

Is anybody aware of an ERC standard (or draft) related to using EIP712 typed signature data to route validation logic for ERC1271 contract sigs?

Or if one doesn't exist, would that be a worthwhile standard?

Here's what I'm using currently, but it needs to be generalized to support recursive contract sigs

building /hatsprotocol | 
proudly mid-curving it since 1995

cc @auryn the champion of recursive contract sigs 🫡

Hhhmmm, shouldn't the recursion happen out of the box with 1271?

not (I don't think) when requiring this additional data be appended and assuming the first 65 bits are the signature. Or more precisely, you can recurse down *to* a contract that implements this scheme, but not past it.

Here's the actual implementation

I believe Safe's implementation is recursive

But from what I can tell, it assumes the length of an individual signature is always 65. This is fine for safe, since there is only one validation route (total valid sigs >= M), but since there is no room to append extra data, this scheme can't support other validation routes like I'm trying to enable

I believe Safe's implementation is recursive 

https://github.com/safe-global/safe-smart-account/blob/2278f7ccd502878feb5cec21dd6255b82df374b5/contracts/handler/CompatibilityFallbackHandler.sol#L57-L68