Inspiration
Our inspiration came from a shortcoming we noticed as first-party oracles. The same data-point needed to be on-chained severally since different parties could not reuse a data-point from a single on-chaining transaction. In addition, there was no record of on-chained data to make smart contract auditing easy.
What it does
Our implementation uses the Filecoin decentralized storage system to store metadata of all requests fulfilled by the Shamba geospatial oracle. It saves both the request and response parameters from an oracle transaction.
How we built it
We built the external adapter using JS and deployed it to a virtual machine on Digital Ocean. The adapter saves oracle metadata into IPFS. The UI is built using bootstrap and deployed on Heroku.
Challenges we ran into
A few challenges with hacking the Chainlink external adapter and jobSpec to enable the data capture and storage on IPFS during the oracle request-response cycle.
Accomplishments that we're proud of
Building an implementation that will make it easier to audit smart contracts post-execution. Particularly useful for applications that work on things like carbon markets and would like to provide transparency on the science behind their carbon credits to users. We are proud that this implementation advances transparency on Web3.
What we learned
We learned a fair bit about the IPFS and the Filecoin system and are eager to continue building out on top of those platforms.
What's next for Oracle Metadata Storage App
We will seek support to advance and extend this implementation into a full application and part of the Web3 protocol we are building around geospatial analytics.
Built With
- chainlink
- filecoin
- ipfs
- javascript
Log in or sign up for Devpost to join the conversation.