Introduction Though smart contract wallet offers many flexibity and possibility to manage wallets, the current AA wallet implementation faces a few UX issues that prevent it from mass adoption. Currently AA wallets have different addresses on different chains. So users cannot receive any fund before they deploy their wallets on a new chain, or otherwise they will potentially lose the fund. With the trend of more L2s, it becomes harder for users and wallets to maintain the signing keys across all chains. To solve these two issues, we propose to a keystore-centric AA wallet design. The goals of the keystore include: Users can have the same AA wallet address across all EVM-compatible chains using the keystore and be able to bind AA wallets with different addresses for non-EVM-compatible chains The keystore should be generic that can be compatible to different AA wallet implementations.

# Bytecode Circuit

Combined training What topics to cover ? How polynomial commitments work How plonk arithmatization works How evm works Hermez is spcificying mul mod. Would be good to multiple specs for mul mod