Project name: Scry
Author name and contact info (please provide a reliable point of contact for the project):
PR0 pr0@keychain.me
L2 recipient address: 0x9D31e30003f253563Ff108BC60B16Fdf2c93abb5
Which Voting Cycle are you applying for?: 11
I confirm that I have read the landing pages for the Builders and Growth Experiments Sub-Committees and that I have determined my proposal is best suited to be reviewed by the Growth Experiments Sub-Committee: [Yes/No]:
Yes
I understand that Growth Experiments grants are subject to a “no sale rule,” as explained in this post, and I have read the terms of the rule: [Yes/No]:
Yes
What are you building?:
Scry is an open source, permissionless, flexible and robust framework for Oracle deployment with multifeed support, subscriptions and instant deployment. We are the ONLY permissionless oracle infra that allows anyone to run their own oracles and nodes with own signers and data.
Scry has deployed the Open Oracle Framework, an infrastructure for oracles for developers to access external data in a fully permissionless and decentralized way. The infrastructure allows devs to deploy high scale oracles for any API with the contracts, nodes and front end all ready to use in <15m. This allows devs to create oracles using their own reputable signers in their communities or use a reference oracle by the Scry team to request data to be brought onchain.
The factory allows easy oracle deployment by devs without even needing to deploy a contract using hardhat themselves.
The infrastructure is fully decentralized and the ONLY protocol in the space that allows devs to deploy their own oracles and control the oracle and feeds fully using their own security/signers/feed sources, as well as wrapping this into a very simple process to allow for rapid deployment and usability. The node/front end and contracts are all open source.
We also have built out Morpheus
Morpheus is a framework that allows developers to request any API from web2, directly onchain for their web3 apps. This tool enables real-time data requests, any API and data to be used, and can be used on any EVM network. Morpheus has been designed to make it easier for developers to build decentralized applications that can interact with the real world, thereby bridging the gap between web2 and web3.
One of the most significant advantages of Morpheus is its ability to access any API endpoint. This means that developers can now easily request data from sources such as social media platforms, weather APIs, and financial data APIs directly on the blockchain. This makes it possible to build applications that are more relevant to the real world such as insurance, synthetics, social dapps and that can provide more value to users.
HashRanCh, a VRF (Verifiable Random Function) from Scry comes in, providing a secure and verifiable method for generating random numbers in smart contracts. HashRanCh hashing process provides a secure and verifiable method for generating random numbers in smart contracts. By using the private key as the seed and computing a sequence of hashes, we can ensure that the data being used is tamper-proof and cannot be manipulated by the oracle aswell as being guaranteed random. This is crucial for applications that require randomness to function, and ensures that the integrity of the entire system is maintained while decentralized. Hash RanCh was custom designed by the Scry team through our RnD as a fully secure cryptographic base for any and all projects to use, with verifier open source.
Our key mssion
Data LPs (Data Liquidity Providers) are essentially decentralized marketplaces for data. They provide a way for developers to source data from a variety of different sources, while also providing incentives for individuals and entities to contribute their data to the marketplace. In a Data LP, anyone can contribute their data and earn rewards for doing so. Developers can then purchase the data they need from the signers they choose. Scry is a pioneering a decentralized and open market data approach with Morpheus that allows anyone to easily set up and operate their own oracle and node with no technical expertise.
By enabling anyone to fill requests for data, Scry allows developers and projects to choose where they source their data based on reputation for who they feel will be honest, as well as even source the data from their own community.
Why do you believe what you are building is going to succeed?:
Optimism is severly underserved by other oracle networks such as Link, with not even 50 feeds by the largest oracle providers, with all being provided by only a few signers, creating not only limited data for devs and projects but all being unable to be custom for projects with their own data sources to ensure security and ability to deploy new feeds and scale.
Oracles key features
- Autonomous oracle system where devs can self deploy own feeds/oracles and use custom signers for permissionless, decentralized and secure deployment with self-controllable feed creation using custom APIs for rapid development
- Use any API with a highly robust parse engine, the parse for the json to be expected and basic info and the feed will be ready to use and submitted on chain by all signers.
- Data lookup for historical data for all feeds natively, allows for both immutable data access, TWAP construction and onchain analytics.
- Allows for various monetization structures at a feed level, oracle providers can charge for certain feeds to earn revenue as well as provide others for public use, subscription models for data requests at the feed level and oracle level.
- Anyone can run a data provider and earn fees from requests
-Creates a data market and lets devs choose their oracle sources at the signer level and batch many for redundancy - Any API endpoint in realtime for any data
- Custom highly secure VRF with simple verification
- 0 Code setup and deployment, takes <60s to set up and have an operational node
- Out of the box nodes, contract deployment and verifiers and front end
The data available to devs directly limits use cases which can be deployed, you can’t deploy insurance without data about whats being insured, you cant deploy financial markets thats not crypto exclusive without access to traditional finance data. By allowing high scale, easy to deply oracles that supports new feeds in real time, projects can scale not just the transactions with L2s but the capibilities.
How many users does your project have currently? Please include how you arrived at this estimate:
Unknown as we support testnets as we are not officially launch as well as having our framework and tools designed to be self deployable. We have confirmed multiple projects that are trying out the infrastructure for their projects. We support 7 networks currently.
How will receiving a grant enable you to further the mission of maximizing the number of users interacting with Optimism? Please include a step-by-step flow of how you imagine this grant can lead to a greater number of user interactions with Optimism:
The tokens will be used towards helping more data providers set up and operate oracles as well as help with gas costs for oracles and users. This allows for more data to enter the chain and so more tools and projects for users. This may be decentralized insurance, finance, social allowing them access to any web2 data they need either through requests or pull based oracles.
Tokens used to subsidise more data>more tools and use cases>more users able to use the tools and more use cases. If theres more data on Optimism and not on other chains devs will focus on Optimism and so there will be more tools that are only available on the platform.
Tell us about the users you plan to target with this grant. Include any defining characteristics that will help you identify and target them.:
Developers an projects, specifically those with need to access external data, specifically defi projects, insurance, analytics, but depends on the use case.
How would these users interact with Optimism? For how long?:
Developers build the tools you need to attract end users. Developers often stay for many cycles, even through bull and bear markets and are key to keeping users and growth.
Provide us with links to any of the following for the project:
-
Demo:
optimism.dapp.scry.finance
Deployments - Scry Protocol -
Website:
https://docs.scry.finance -
Twitter:
https://twitter.com/ScryProtocol -
Discord/Discourse/Community:
Scry Protocol -
Github:
ScryProtocol · GitHub -
Technical/Economic Documentation:
https://docs.scry.finance -
Other:
Who are your competitors, and are they on Optimism?:
Optimism is severly underserved by other oracle networks such as Link, with not even 50 feeds by the largest oracle providers, with all being provided by only a few signers, creating not only limited data for devs and projects but all being unable to be custom for projects with their own data sources to ensure security and ability to deploy new feeds and scale. Alternatives are usually just Link forks or also have a token required in the model, cannot deploy own oracles, cannot access custom data or are not simple to use.
Team
Who are your founders?:
PR0
What makes your team well-suited to carry out the project described in this proposal?
We have already built it. Its operational. No vaporware. No BS. We show before we ask for funds.
Is this your first Web3 project?:
No
If not, what else have you built? (Share links, Github repository, or any other useful information.):
Grant Request
What is the size of the grant request? (250k OP max):
50k OP
How do you justify the size of the grant?:
The funds will be used to create a sustainable model for data and compensate for gas costs, developer support, expand tools, bring new data providers into the market, allow for subsidies for data and allow for feeds to be maintained reliably with stable nodes and high frequency.
Roadmap and Distribution Plan
Describe in discrete steps how you will successfully implement your grant plan:
- Deploy reference oracles and help new projects access data they need directly.
- Create data markets allowing anyone to create their own nodes and oracles to earn revenue and decentralize the data sources.
- Just keep building new tools and features.
How will the OP tokens be distributed? (please include % allocated to different initiatives such as user rewards/marketing/liquidity mining. Please also include a justification as to why each of these initiatives align with the problem statement this proposal is solving. Distribution should not include the sale of any tokens by the grantee or the use of tokens for compensation, protocol expenses, etc. See the no sale rule here):
75% Data feed subsidies for oracles and nodes to provide data. These will be used by allowing for gas compensation, dedicated allocation for new providers, allocations for key providers, allocations for reputable community members to be data providers. This is needed to allow for a large data market and as many players to enter as well as keep oracles maintained and operational.
25% Marketing incentives through giveaways to promote reach, partnership incentives for projects to use the oracles, hackathon prizes.
Please clearly define the milestones you expect to achieve in order to receive milestone based installments. Please consider how each milestone relates to incentivizing sustainable usage and liquidity on Optimism. Progress towards each milestone must be trackable: Rather than applying then creating milestones and building we have built as much as we can, with an operational oracle, factory and front end ready to show that we are both able to perform and that we can perform what we say. The front end is available at
https://optimism.dapp.scry.finance/
With contracts and framework ready for developers to self deploy.
Over what period of time will the tokens be distributed for each initiative?:
Will be based on opportunities, but targeting 1y, but if we are able to make it last based on market conditions then it will be used to continue
Please provide benchmark milestones for this project. These milestones should guide the Optimism community on the progress of your project throughout your work on the project. Do not use distribution of the grant itself as a milestone:
- Oracle feeds available
- Projects using Scry oracles
- Feeds processed
- Data Providers
Please define critical milestones for this project. Critical milestones are meant to show good-faith efforts to accomplish the project. Non-completion of these milestones could lead to revocation of remaining grant rewards. Do not use distribution of the grant itself as a milestone:
q2
Have atleast 50 feeds that are maintained to match Link. Based on requests by projects.
Have the framework for Morpheus and DataLink deployment by any devs and used
Have 5 signers for the reference oracle
Have atleast 20 feeds that are maintained by reference oracle based on dev needs.
q3
Have atleast 50 feeds that are maintained by reference oracle with high uptime
5 Projects using the infrastructure
5 Independant oracles using Morpheus
10 Projects using the infra
20 Projects using the infra
If the OP tokens are for direct distribution to users, why will incentivized users and liquidity on Optimism remain after incentives dry up?:
Because the projects will have users with their own uses and protocols, and will continue to need the data and oracles to allow for the contracts and use cases
Please provide any additional information that will facilitate accountability (smart contracts addresses relevant to the proposal, relevant organizational wallet addresses, etc.):
core oracles can be found there for optimism as well as non reference and core oracles and addresses.
Deployment address / oracle address
0x00f0000000F11a5380Da5A184F0C563B5995fee2
Optimism Relationship
Infrastructure
What is the problem statement this proposal hopes to solve for the Optimism ecosystem?:
Optimism is severly underserved by other oracle networks such as Link, with not even 50 feeds by the largest oracle providers, with all being provided by only a few signers, creating not only limited data for devs and projects but all being unable to be custom for projects with their own data sources to ensure security and ability to deploy new feeds and scale.
How does your proposal offer a value proposition solving the above problem?:
- Autonomous oracle system where devs can self deploy own feeds/oracles and use custom signers for permissionless, decentralized and secure deployment with self-controllable feed creation using custom APIs for rapid development.
- 200+ different feed updates with 1 tx (high scale data). Scaled with Layer 2s.
- Use any API with a highly robust parse engine, controlled by a simple spreadsheet, just put the URL, the parse for the json to be expected and basic info and the feed will be ready to use and submitted on chain by all signers.
- Data lookup for historical data for all feeds natively, allows for both immutable data access, TWAP construction and onchain analytics.
- Allows for various monetization structures at a feed level, oracle providers can charge for certain feeds to earn revenue as well as provide others for public use, subscription models for data requests at the feed level and oracle level.
Why will this solution be a source of growth for the Optimism ecosystem?:
The data available to devs directly limits use cases which can be deployed, you can’t deploy insurance without data about whats being insured, you cant deploy financial markets thats not crypto exclusive without access to traditional finance data. By allowing high scale, easy to deply oracles that supports new feeds in real time, projects can scale not just the transactions with L2s but the capibilities.
Is your project Optimism Native?:
No
Confirmations
I understand that I will be required to provide additional KYC information to the Optimism Foundation to receive this grant: [Yes/No]:
Yes
I understand that I will be expected to following the public grant reporting requirements outlined here: [Yes/No]:
Yes