Yes, replace the byteball directory with the backed up one.

I hope you are learning some foreign language too - I recommend Polish, a riddle wrapped up in an enigma.
/degression

Pilots are going to start bet heavily on the flight delay and intentionally cause delays.  
Jokes aside it may be problematic in case of strikes that cause cancellations pretty often.
Lufthansa cancels 1,700 flights due to pilots' strike

Tonych's bot would be hit by heavy losses if many ppl bought insurance well in advance, especially as you said if anybody had knowledge of the planned strike and bought plenty of insurance. Running this kind of bot requires constant attention to the situation in airlines and other unexpected events like volcano eruptions, heavy snowfalls, tornadoes and the like. Not a part time job but tech can be sold to a company interested in running it with more staff to keep attention and adjust insurance cost in time or even exclude certain flights from the service.

If that happens there's a need for competition so we have more than just one bot like this because if a company starts to run it for profit the cost of insurance certainly will go up. That's why it's important how a new bot is introduced to the Bot Store. People will look there first in search of an insurance bot therefore whoever has a bot in the bot store will have advantage over the others.

Even the order itself in which bots are presented in the Bot Store will have a tremendous impact on the popularity of the given bot and therefore profits of whoever runs it. All this needs thorough reflection on the concept design.

My feeling is that the Bot Store would likely have to be taken outside the wallet app and kept on a website because the wallet app is too small and to difficult to keep updated with the future number of bots and frequent changes that will inevitably happen. Users would likely want to have some form of searching and sorting capability - if there are hundreds of bots it won't be possible to do so inside the wallet app.

Tricky English... Thanks

People like the flight insurance bot. It demonstrates a real usage - the first of its kind in the world actually. Other cryptos are still "working on" this kind of service. 

That's perfect then. No need to do anything just wait for the message to arrive and if the flight is delayed unlock money from the contract. It's a beauty

As far as I know from the flight oracle. But I'm not sure what you need to do to check it in the app. Probably need to chat with the flight oracle - it's in the bot store:

Because there are low risk investments like government bonds and plenty others and high risk "investments" like leveraged derivatives and plenty of others that are no more than gambling.

You need to put the value in a correct format: AB6580 07.08.2017. It works fine:



The price is a bit steep though on this particular flight (20%):

What did you enter as flight details?

You get nothing but you paid nothing as the contract is not set up. I bet you can set up 2 or more separate contracts if you want larger compensation. Did you try two contracts for 1 GB compensation?

It's just 500 USD. A bit poor then. Should allow larger refunds. I bet tonych put this to prevent any excessive bleeding of capital in case his probability calculations don't work as expected or prevent users from mistakes like 10 GB or 100 GB entered mistakenly.

As the screenshot shows you choose what kind of delay you want compensated and with what amount of money. You choose 30 min, 1 hour, 2 hours, or 4 hours or cancellation. You provide  the amount of expected compensation and the bot provides you with the cost of such insurance.

For anybody taking real flights and risking some serious cost associated with flight delay this is an excellent solution to be compensated. No more hassle with airlines about refunds that they rarely provide. Here it is 100% guaranteed in a trustless way. Perfect!

In this way hub becomes along with witnesses another central point of the network open to social manipulation, advertising, propaganda, bribes, cartelization  and of course attacks. We actually don't know how this whole concept will work in the long run. Byteball is smalll at the moment. When/if it grows it will become a target for increased attacks by any vector possible. We need to think about it and ask about it if we want to have any confidence in the system. Nobody in its right mind will put any significant amount of money in the system that raises security questions and is open to attack vectors.

When you establish an insurance contract the bot puts the money into the contract (just like you) and it stays there until the contract expires. So insolvency is not an issue in this case. That's the big advantage of smart contracts. The insurance payment is guaranteed by mathematics and algorithm. There's no way that you won't be paid. That's not the case with traditional insurance companies. They can go broke and not pay their clients.

My question regarding who funds the bot is aimed at providing transparency. Of course the owner of this bot has the right to stay anonymous because it actually doesn't matter if it is run by tonych or ISIS. The bot will work the same in either case because it's mathematically guaranteed. Nevertheless it would be nice if we know.

The other question that arrives is who decides which bot is added to the bot store? If I copy-paste the bot that tonych just opensourced and start running a similar bot will it be added to the bot store automatically? If not, who decides which bot is added to the bot store and which is not?

I assume there needs to be someone deciding, otherwise a bad actor could spam the bot store with copy-pasted bots just to make trouble and cause problems.

All of this comes down to the centralization issue. How much power does any individual has (or can have) over the operation of the network? Decentralization is crucial for the byteball network to succeed but unfortunately on this front we don't know much.

Decentralizing the byteball network will be painful for tonych and it's understandable. Byteball is his baby, he worked very hard for over two years to develop and write the code. Giving up control over this network is like leaving your beloved baby on the mercy of other people. That's is not easy but at some point it has to start otherwise it will continue to be "one man cryptocurrency" - one man is a single point of failure easy to attack by bad (state or non state) actor and destroy the network. We should address this issue if we want to have any hope in byteball to succeed.

"Gamble", "insurance" and "investment" are the words describing the same thing. The difference is only in the probability of loosing. If the probability of loosing is high its called gambling. If the probability of loosing is moderate it's called "insurance". If the probability of loosing is low it's called "investment". The final outcome is affecting the name too.  For example if somebody went broke on an "investment" you will hear people say that he "gambled" and lost. Buying insurance is a gamble too essentially. You gamble on the probability of negative event occurrence. Those who don't buy insurance actually gamble too - on the probability of negative event not occurring.

It's all the same thing but with different names given to it invoking negative or positive attitude of the one giving the name.

Who funds the bot? I mean the bot can be profitable or loosing money depending on the probability and randomness of flight delays. I wonder who will eat the loss or profit?

Yes, you have to relink. The Byteball app has built in backup feature so you don't do a specific file backup but the whole app directory to a encrypted archive file through built in backup feature.

The price continues to crash. Wise people may be selling to secure Bitcoin Cash before 1AUG17.

You are trying to back up full node wallet with the whole history of DAG database. Instead of this make a new Byteball LIGHTWEIGHT installation on a new windows user profile. Transfer all bytes and blackbytes to this new light wallet and backup the light wallet. It will take a few megabytes in size instead of gigabytes.