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
Now that #2044 has been merged, my understanding is that the script hash used to invoke a contract is dependent on the original script contents + the address of the contract deployer. Is there a deterministic way of generating the script hash of a contract that hasn't been deployed yet? I'm guessing no.
The text was updated successfully, but these errors were encountered:
@devhawk#2044 change the way scripthash generated, so if different user deploy the same contract script, they will get different script hash. and the scripthash depends on the sender, aka contract deployer.
Now that #2044 has been merged, my understanding is that the script hash used to invoke a contract is dependent on the original script contents + the address of the contract deployer. Is there a deterministic way of generating the script hash of a contract that hasn't been deployed yet? I'm guessing no.
The text was updated successfully, but these errors were encountered: