Timeline for Deploying smart contract programatically from web3 / nodejs
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 2, 2017 at 12:24 | answer | added | Subhod I | timeline score: 0 | |
| Aug 22, 2017 at 18:47 | vote | accept | mcansado | ||
| Aug 18, 2017 at 0:52 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 19, 2017 at 7:35 | comment | added | mcansado | It would be more convenient because that way I could have contracts directory as part of the node app with all contracts in it. But what would you propose as the alternative? | |
| Jul 19, 2017 at 3:39 | comment | added | Midhun Mohan | Is it necessary to read the contract from a file? if contract is not changing you can avoid onfly compilation. | |
| Jul 18, 2017 at 22:25 | comment | added | Alexey Barsuk | Check compilation results for errors if (output['errors']) { console.log(JSON.stringify(output['errors']))} | |
| Jul 18, 2017 at 21:01 | answer | added | thefett | timeline score: 0 | |
| Jul 18, 2017 at 19:56 | answer | added | Chris Prinz | timeline score: 0 | |
| Jul 18, 2017 at 18:09 | history | asked | mcansado | CC BY-SA 3.0 |