Vision, Resources & Decentralisation
Whilst it is possible to build a crypto notifications platform as a centralised service on web 2 infrastructure, doing so would restrict the platform’s modularity and scaling potential, and possibly run counter to the values of its initial user base. As a protocol that will initially be used by crypto natives who value trustlessness, permissionlessness, security and ownership, it is crucial that SCENARIO aligns with these values and is designed in a way that allows for it to be composable with other decentralised applications.
With its underlying logic running on a decentralised compute layer, SCENARIO will be able to grow in step with demand. Globally dispersed, engaged and economically incentivised users will act to reach consensus on event occurrences and trigger notifications in response to user requests. The protocol’s event data will be transparent, provably crowd-sourced, and open to use by other platforms and builders.
As is the case with protocols such as Uniswap, SCENARIO smart contracts will be immutable once fully deployed. In addition to ensuring liveness, transparency and auditability, this will also allow for community members, Dapps or businesses to build their own front-ends or related applications in order to harness (or add value to) the underlying infrastructure. The protocol and its founding team will explicitly encourage the development of alternate front-ends and novel business models which leverage the core contracts. These contracts will serve as public goods that continue to generate data without an ongoing need for developer intervention at the protocol layer, leaving further innovation to occur at the user interface level.
At scale, a decentralised model for crowd-sourced agreement on what has happened or what is true is also the most robust, and is further strengthened when such agreement is directly connected to crypto-economic incentives which reward honest user behaviour and make dishonest responses unprofitable and increasingly difficult to repeat.
Scenario is...
A battle-tested, immutable set of smart contracts
Accessed by...
A broad network of two different participant types
Who are...
Economically incentivised to keep the service running
Creating a...
Decentralised and open base layer 'protocol-as-a-service'
On top of which...
Third parties can build and create
Allowing them to...
Further harness and monetise the protocol or offer second-layer services