Direction

Through the bounty, we want participants to create useful data and increase the number of inquirers available on Chainsight.

The goal is to encourage people to generate valuable data on Chainsight, which can be implemented using Chainsight's CLI. However, there are deployment costs (Cycles) associated with the CLI, potential bugs still exist, and ongoing maintenance of the deployed canisters can be challenging. Therefore, for the initial phase of the hackathon/bounty, we are asking participants to brainstorm and develop valuable data. They can evaluate it by uploading the sample data they have collected and the corresponding Python scripts to GitHub. Later, the Chainsight team will review and agree to deploy the code using the CLI.

Example

Let’s say we can introduce a method to measure price stability based on historical price data by calculating the average price deviation.

https://github.com/horizonx-tech/rating-stablecoin-logic/blob/main/src/logics/deviation/src/lib.rs

[https://drive.google.com/file/d/1vNBIknDYRCP6sRK70oMKjcToJe_0UGL8/view](https://drive.google.com/file/d/1vNBIknDYRCP6sRK70oMKjcToJe_0UGL8/view)

Steps:

1. A participant determines the type of information required for on-chain applications, based on data that can be obtained from the web. Any data is acceptable as long as it can be accessed online. For example, utilizing historical price data to calculate price volatility. They are required to provide a detailed explanation of when the resulting data from the calculation will be valuable, as well as how the data was gathered. This is the most time-consuming part.
2. The participant then processes the data to derive meaningful information and writes code to test it. The code must be written in Rust, not Python, to ensure compatibility with Chainsight CLI in the future. Sufficient data should be prepared in the repository and calculations should be performed according to the designated formula.
3. The participant uploads all necessary code to GitHub as open source. Subsequently, all participants review each other's code and vote on which one is the most useful, scalable, and easy to manage. Based on the voting results, we award prizes to the top 3-5 participants. (according to the numbers of participants)

1. Topline Metrics:
   • What are the key metrics you are quantifying?
     • The data types that can be used in Chainsight in the future will mainly the metric.
     • The more people who participate, the more likely it is that useful data will be generated. However, the number of participants should be limited to 50-100 teams per session. This is because there is a limit to the number of peer reviews that can be conducted within a given time period.
2. Ideal Workshop Structure:
   • Duration:
     • 48 hours * 5 times of workshop/hackathon
     • Within 48 hours, the ideas are compiled, test code is written and uploaded to GitHub; one team has one minute to present, so you may have time to prepare slides for your presentation.
   • Topics Covered:
     • What data is needed for DeFi?
   • Integration of Chainsight: How can we incorporate Chainsight into the workshops?
     • Data that is highly rated on the bounty will be indexed on Chainsight and made available on-chain. Maintenance costs and deployment are handled by the Chainsight team.
3. Travel Plans:
   • What is your travel plan for the next two months?
     • Basically in UAE, but if necessary we can go out anytime
4. Remote Workshops:
   • Will you be able to conduct these workshops remotely? (We will have a remote setup)
     • We will be able to conduct workshops remotely.