ERC-6492 signature validation

[bobo-k2]

Summary

Adds ERC-6492 signature validation support to the testapp's verifySignMsg helper.

ERC-6492 signatures are produced by undeployed smart contract wallets (e.g. a fresh SCW that has not yet been deployed on-chain). The standard isValidSignature contract call would fail for these accounts because no contract exists yet.

What changed (examples/testapp/src/components/RpcMethods/method/signMessageMethods.ts):

• Import viem helpers: encodeAbiParameters, erc6492SignatureValidatorByteCode, isErc6492Signature, parseAbiParameters.
• In verifySignMsg, detect ERC-6492 signatures with isErc6492Signature before falling back to the existing EIP-1271 path.
• When an ERC-6492 signature is detected, encode (address signer, bytes32 hash, bytes wrappedSignature) and simulate the Universal Signature Validator bytecode via publicClient.call. The validator deploys the account and calls isValidSignature in a single read-only eth_call — nothing is deployed on-chain.
• Parse the bool result from the returned ABI-encoded data and return a human-readable verification message.
• Add authorizationList: undefined to the fallback readContract call to silence a viem type warning.

How did you test your changes?

• Tested manually in the testapp by connecting a fresh (undeployed) SCW account, signing a typed-data message, and running verifySignMsg. The ERC-6492 path returns "SigUtil Successfully verified signer as <address> (ERC-6492)".

• Verified that standard EIP-1271 signatures for deployed accounts still go through the existing readContract path without regression.

[Copilot]

Pull request overview

Adds ERC-6492 signature validation support to the testapp’s verifySignMsg helper so signatures from undeployed smart contract wallets can be verified via Universal Signature Validator simulation (eth_call) before falling back to the existing EIP-1271 on-chain isValidSignature path.

Changes:

• Detect ERC-6492 signatures using isErc6492Signature and validate them via publicClient.call with erc6492SignatureValidatorByteCode.
• ABI-encode the validator call payload and return ERC-6492-specific success/failure UI messages.
• Add authorizationList: undefined to the EIP-1271 readContract call to silence a viem type warning.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[b-d-m-p]

Clean implementation! The ERC-6492 detection and validator flow looks good. Just a couple minor suggestions.