Public Oracle System

Public oracle system has been designed to simply obviate requirements from external data that the validity of data or proving the validity of data is not that important for user. Of course in this method various kind of proofs will be provided to resolve proof of validity of data in a near future.

Public Oracle Data Sources

Data sources are various kinds of references such as a website or a web API from which required data is requested by oracle data carriers based on users’ needs. One should note that each data source has a special use case and functionality and choosing a suitable data source is of great importance. There are several critical data sources that are expected to exist in Bridge oracle system. Various data sources that are supported by public oracle system include:

URL: URL data source enables users to fetch every kind of data using http/https request APIs into their smart contracts. This data source supports both http/https GET and POST requests. If only one parameter is sent in the query, the request will be considered as a http/https GET request, automatically. Otherwise if a second parameter is sent through query, oracle will treat it as a POST request.

Complex URL: This data source is similar to URL but a little more flexibility for fetching data.

WolframAlpha: This data source redirects users’ requests and questions to computational knowledge engine of WolframAlpha Company which is able to answer what one wants to calculate or know about. WolframAlpha computational intelligence answers the inquiries and corresponding responses are returned to the users’ smart contracts.

Random: This data source generates random numbers. Random number has many critical use cases including statistical sampling, computer simulation, cryptography, completely randomized design, scientific calculations, etc.

BTFS: BTFS (BitTorrent File Sharing) is decentralized storage system of TRON network. Using this data source, enables users’ contracts to be able to interact with the file storage system.

Nested: This case enables users to utilize the combination of different types of data sources or multiple requests of the same data source that returns a unique result.