Is there a plan / EIP for native multi-signature transactions?

Question

We have a 2-of-3 multi-signature wallet contract which works fine. However, when sending to exchanges or wallets which use RPC calls (rather than contract events) to capture incoming transactions, they do not see ours (see this for why).

It seems reasonable and useful to have native multi-signature addresses which can initiate transactions and be treated as first-class senders in transaction objects.

Does anyone know of a plan to add this feature in an upcoming protocol update, or an EIP on which to discuss it?

Answer 1

AFAIK, there's no plan for it. When we met Vitalik in Hanoi, we also asking about the multisig and threshold signature then he answered that there's no clear reason to support it native so if you have clear reason to request it you can make your own EIP though.

Answer 2

Account Abstraction, should enable this, assuming it gets finalized and included. You can see in the Account Abstraction EIP, Vitalik said:

It will be possible for accounts to use whatever signature scheme they want