The purpose of this section is to provide examples of grant applications that identify potential/existing projects that can/do benefit the Rubicon Ecosystem and applications that represent the level of vigor expected of grant applications. These applications follow the Grant Proposal Template outlined here and are focused around the program values outlined here.
Grant Title:
Multi-chain Rubicon User Dune Dashboard
Author(s) and contact info:name: denver
email: denver@rubicon.finance
twitter: @DenverBaum
discord: denver#8815
github: https://github.com/denverbaumgartner
About you:
My name is denver and I have worked on a variety of blockchain related data projects. Before working in the web3 space, I had a variety of data science experiences at places such as the SEC. You can find some of my web3 data work below:
dune: dune.com/rubicondefi
subgraphs: https://github.com/RubiconDeFi/rubi-subgraphs
python: https://github.com/RubiconDeFi/rubi-py
Grant Description:
The Rubicon DeFi ecosystem could gain a more comprehensive understanding of its user activity by creating a multi-chain Dune dashboard. This dashboard would provide a high-level overview of Rubicon user activity across multiple chains and decentralized exchanges (DEXs), allowing the Rubicon community to make informed decisions about future developments and better allocate time and resources based upon user needs.
-
The Problem you hope to solve / study
As Rubicon expands its reach across different chains and DEXs, it becomes increasingly difficult to understand user activity and make informed decisions about future developments. The creation of a multi-chain dashboard will help address this problem by providing a centralized location for collecting and analyzing user activity data. Outside of just focusing on network wide metrics such as TVL and Volume, it would be useful to be able to view what other networks existing Rubicon users transact on, along with deeper insights into general trends for Rubicon users.
-
The Context of the Problem and helpful sources
The decentralized finance (DeFi) landscape is rapidly growing, with an increasing number of protocols and platforms. The creation of a multi-chain dashboard for Rubicon will provide a solution for the protocol to keep pace with this growth and stay ahead of the curve. Additionally, a multi-chain dashboard will set a solid foundation for future developments without creating additional tech-debt from as a result of dashboard development being focused on a single-chain.
-
The Criteria through which you evaluate the problem
The success of the project will be evaluated by the accuracy and relevance of the user activity data collected by the dashboard. The dashboard’s ability to identify and analyze trends and patterns in user activity across different chains and DEXs will also be considered when evaluating its success. Specifically, the ability to analyze the entire dashboard based upon certain criteria, such as network, asset, or user, will prove to be beneficial in both the short and long-term and indicate some level of success of the project.
-
The Work you hope to do in response to the problem
The project will involve developing a multi-chain dashboard for Rubicon that is built on Dune, the public SQL analysis website for blockchain data. The dashboard will integrate with existing data sources and provide real-time user activity data across multiple chains and DEXs. An example mock-up of what this dashboard is expected to look like is provided here, and any feedback from the Community or Grants Committee regarding this mock-up is appreciated. Before work begins, it is recommended that the Grants Committee comes to a final agreement on the architecture and contents of the dashboard in order to ensure all parties have a shared understanding of the work to be done.
-
The Reason for doing this work in response to the problem
The creation of a multi-chain dashboard will provide Rubicon with valuable insights into user activity and help inform future developments. It will also enable the Rubicon team to identify new opportunities for growth and focus their efforts in areas with the highest user engagement. By leveraging the power of Dune’s public SQL analysis, the dashboard will provide a scalable and flexible solution for collecting and analyzing user activity data.
Goals and Impact:
The goal of this grant is to successfully develop a multi-chain dashboard for the Rubicon DeFi ecosystem, which will provide a comprehensive understanding of user activity across multiple chains and DEXs. The successful completion of this project will have several important impacts that will benefit the entire Rubicon ecosystem. Most notably, a successful dashboard will act as a shared source of truth within the community that can be easily cited to support data driven decision making by the collective.
Success will be measured by:
-
Accuracy of Data: The accuracy of the user activity data collected and analyzed by the dashboard will be a key measure of success. The dashboard will be expected to provide accurate and relevant data, utilizing public tables such as
dex.trades, to inform the Rubicon ecosystem’s decision-making process. Clean code is of utmost importance to ensure that any independent actor can easily verify the logic and validity of the underlying queries. - User Engagement: The dashboard will also be evaluated based on its ability to identify trends and patterns in user activity across different chains and DEXs. The goal is to provide insights into areas with the highest user engagement and identify opportunities for future growth.
- User Adoption: The user-friendly interface of the dashboard will be critical to its success. The goal is to increase user adoption of the dashboard and ensure that it becomes a valuable tool for the Rubicon ecosystem and its users. Easy filter parameters, such as by network, asset, or address will increase the likelihood of widespread adoption of the protocol.
- Scalability: The use of Dune’s public SQL analysis will provide a scalable and flexible solution for collecting and analyzing user activity data. The dashboard’s ability to adapt to the growing DeFi landscape will be a key measure of success. Architecting queries in a modular way, utilizing aggregate data tables, will help to eliminate the unnecessary creation of tech-debt.
- Maintainability: The dashboard will be designed with maintainability in mind, with modular, easy-to-read queries that can be forked and used by others for further analysis of the Rubicon protocol and its users. The dashboard should render well on both mobile and desktop devices.
Assuming the grant is successful, the Rubicon DeFi ecosystem will have access to a comprehensive understanding of its user activity across multiple chains and DEXs. This will inform the Rubicon ecosystem’s decision-making process and enable it to identify new opportunities for growth and focus its efforts in areas with the highest user engagement. The successful development of a multi-chain dashboard will position Rubicon in line with the forefront of the DeFi landscape and provide a collaborative platform for the ecosystem, while also providing a public good for the wider DeFi community.
Milestones:
Assuming the grant is successful, the following milestones are proposed:
- Milestone 1: Development of Rubicon Specific Portion. This will include the creation of a high-level dashboard that provides an aggregate of key statistics of the Rubicon protocol across different chains/networks. This dashboard will include key metrics such as total trading volume, number of trades, and user activity.
- Milestone 2: Network Specific Portion. This milestone will include the creation of a section that focuses on analyzing user activity on a specific chain and comparing their usage of Rubicon to other DEXs. Key metrics such as trading volume, number of trades, and user activity will be compared to provide insights into the performance of Rubicon on each network.
- Milestone 3: Network Comparison Dashboard. The final milestone will include the creation of a comparison dashboard that compares Rubicon user statistics across multiple chains. This will provide a high-level view of Rubicon user activity across different networks and help to identifying trends and patterns. The comparison dashboard will also provide insights into the total volume over set periods of time on each chain, helping the Rubicon ecosystem make informed decisions on future network launches and development efforts.
Each of these milestones will result in a deliverable that will be made available to the Rubicon ecosystem and the wider public. The community can expect a modular, easy-to-read dashboard that provides valuable insights into the Rubicon protocol and its users, which can be forked and used for further analysis. The final deliverable will be accessible from both mobile and desktop devices and will adhere to public standards set by public tables such as dex.trades.
Funding Request:
(How much funding are you requesting?)
Budget Breakdown:
(How exactly will the funds be used?)
Timeline:
Milestone 1: 1-2 Weeks
Milestone 2: 1-2 Weeks
Milestone 3: 1-2 Weeks
Total Timeline: 4-6 Weeks after grant approval
Other Information:
Past SQL & Visualizations, I am proficient in Python and am hoping to expand upon this work with the creation of a dex.offers table that can achieve a similar level of increased visibility and use as dex.trades. Upon success of this grant application, this would be an area I would be interested in receiving additional funding to work on.
I understand that I am responsible for reporting progress on this grant in the public forum
YES
Retroactive Grants
Retroactive grants are intended to support individuals and teams who have already made valuable contributions to the Rubicon Protocol ecosystem. We believe that this is an efficient way for the community to support important contributions and to encourage the development of minimal viable products and projects. The grant applicant should show the impact of their work and quantify it. If the proposal is for a minimal viable product, it should quantify the potential impact of further development of said product. Additionally, a portion of the grant may be allocated to applying for additional funding going forward, in order to continue to drive the project’s progress.
Grant Title:
rubi: Python SDK for Rubicon
Author(s) and contact info:
email: denver@rubicon.finance
twitter : @DenverBaum
discord : denver#8815
github : denverbaumgartner (denver) · GitHub
About you:
My name is denver and I have worked on a variety of blockchain related data projects. Before working in the web3 space, I had a variety of data science experiences at places such as the SEC. You can find some of my web3 data work below:
Grant Description:
The rubi Python SDK has already been completed and tested thoroughly with a comprehensive suite of tests for all write functionality to the blockchain. It supports a majority of functions and views exposed on the RubiconMarket, RubiconRouter, and MarketAid contracts, making it easier for developers to interact with the Rubicon protocol and collect data about it. The SDK also provides higher level functionality such as a book builder, and has been integrated with open-source subgraphs to enable data access.
In addition to data collection, the rubi SDK has some additional features such as historical asset balance tracking for MarketAid contracts, making it a comprehensive tool for developers to work with the Rubicon protocol. The repository has full documentation for all functions interacting with the contracts and there are plans to expand documentation to include data collection and processing.
-
The Problem you hope to solve / study:
The
rubiPython SDK is a solution that was created to address the lack of a Python interface for the Rubicon protocol. The goal of the SDK is to make it easier for developers to interact with the Rubicon protocol and collect data about the protocol. This will enable the creation of more robust and sophisticated tools and applications for the Rubicon ecosystem. -
The Context of the Problem and helpful sources:
The Rubicon protocol is built on the Ethereum blockchain and is designed to be a decentralized exchange (DEX) platform. Interfacing with the Rubicon protocol using a high-level programming language like Python will allow developers to create and maintain powerful tools and applications that can be used by the wider Rubicon community.
-
The Criteria through which you evaluate the problem:
The success of the Rubi Python SDK was evaluated based on its ability to enable developers to easily interface with the Rubicon protocol, as well as its ease of use and its overall functionality. The SDK was built with scalability and maintainability in mind, and was tested with, and maintains a testing framework for, various use cases to ensure that it meets the needs of the Rubicon ecosystem.
-
The Work you hope/have to do/did in response to the problem:
The Rubi Python SDK was built around the web3.py and subgrounds packages. The web3.py package is a Python interface for interacting with the Ethereum Virtual Machine (EVM), while the subgrounds package is a Python interface for interacting with subgraphs, which are public APIs supported by The Graph network. The Rubi Python SDK extends the functionality of these packages to enable developers to easily interface with the Rubicon protocol.
-
The Reason for doing this work in response to the problem:
The Rubi Python SDK was created to fill a gap in the Rubicon ecosystem by providing a Python interface for the Rubicon protocol. This will enable developers to create and maintain powerful tools and applications that can be used by the wider Rubicon community.
-
The Work you hope to expand upon if applying for additional funding:
The
rubiPython SDK is already a functional solution for interacting with the protocol, but there is always room for improvement. Future funding could be used to expand the functionality of the SDK and to add more advanced features. One such feature is a nonce-manager as outlined in this issue. This could include the integration of additional data sources and the creation of more complex use cases.
Going forward, the repository could benefit from more examples to help new users get introduced to the various functions and use-cases of the SDK. This would help the entire Rubicon ecosystem benefit from the SDK and encourage more collaboration among developers.
Goals and Impact:
Further funding would go towards two major tooling areas that are currently lacking in both the Rubicon ecosystem and Ethereum-Python ecosystem more broadly:
-
Nonce Manager: Currently, web3.py does not have a manager that is supported out of the box. This is common tooling that is needed for all automated traders, and tooling that will only grow in complexity as further aspects of the mempool/EVM are accounted for. The Nonce Manager must be well tested and ready to support production systems.
-
Market Simulator: Market simulators are helpful for a variety of reasons, from back-testing to reinforcement learning, and the ecosystem as a whole would benefit from a shared market simulator infrastructure. Work towards this effort have already begun with data collection and the existing SDK, and future development could be centered around py-evm to take advantage of existing infrastructure. The Market Simulator will be constructed as an environment that extends the functionality of the Gymnasium repository, and ideally act as a starting place for
gym-evm.
Milestones:
- v0 of Nonce Manager: The first milestone will be the completion of the v0 of the Nonce Manager, which will include basic functionality such as transaction management and nonce tracking. The community can expect a fully functional Nonce Manager that supports the most common use cases, and is well-documented.
- v1 of Nonce Manager: The second milestone will focus on expanding the functionality of the Nonce Manager to include more advanced features such as error handling, transaction prioritization, and support for batch transactions. The community can expect a Nonce Manager that is robust and ready for production use, with clear guidelines on best practices for usage.
- v0 of Market Simulator: The third milestone will be the completion of the v0 of the Market Simulator, which will include basic functionality such as data collection, market simulation, and visualization tools. The community can expect a functional Market Simulator that allows for basic back-testing and provides a foundation for future development.
- v1 of Market Simulator: The fourth milestone will focus on expanding the functionality of the Market Simulator to include advanced features such as reinforcement learning, historical data analysis, and improved visualization tools. The community can expect a Market Simulator that is a valuable resource for traders and researchers, and provides a platform for further innovation and development.
- v2 of Nonce Manager and Market Simulator: The final milestone will be the completion of the v2 of both the Nonce Manager and Market Simulator, which will include all the features and improvements developed in the previous milestones, as well as any additional features that have been identified during the development process. The community can expect a comprehensive toolset that serves the needs of the Rubicon ecosystem and the Ethereum-Python ecosystem more broadly.
Funding Request:
(How much funding are you requesting?)
Budget Breakdown:
(How exactly will the funds be used?)
Timeline:
Assuming the grant is approved and funding is secured, the expected timeline for completion is as follows:
- Week 1: Initial research and analysis of the current state of the Ethereum-Python ecosystem and the Rubicon ecosystem to ensure compatibility with existing tools and infrastructure. This will involve collaboration with the relevant communities to gather feedback and requirements.
- Week 2: Development of a comprehensive plan for the Nonce Manager and Market Simulator, including design and implementation details. This will include regular updates and reports to the community to keep everyone informed about progress.
- Weeks 3-5: Implementation of the Nonce Manager, including thorough testing and quality assurance procedures. This will involve the creation of robust test cases and the use of automated testing tools to ensure a high level of reliability and scalability.
- Weeks 6-10: Implementation of the Market Simulator, including integration with existing tools and infrastructure such as
py-evm. This will also involve thorough testing and quality assurance procedures. - Weeks 10-12: Finalization of the project, including documentation, code reviews, and bug fixing. This will involve the release of a stable version of the SDK, along with a detailed report on the project’s progress and future plans.
This timeline is subject to change, and may require adjustments based on the complexity of the work and the availability of resources. However, the overall goal will be to complete the project within ~3 months, with regular updates and reports to the community to ensure transparency and accountability.
Other Information:
I have a history of data science work with a focus on machine learning and am passionate about building tools that benefit the open-collective through shared common infrastructure and processes.
I understand that I am responsible for reporting progress on this grant in the public forum
YES