EIP 7702 - Allow JSON-RPC Accounts to use signAuthorization

[Wagalidoom]

Currently it's possible to use the experimental EIP 7702 with local accounts only. I wanted to know if it was plan to make it also compatible with JSON-RPC accounts in the future?
Same question, i was curious to know if this feature will be added to wagmi package too?
Thank you!

[jxom]

It is not possible to sign an authorization over JSON-RPC right now, so it won't be added into Viem until there is an ERC for it.

[ARJUN-R34]

@jxom Is this because the JSON RPC provider would require a new function to sign the authorization ?
I went through the privateKeyToAccount function in viem library and saw the experimental_signAuthorization function being included. I guess that is why this works.

If I use the privateKeyToAccount function from web3js library, it won't work right ?

[brianonchain]

wallet deprecated the wallet api eth_sign, which would have made it possible to sign authorizations. so yeah, it should be easy for wallets to allow signing (shouldn't depend on a new erc). but for wallet security, most wallets probably won't allow it. trend now is for wallets to whitelist code that can be attached to EOA, and to do it from within the wallet, not from the DApp frontend

[kaoizm]

Two years on, a small update for anyone finding this thread.

The blocker jxom mentions — no ERC for pre-delegation signature verification — now has a draft: ERC-8010 (ethereum/ERCs#1186). While turning it into executable conformance vectors we found that its wrapped-signature context is defined differently on the signer and verifier sides (field order and ABI types), so a conforming signer's output does not decode under a conforming verifier: ethereum/ERCs#1186 (comment)

Separately, for the signAuthorization side of this discussion, the underlying EIP-7702 authorization tuple now has portable vectors — signing hash keccak256(0x05 || rlp([chain_id, address, nonce])), low-s / y_parity handling, authority recovery — that a JSON-RPC signer can test against without pulling in a client: https://github.com/kaoizm/7702-safety (vectors/conformance.json, section authorization).

One behaviour worth deciding before this API ships: chain_id = 0 authorizations are valid on every 7702 chain where the authority's nonce matches. If signAuthorization lets callers omit chain_id, that should be an explicit "replayable on every chain" choice surfaced to the user, not a default.