Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Oracles - external data carriers for decentralized apps #111

Closed
fjrojasgarcia opened this issue Jan 21, 2018 · 9 comments
Closed

Oracles - external data carriers for decentralized apps #111

fjrojasgarcia opened this issue Jan 21, 2018 · 9 comments

Comments

@fjrojasgarcia
Copy link
Contributor

For me it would be important to mention in the book the inherent isolation of Ethereum from the outside world and the importance of defining mechanisms, commonly called Oracles, to achieve its interaction with it.

There is already some initiative trying to cover this limitation, such as "http://www.oraclize.it".
They define themselves as the "data carrier for decentralized apps".

Maybe there is something more about it out there.

@Benudek
Copy link

Benudek commented Jan 21, 2018

It seems to me it might be fair to discuss the need to have oracles is also an inherent obstacle for smart contracts to cover without further consideration non digital assets. If a smart contract does sth but the assumptions it has on the world the smart contract might overall be useless or open to manipulation. With digital assets like currencies e.g. Ownership can be proven with cryptography. Owning a car or facts like the weather or who caused an accident, need to come to smart contracts via oracle. This unsolved limits the usecases for smart contracts so far. In my humble opinion :-)

@dzwiener
Copy link

Auger would be a good token to explore as well since it proposes it will change the way how oracles operate.

@fjrojasgarcia
Copy link
Contributor Author

I agree that the inherent isolation of Ethereum, or any other decentralized system, is a feature and not a bug. The thing here for me is more about the impact of the innovation power in this field.

As Andreas has helped many of us to understand that the power of innovation transcends unimagined boundaries, I think that probably at this very moment there are a handful of brilliant minds working on this matter and I would not rule out the arrival of some surprising solution.

Perhaps it would be good if the book considered this aspect and that future readers had at least some notion and created their own criteria in this regard.

That's my humble opinion also :-)

@aantonop
Copy link
Member

Agree, it is important to explain both the security model which depends on isolation, versus the need for Oracles to achieve many real world use cases.

Where does this fit in the list of topics?

@wbnns wbnns assigned wbnns and aantonop and unassigned wbnns Jan 24, 2018
@topitsky
Copy link

I think before we can have oracles, we first need immutable, trustless sensors.

@Pongch
Copy link

Pongch commented Mar 27, 2018

I believe this could fit pretty well into DApp section of the book. Since the outlines already explaining off-chain & on-chain Data. We could explore the reasoning behind oracles, then going into its limitations, current & possible implementations etc.

@timnugent
Copy link
Member

The draft text for oracles is in the contrib directory. One possible issue with putting this within the Dapps section is that oracles are not necessarily Dapps themselves

@Pongch
Copy link

Pongch commented Mar 27, 2018

I see, I wasn't aware the content for oracle is already being written. Come to think of it, Oracles and getting off-chain data as a topic is important enough to deserve its own section in my opinion.

@aantonop aantonop added this to the First Draft to Tech Review milestone Apr 6, 2018
@aantonop
Copy link
Member

aantonop commented Apr 7, 2018

Great work on this topic. See contrib/oracles.asciidoc. It will be included in the first edition

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants