PIP-22: add EIP-3074 style account abstraction

idk - even as of now, Polygon POS does not follow strict EVM equivalency since it doesn’t have a beacon chain, and therefore doesn’t have PREVRANDAO

Is there anything specific gained by not having an EIP like 3074? I agree that there should be full compatibility with Ethereum’s execution environment, ensuring that tooling for Ethereum works for Polygon POS, but what reason is there for not including additional opcodes?

Again, especially in light of the fact that for any other L1/L2 protocol there have been divergences for Ethereum’s protocol. Polygon POS uses a dPOS system, which was different than Ethereum’s POW at its inception, and is different than Ethereum’s post-Merge POS. Why would the line be drawn at specific opcodes?

1 Like