Incentera

• 

  Incentera Landing Page

• 

  Incentera Dashboard

Inspiration

Independent humanitarian organisations are facing an increased need for volunteers in response to extreme weather events and other public health crises due to increasing frequency and severity. The glink team have friends working in this type of environment and are familiar with challenges they face. We have been thinking of ways to leverage node infrastructure for real world applications in support of these organisations, almost like RICO but for public good.

What it does

Incentera creates jobs based on public health warnings delivered by the NINA API via DirectRequest and incentivises participants to assist independent humanitarian organisations in fulfilling these jobs. Governments, philanthropists and local communities are able to financially back initiatives of their choosing, further incentivising jobs about which they care. Incentera is built on a reputation mechanic, with stake and reputation requirements for randomly selected participants varying depending on the severity of the job, and awards an additional incentive base on an inflation rate polled from Truflation every 24 hours.

How we built it

The glink team have expertise in running Chainlink oracle node infrastructure, created the DirectRequest job specification and handled polling of the NINA API. 81k provided expertise in smart contract development, writing Solidity code and deployment scripts using the Foundry toolchain.

Challenges we ran into

Given the nature of data to be consumed, we were not able to rely on a disaster occurring on-demand and so had to mock the API response for testing purposes. On the operational side, there was illness and personal circumstances to contend with which made it a challenge to juggle hackathon commitments alongside normal business operations for continued running our respective startups. We believe the Chainlink hackathon is an excellent testing ground for new ideas and collaboration – this was successful between our respective companies, although not so positive when evaluating new external contributors. Given these challenges, we were not able to complete integration of the contracts with a front-end user interface within the time constraints.

Accomplishments that we're proud of

We are pleased with the core structure of protocol smart contracts and focus on reputation as an addition to a financial incentives. We are also very proud of formulating the idea for a unique use case which has the potential to impact large parts of society once further built-out.

What we learned

This was the first time the glink team has used AnyAPI and found it to be straightforward. We further developed understanding of modular smart contract architecture and, although not directly implemented here, attaching library logic to structs. We also spent some time beginning to learn Remix as an alternative React-based front end framework.

What's next for Incentera

Rather than relying on a single oracle node, we plan to build a DON for monitoring of API updates and add additional observation sources. We would also like to further explore the arbitration capabilities of our contracts and the respective oracle networks which we anticipate will be required. We envision multiple layers of arbitration as to the value of a participant's contributions, both data-driven and subjective, so plan to continue exploring the design space of hybrid smart contracts in which social context is important. We would also like to further refine the economic design and move to increased off-chain computation.

Built With

• fly.io
• foundry
• nina-api
• react
• remix.run
• solidity