-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Constructor parameters not being deployed on the blockchain #1118
Comments
@chriseth The encoded constructor arguments are as follows in web3.js
Is this correct? |
@frozeman @chriseth @Pris17 It worked after I downgraded to a lower version. 1.0.0-beta.19 to be precise. The constructor parameters were initialised on the deployed contract. There must be some issue with beta.23. |
Looks like this is fixed now. I tried it and everything worked as expected on |
Yes, it worked in the version mentioned above. |
@pubkey @sma1692 @chriseth @Pris17 @frozeman
It gets deployed here , but it says TxReciept Status failed, can anyone tell me whats the issue here ? here are the transactions |
@sathyamlokare Please ask your question on https://ethereum.stackexchange.com/ |
I have written a js script wherein I am trying to deploy a contract from an externally owned account (the address does not belong to eth.accounts but is generated by a separate script). The contract gets deployed however the constructor parameters aren't set. Following is my code for the same. There is no issue with the nonce. I change it periodically.
The contract gets deployed there is no issue with that but somehow the values aren't initialised. I tried a few versions, where I add the parameters and use encodeABI() after signing but nothing works. The version I am using is 1.0.0-beta.23. How do I resolve this?
The text was updated successfully, but these errors were encountered: