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

Agent Oraclization #32

Open
ldub opened this issue Aug 11, 2018 · 2 comments
Open

Agent Oraclization #32

ldub opened this issue Aug 11, 2018 · 2 comments
Labels
enhancement New feature or request

Comments

@ldub
Copy link

ldub commented Aug 11, 2018

Agent Oraclization, or the ability to allow third party smart contract to use SingularityNET services (hosted offchain) as oracles, requires changes in the platform-contracts (singnet/platform-contracts/issues/28) as well as changes in the daemon itself to become an Oracle.

@ldub ldub added the enhancement New feature or request label Aug 11, 2018
@ferrouswheel
Copy link
Contributor

Am curious... does "Oracle" have a specific meaning in the blockchain world? Or is it our own definition for exposing SNet services to external smart contracts?

@tiero
Copy link
Collaborator

tiero commented Aug 20, 2018

The blockchains in general have limited or zero external transport capabilities, resulting in tiny surface of attack wich is good, but also no way to gather data from outside. The concept of oracle can be trustful (such as just an API of third party). The problem is that if the API changes or disappear, the smart contract will not behave in a deterministic way for the same input. Some provably honest solution are out there, for example take a look at oraclize.it

anandrgitnirman pushed a commit that referenced this issue Feb 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants