I think it will end much faster than 1 hour! Maybe 20-30 mins

Is there a specific gas price/gas limit requirements in the contract?

So I have a few technical questions if I may on the blockchain technology, and how it fits into insurex:

As I understand (and please correct me if Im wrong), confidential private insurance information won't be stored on the blockchain itself, but in the Nosql storage instead? So things like pricing, parties involved in an insurance deal, addresses and contacts of people will be stored in Nosql and not on the blockchain?

But everything else data wise will be written onto the ethereum blockchain? So things like:

- the whole marketplace where people buy and sell (with smart contracts implemented)
- actual insurance contract information
- terms and conditions for insurance contracts which can be issued via smart contracts (like Corda is able to do for banks now)
- portfolio info
- analytics

So what you're doing is having a hybrid..where some data is on ethereum, but other data is kept on a normal database, and the two meet together in an UI, built on normal application languages (node.js etc).

So the follow on question then would be: what type of backups/redundancy or contingency plans will you have if the ethereum network has issues? For example, bottleneck issues which we've seen recently. If a lot of data is purely on ethereum, and ethereum slows down or has other problems (which is possible because its still a third party and a work-in-progress), companies wont be able to access what they want

In essence, how are you ensuring data integrity and the ability to access the information a company needs on insurex in case something goes wrong on the blockchain or somewhere else?

What are your anticipated insurance transaction volumes on the insurex platform once the concept takes off? Because ethereum at the moment is showing some slowdown at 300,000 transactions a day (obviously that will improve with updates)

I would think some insurance companies would also want to use a sidechain to store their insurance information. So have their own private blockchain maintained in the cloud which covers all its sensitive information etc instead of a centralised nosql concept. So they would get the benefits of blockchain, but also keep control over their data in case things go wrong with a more standard public blockchain tech like ethereum

Im thinking something like Factom's blockchain technology to store insurance information as an add-on to insurex would also be good, so data is stored securely in an independent way, but also a smart way.

So..insurex is a great concept but I have some questions there....it doesnt say enough in the whitepaper about the extent of the blockchain implementation and whether everything's been thought of in regards to contingencies and how the control, safety and security of the data on it will work

You guys are running all this on your own servers, people have to trust you guys to keep the servers running this is not decentralized where people are running the network. The coin is payment to use your guys' service. This is a centralized network where you guys hope people will use your service and then pay you, then I'm guessing you guys will sell that back to the market. Is this right? I see why this project is not getting much support. Crypto goes hand in hand with decentralization, people own the network that way corruption can never occur. Corruption occurs due to centralization, sorry but you guys are a centralized organization creating a centralized project. NO THANKS.

is the upgrade to wallet v. 2.0.0.3 mandatory or will it be possible to upgrade from v. 2.0.0.2 direct to the Breeze wallet when it's released?

That is correct I did that and it worked. Create a transaction to yourself to claim the intrest

D/loaded and installed Komodo GUI Wallet for WIN - v0.7.8

specifically, the komodoGUI_setup.exe on https://github.com/ca333/komodoGUI/releases

started the wallet app and 1st process to appear on the screen was 'Verifying the proving key' followed by 'Loading block index' after ~ 20 seconds of which the following errpor message appeared:


How do I check that the server is running and that I'm connecting to the correct RPC port?

How do I check the 'console output'

Thanks for any help

[  --- ]

You can add more nodes from here: https://espstats.net/nodes/
The bootstrap have 481 MB is size. (also can be dawnloaded from espstats.net.

.

A general unexpected critical error has occurred.
Error: couldn't connect to server: EOF reached (code 1)
(make sure server is running and you are connecting to the correct RPC port)
See the console output for more detailed error information!

Thanks polycryptoblog and Komodo for replies.



I've downloaded and installed the Windows version of the Komodo Swing wallet

Which of the various application files (e.g. komodo-cli and komodod) do I click on to run the wallet?

Thanks.

It is enough that you control the privatekeys. You don't have to use any particular wallet. You could just have an offline wallet and you would still receive the JUMBLR asset.

P.S. we did also release alternative KMD wallet: https://supernet.org/en/products/komodo-swing-wallet

[---]

You will be able to easily exchange tokens from each blockchain at a 1 to 1 value at anytime using smart contracts we have already designed.

https://mobilego.io/frequently-asked-questions/

Well looks like a lot of you guys decided you can't take the rise and dumping now. I wish I had my buy orders set in further down, I should have known whenever everyone here talks about STRAT going up 100 times, it always takes a dump..Oh well I am holding for the longer term so will not be phased by the the numpties.