SSO Contracts - Create2 for Account Deployment

[4NNNN]

Account Implementation can't be deployed using normal create2. If that's the case, the account would be treated as a normal contract rather than an create2Account deployed "Account".

This wasn't possible before because if the account is a normal contract, any call to the proxy of the account would end up in "touched disallowed storage slots revert". Did you guys go for a testnet simulation and how is this possible now?

[4NNNN]

Account Implementation can't be deployed using normal create2. If that's the case, the account would be treated as a normal contract rather than an create2Account deployed "Account".

This wasn't possible before because if the account is a normal contract, any call to the proxy of the account would end up in "Untouched storage slots revert". Did you guys go for a testnet simulation and how is this possible now?

639

[4NNNN]

@JackHamer09 The question context revolves around SSOAccount deployment. I wanted to know, how did you guys achieve to bypass "untouched storage slot revert" and what exactly was causing it!

Server whitelisting is the last call - What made you guys whitelist few contracts of the SSO codebase and why couldn't you guys figure out the storage slot reverts. It would be nice if you give us specifics, because we're working on it as well!

[JackHamer09]

I'll try to get more details about that and get back to you

[JackHamer09]

Hey @4NNNN
Whitelisting is needed so that accounts can read their implementation address from the beacon during validation.
This happens because of some very strict security rules, but I think this should change in future protocol versions.
You can also read more about this here: https://docs.zksync.io/zksync-protocol/account-abstraction/extending-4337#extending-the-set-of-slots-that-belong-to-a-user

[4NNNN]

@JackHamer09 Figured, I just replaced beacon proxy implementation with a 1967 proxy implementation.

[XinyuCRO]

Hi @JackHamer09 , seems that adding SessionKeyValidator, WebAuthValidator, SsoBeacon addresses to the paymaster access whitelist is not enough, can I know the full address list when deploying the whole zksync-sso setup to a zkstack chain?