-
Notifications
You must be signed in to change notification settings - Fork 444
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
How to encode data for appending constructor to bytecode for deploying contract? #86
Comments
From @Mahdimm on August 8, 2018 8:52 Hi @shamatar
such as this encoding on java:
should I do this manually or there is function for this in your library? |
From @shamatar on August 8, 2018 8:58 Hello @Mahdimm There is an example in tests
First of all you need to get an ABI and compiled bytecode of the contract you want to deploy, then construct a transaction using the |
From @MrShafiee on August 13, 2018 14:23 Hello @shamatar
But the response of the request was:
what is the problem? |
From @shamatar on August 13, 2018 14:55 Did you attach a keystore? My example in tests is about deploying a contract with a “remote” signing - when the key is stored on the Ethereum node. If you want to sign locally (on device), just attach a keystore and specify the right account in “options” From: MrShafiee [email protected] Hello @shamatarhttps://github.com/shamatar [{ But the response of the request was: [{ what is the problem? — |
From @MrShafiee on August 14, 2018 13:12 Thanks @shamatar , you are right 👍
and after that, call eth_sendRawTransaction automatically, to deploys new contract. |
Hello. Me and Alex (@shamatar) as main maintainers are moving our development to the new repo. |
Answer: |
From @Mahdimm on August 5, 2018 8:46
Hi thanks for @shamatar you library,
is there any func for encoding the parameter of constructor for adding to bytecode string?
or how we should do this for adding our parameter to constructor (end of bytecode)?
Copied from original issue: BANKEX/web3swift#207
The text was updated successfully, but these errors were encountered: