Scenario Protocol
Separate signal from noise. Decentralised alerts.
About
The problem it solves SCENARIO lets you request specific alerts on ANY topic, using a simple, intuitive interface. This means you can finally separate the signal from the noise by reducing notifications traffic from 100s or 1000s of irrelevant pings to just the 5 or 10 that you actually need. Simple. How does Scenario do this? - Define your alert (or join an existing request). - Pay a small fee... Then step away and relax! - Other tuned-in users will trigger the alert when the time comes, and claim a bounty for their work. Powered by onchain consensus. Useful and easy to navigate for anyone. Scenario solves some of the biggest problems faced by web3 users (and the broader public) today: information overload, overcrowded social feeds, countless irrelevant alerts, burnout, and missed opportunities. Currently, if you want to know when something specific happens in the future - be that the release of a project’s new product or feature, a liquidation risk in DeFi, an NFT mint, or even an injury to a specific player in fantasy sports - the only way to hear about it is by following a whole suite of platforms and channels. Worse still, you can be sure that even after doing so, 99% of the pings you get won't be about the specific things you’re waiting to hear about! In a world where nearly 3 billion people receive push alerts but ultimately opt to unsub due to irrelevance, Scenario addresses a huge market need by using crowd-sourced information to trigger alerts *only* when user-defined events occur. You don't need more alerts - you need the RIGHT ones! Team - Steve Merry: Co-founder and Product Lead Crypto-native since 2018 and forged in (at least) two bear markets. More than fifteen years of experience in business development, project management, communications and partnerships. Successfully founded and scaled an entertainment business to 100,000+ fans/followers. Explorer of DeFi from its inception, and a believer in the broader vision and ambition of Ethereum. Andy Lower: Co-founder and Tech Lead Previously solo-founded and developed a Shopify ecommerce business. Successfully exited via company acquisition. 10+ years experience as a full stack developer. A skeptic of many blockchain-related projects, but a believer in the power of consensus-based systems and the importance of decentralization.
How it's made
Challenges we ran into **Time Pressures** As we built out this showcase feature, the obvious initial challenge was the time pressure of the hackathon itself. We worked at managing this by continually reviewing the scope of what we intended to build, limiting features where needed. **Wallet API V2** As we created the on-chain reputation and bonding mechanism for our scenario confirmation mode, we encountered some genuine challenges with the Wallet API V2. As the smart wallet API was itself still in alpha, we found that error messages were often being thrown when connecting to Paymaster for gas sponsoring. We resolved this as best we could by liaising with the Base team on discord. These issues continued to present sporadically until the final day before project submission. Another interesting challenge for us was the fact that we needed to think carefully what we would focus on and change immediately following our Base Batches submission; the version we are submitting has many features we plan to quickly iterate on further - but we needed to break those off, accept that the hackathon submission was time-boxed, and be comfortable with the idea that the product would continue to be refined after submission.