Topic: [PRE-ANN] INCHAIN. Ethereum based insurance platform - page 13. (Read 27781 times)

Hi dev could you reserve for me italian translation? thanks!

Hmmm insurance doesn't sound interesting enough for people to jump on this boat I guess.

Oracles as the key for insurance via smart-contracts may have additional development problems. Specially with security

It seems for me much more ICOs will take place in future. Good tendency I think.

You are right. Better forget this exchange and don't use.

Thank you sir I will start very soon on it.

TY, preparation in progress, we work with some business advisors to participate in our project
Also, we work on roadmap and escrow clear rules

the second interesting ICO for me in this month. waiting for the dates and further details

Any concrete proposal?

Greek is your)

Lol, guys, you should re-design first tread post.

There won't be any PoW or PoS concepts in this project. Neither there will be any hash rate concept except of the Ethereum PoW itself.

Some explanation about Oracles from our architect Andrey Zamovsky (www.facebook.com/nixoid).

As most of you understand, there is no way for smart contract to fetch any information from outside of the blockchain where it operates. This limitation has been introduced intentionally, and let me explain why. Since every node executes every line of every smart contract, and anyone can submit any smart contract, the entire blockchain network can easily become a weapon of DDoS attack as soon as it allows interaction of smart contracts with external resources.

It is a problem because the code that handles insurance events should be triggered by an events in real world. The solution to this problem is called “Oracle”.

Oracle is a smart contract that contains information about the state of “external reality” (e.g. non-blockchain events).

There are 2 approaches to fill oracle with the information:
Using crowdsourced approach, where any participant of the network can submit the data and get some reward for doing that. (see “Prediction markets”)
Associate the oracle contract with some trusted party, by delegating private key to that party (can be several participants for backup purposes).

The first approach is more favorable by community, however decentralized prediction market is a very complex system by itself and they are currently at the early stages of testing.

The second is more similar to how SSL certificates work: as soon as the originator of the data have announced his public key, anyone can verify the validity of the submitted data.

For example if we wanted to set up an oracle that would report earthquakes (http://earthquake.usgs.gov/earthquakes/feed/), we would:
assign a keypair to http://earthquake.usgs.gov/
Ask USGS to publish their public key (ethereum address) on their website
Set up a special module on the backend that will be submitting every new item of the feed to the smart contract.

We believe that the second approach will still do the job and much easier to start with, so we are planning to go ahead with it.

Or insure their risks))

So, for now we calculate a development and an insurance fund needs, this info will be published when ANN takes place.

There will no cap for the investments, all investments will be distributed to a development (fix price) and insurance fund (remained investments), i.e. more BCT in insurance fund means more abilities to Inchain token holders to invest it and earn ROI, and more stable Inchain decentralise managed bussines.

Thank you)


First, we will use very trusted escrow
Second, we include in the project very seriously business advisors, who care about their reputation
Third, our payments will be very transparent
Fourth, Inchain will have decentralised management model
Fifth, we believe in Inchain

Actually I do not see any reasons to use it.

I would like to reserve the greek translation and i have allready started here https://bitcointalksearch.org/topic/inchain-ethereum-based-insurance-platform-1607220 It will be completed soon

yeah, very suspicious exchange. if someone use it, he/she should be very very careful

I don't think that it is good idea. Here is one of the reasons http://forklog.net/cryptocurrency-exchange-yobit-runs-suspicious-operations/