Background
EIP-7702 type 0x04 transactions rely on an authorization signature to allow an externally owned account (EOA) to delegate execution to a specified implementation contract.
In practice, many modern wallets—particularly browser-based wallets—do not support eth_sign, but do support personal_sign. Without support for personal_sign-based authorization signatures, these wallets are unable to participate in EIP-7702 flows on Story, limiting practical adoption and integration.
This change is intended to improve wallet compatibility and does not alter the underlying EIP-7702 authorization model, including chain binding, nonce-based replay protection, or implementation binding.
Proposal
Formalize support on the Story chain for EIP-7702 authorization signatures generated via personal_sign, in addition to the existing eth_sign-style authorization verification.
Transactions containing personal_sign authorizations include an explicit signaling mechanism allowing the execution client to distinguish the signature type during verification. Authorization semantics remain unchanged, and backward compatibility is preserved.