ICO protection in real life

Let’s imagine that owners have decided to develop and maintain their own solution to run an ICO. First of all, there should be no private keys. Just forgot about them. During the ICO owners mustn’t use any private keys on production server. If server will be compromised, no funds will be lost. This is the main issue of product owners during ICO — keep investments safe. No private key — no possibility to stole the coins.

The main issue is solved, then move to another one. Server should run 24/7. It’s more complicated job, but there are a lot of tools for this purpose. The main idea is that all data have to be replicated. Database should be copied to another server or several servers as frequently as possible. The same is to web server. Owners should be able to switch another server in few seconds to continue running the site if something wrong. Load should be balanced between several servers. Also there should be anti DDoS tools running.

All have to remember, downtime may be reason of losing of investments for thousands dollars or falling down project reputation. Anyway, ICO should be online from start date to end date. No delays, no downtime, no private keys. All have to be replicated, balanced and ready to change context.

It will cost much enough, but less than you may lose if something happens outside your control.

Be attentive, and have a profitable ICO.

Related posts:

The article aims to explain how to vote with GTON, the governance token, for approving or rejecting a certain governance proposal for the Graviton system. Please note that before attempting to vote…

For the vast majority of my life I’ve criticized the concept of religion harshly. In my eyes, each were founded on fits of fantasy and irrational “faith” or superstition (though, some more egregious…

Cheney Meaghan is a single mom and writer from Connecticut trying to make a living with her words. You can support her best by clicking here to sign up for her email newsletter.