Categories
- 17.3K All Categories
- 9.5K Mining
- 574 Pool Discussion
- 378 Promotional
- 1.4K General Project Discussion (non-technical)
- 485 Education
- 811 Protocol and Client discussion
- 170 web3-js
- 29 Whisper
- 16 Swarm
- 3 RLP
- 303 IoT & Hardware
- 1.2K Smart Contracts and Dapps
- 28 Serpent
- 359 Solidity
- 664 Projects
- 1.2K Reference clients code and builds
- 249 Eth & AlethZero- Cpp Implementation
- 471 Geth - Go Implementation
- 242 Mist
- 15 Node.js Implementation
- 36 Python Implementation
- 49 Mix
- 36 Other Implementations
- 170 Meetups
- 40 Other Events
- 226 Jobs & Skills
- 281 Press and Articles
- 75 Audio/Video
- 296 Ether Sale
- 1.2K Other Languages
- 96 Chinese
- 255 German
- 33 Italian
- 111 French
- 3 Hebrew
- 42 Japanese
- 75 Portugese
- 46 Romanian
- 185 Russian
- 231 Spanish
- 47 Turkish
- 125 Watercooler
TIPPING ETH for Web3js Security Advice
WhiteOutMashups
Kuala Lumpur, MalaysiaMember Posts: 5 ✭
in web3-js
Hey guys I have another general question for some more ETH tips 
If we are running a script that sends transactions automatically with web3js on a server, then what are some of the best practices for keeping the private key safe? We need to have it on there to do the signing, but what is the gold standard, reccomended way of keeping private keys like those safe?
It would be very annoying to have to re-issue all the coins all over again to the investors, if the token private key got hacked, and might look bad. No money would be lost, but it would give us a bad image.
We have created an idea, where we keep the private key on the server, encrypted, and we use https and a private, WPA2 secured Wi-Fi connection to make the API calls from. Would you think this suffices, in terms of security? Thanks.
So please leave some server / private key security tips here with your ETH address and we will tip some ETH if it is relevant and helps, Thanks!
If we are running a script that sends transactions automatically with web3js on a server, then what are some of the best practices for keeping the private key safe? We need to have it on there to do the signing, but what is the gold standard, reccomended way of keeping private keys like those safe?
It would be very annoying to have to re-issue all the coins all over again to the investors, if the token private key got hacked, and might look bad. No money would be lost, but it would give us a bad image.
We have created an idea, where we keep the private key on the server, encrypted, and we use https and a private, WPA2 secured Wi-Fi connection to make the API calls from. Would you think this suffices, in terms of security? Thanks.
So please leave some server / private key security tips here with your ETH address and we will tip some ETH if it is relevant and helps, Thanks!
Comments