Builder Bounty Fund & SDK

15% of the total supply of SNR (150,000,000 tokens) will be set aside for targeted builder bounty programs (to be awarded at the discretion of the founding team). The primary focus of this fund will be to encourage other builders to develop new and/or novel solutions for the protocol’s front-end notification service which improve upon or complement the founding team’s front end. Alternate front-ends will have the potential to create new drivers for user onboarding through targeting different user groups, being easier to use, being more decentralised, or simply by offering additional UI options for users.

One example of how this model might work would be a case in which a third party decided to develop a centralised and/or highly abstracted notifications front-end utilising the SCENARIO protocol as a back end. This third party builder would be able to add an additional take-rate as part of their new product or service, and would be rewarded by the SCENARIO team in SNR tokens for bringing additional activity to the protocol. In this example, the Builder Bounty Fund is being used to fast-track adoption by supporting a front-end product that allows retail users to enjoy a fiat onramp and request notifications without having to engage with the self-custodying or on-chain aspects of the protocol. Such users may have no interest in the mechanisms that make the service effective, whilst still seeing great value in being able to generate novel and personalised notification requests that are quickly triggered when needed.

A JavaScript software development kit (SDK) will provide a quick and easy way for third-party developers to interact with Scenario's smart contracts. The SDK will be designed to support both web2 and web3-native developers and allow them to build performant front-ends without having to worry about how best to communicate with the blockchain or have a strong understanding of the Solidity language. All functionality relating to SCENARIO contracts, such as creating, joining and confirming pools, will be abstracted away behind an easy-to-use SDK.

Initially, the builder bounty fund will also be the recipient of 50% of any slashed SNR in instances where users are penalised for dishonest pool resolutions. Once the protocol has reached maturity and the founding team’s involvement has reduced or ended, slashed SNR will instead be redirected to SNR stakers.