Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #404
Data Oracles are a new way to access data directly on chain. This allows users/smart-contracts to request a specific chunk from a file on the network and for a "finders fee". Data-oracle relayers can then scan the chain for new requests and get the file from storage providers, upload the specific chunk to the network along with a proof just like a traditional storage provider. This then uploads the chunk of the file directly to the chain which can then be accessed by smart contracts or users without going off-chain. The "finders fee" functions as a marketplace model, so there are no guarantees the file chunk you want will be put on chain. If you are an app developer you can run a dedicated machine that will run for cheap with whitelisted wallets or files.
The digram below is a visual guide of what this system does:
The roadmap would include the ability to request data from providers, but also propose edits to files and have oracles commit those edits to the files directly on chain.
For updating data directly from the chain the workflow would look something like this: