The project is meant to become something like Uniswap, from the look and feel, for GitHub. Functionality wise it will focus on bounties and their promotion through Twitter. A more detailed description (darft) you can find here: https://github.com/octobay/app/blob/master/LIGHTPAPER.md We planned to submit new features for our project around the topics of this hackathon. Unfortunatley development was a bit delayed/blocked by other priorities and considerations. What was created during this time, is a new Subgraph and two new Chainlink adapters for our project. The Subgraph is just a minimum implementation, with two entities, Issue and IssueDeposit and one event handler for adding new deposits. Fetching the data is handled by our API server with a maybe a bit "quick and dirty" in-memory cache. The Chainlink adapters are being used to let anyone use our Twitter account to tweet an issue and pay for it with a custom ERC20 token. It's a bit "experimental" but the price for a tweet will depend on the number of followers our account has. Therefore the oracle runs two jobs, one for updating the followers in the contract and on its fulfillment the second one, to tweet.
How It's Made
In terms of this hackathon there's not too much worth mentioning I'm afraid. Chainlink adapters are pretty straight forward, simple node/express server. They just connect to a Twitter OAuth app and use their API. The Subgraph currently just listens to one contract event, when a new deposit for an issue is made, and indexes it. No complex graphql magic filter queries or anything making use of it yet. Not even pagination is implemented. 10 issues max! :D