Timeline for Sign a raw TX without a library?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 17, 2017 at 5:46 | 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. | |
| Nov 16, 2017 at 11:26 | history | edited | Alex Papageorgiou | CC BY-SA 3.0 |
Added clarification
|
| Nov 15, 2017 at 9:16 | answer | added | Richard Horrocks | timeline score: 0 | |
| Nov 15, 2017 at 5:40 | answer | added | Tjaden Hess | timeline score: 2 | |
| Nov 15, 2017 at 3:10 | comment | added | libertylocked | When your contract sends a message it's already signed. | |
| Nov 14, 2017 at 23:17 | answer | added | SteveJaxon | timeline score: 1 | |
| Nov 14, 2017 at 17:09 | comment | added | Alex Papageorgiou | As you correctly assumed, it is a private network so that wouldn't be an issue. | |
| Nov 14, 2017 at 17:08 | comment | added | Richard Horrocks | "...sign a raw transaction within Solidity without gas constraints." - If I understand correctly, then what you're proposing would expose the private key to the rest of the network. Is that going to be an issue in your setup? (Which I'm assuming is a private network.) | |
| Nov 14, 2017 at 16:55 | history | asked | Alex Papageorgiou | CC BY-SA 3.0 |