Closed broody closed 8 months ago
@kariy I've tested the merged changes on dev/katana
, I've now this behavior:
2024-01-09T17:57:28.354771Z TRACE forked_backend: requesting class at hash 0x16c6081eb34ad1e0c5513234ed0c025b3c7f305902d291bad534cd6474c85bc
2024-01-09T17:57:28.356509Z WARN executor: Transaction validation error: ValidateTransactionError(StateError(UndeclaredClassHash(ClassHash(StarkFelt("0x016c6081eb34ad1e0c5513234ed0c025b3c7f305902d291bad534cd6474c85bc")))))
Looks like the forked network does not find the new account account class hash in it's state.
Looks like the forked network does not find the new account account class hash in it's state.
Yes, hence this PR #1404
Looks like the forked network does not find the new account account class hash in it's state.
Yes, hence this PR #1404
Arg sorry, didn't make the match here. Thanks sensei. :pray:
Fixed by #1404, I've tested the steps in the issue and works as expected. Thanks guys!
Describe the bug After forking katana with a world already deployed,
sozo migrate
against the fork with the same build artifacts deployed to the original katana results in error.To Reproduce Reproducible locally and using slot.
katana --disabe-fee
sozo build && sozo migrate
katana --rpc-url http://localhost:5050 --disable-fee --fork-block-number 11 --port 1234
sozo migrate --rpc-url http://localhost:1234
(comment out rpc-url in scarb)Log error
Expected behavior Sozo migrate should complete successfully logging all contracts already deployed.