-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Predeployed account not supporting interface ID of OZ 0.8.1, subsequent deployed accounts support #422
Comments
Notes:
|
|
UpdateThe problem is in the way we initialize predeployed accounts. We don't really execute their constructor logic, we only set the public key in their respective storage. But when an account is deployed manually using a Actual Constructor Logic (Cairo)Devnet Constructor Simulation (Wrong)starknet-devnet-rs/crates/starknet-devnet-core/src/account.rs Lines 108 to 125 in 47ee2a7
Solution ProposalI'll probably deal with this by adding the remaining constructor logic simulation, i.e. do a direct write instead of calling self.SRC5_supported_interfaces.write(interface_id, true); I'll also expand the tests. But I can only continue working on Thursday. |
Describe the bug (observed vs expected behavior)
on devnet at commit : 6a51d04, the predeployed accounts with open zeppelin version 0.8.1 dont support this interface id
however other accounts deployed after devnet is started , with the same class hash, they do support the interface.
Not reproducible on testnet
To Reproduce
Steps to reproduce the behavior:
starknetjs@6.7.0
Devnet version
System specifications
The text was updated successfully, but these errors were encountered: