You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ContractIDByNodeIDAndHash storage map should not reference not existing node contracts.
Also, if such contract exists, the deployment hash in key should be same as deployment hash in contract
Seen on devnet:
ContractIDByNodeIDAndHash key [node: 34, hash: "b076d2fcefdbe02f9902870860a66e91"] gives contract id 16672 and this contract does not exist
ContractIDByNodeIDAndHash
storage map should not reference not existing node contracts.Also, if such contract exists, the deployment hash in key should be same as deployment hash in contract
Seen on devnet:
ContractIDByNodeIDAndHash
key[node: 34, hash: "b076d2fcefdbe02f9902870860a66e91"]
gives contract id16672
and this contract does not existContractIDByNodeIDAndHash
key[node: 28, hash: [128, 48, 56, 48, 97, 52, 54, 51, 49, 50, 100, 52, 54, 50, 102, 54, 50, 97, 52, 52, 97, 99, 48, 97, 54, 100, 53, 48, 98, 99, 99, 52] = "�080a46312d462f62a44ac0a6d50bcc4"]
gives contract id3768
and the deployment hash in this contract[48, 56, 48, 97, 52, 54, 51, 49, 50, 100, 52, 54, 50, 102, 54, 50, 97, 52, 52, 97, 99, 48, 97, 54, 100, 53, 48, 98, 99, 99, 52, 52] = "080a46312d462f62a44ac0a6d50bcc44"
does not matchThe text was updated successfully, but these errors were encountered: