Skip to content

Conversation

@joshieDo
Copy link
Contributor

No description provided.

This test demonstrates that when an EOA's own address is used as the
publicKey for an admin key (which happens when using the EOA's private
key to create the admin key), the validation fails due to a recursive
validation loop in the signature checking logic.

The issue occurs because:
1. unwrapAndValidateSignature extracts the inner signature
2. For Secp256k1 keys, it calls isValidSignatureNowCalldata with the EOA address
3. Since the EOA has code (via EIP-7702), it calls isValidSignature on the EOA
4. This triggers the 64/65 byte special case expecting raw EOA signature
5. But the signature is EIP-712 formatted, causing validation to fail
@joshieDo joshieDo force-pushed the test/eoa-admin-key-validation-issue branch from 6af630f to 6474ffc Compare August 29, 2025 10:24
@jenpaff jenpaff modified the milestones: Mainnet Launch, v0.5.2 Aug 29, 2025
@legion2002 legion2002 modified the milestones: v0.5.2, v0.6.0 Sep 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants