Our scoring framework promotes fairness, transparency, and clear alignment with our mission to encourage innovative, high-quality projects using the Pyth technology stack.
This section assesses the technical execution and robustness of the project, specifically focusing on the integration of Pyth on-chain price feeds.
| Level of Achievement | Points | Descriptor |
|---|---|---|
| Excellent | 16-20 | Pyth integration is flawless, demonstrating a deep understanding of its functionalities. All critical errors and edge cases are anticipated and handled gracefully, ensuring application stability. Price data is consistently and accurately pulled on-chain. Code is efficient and well-documented. |
| Good | 11-15 | Pyth integration is mostly correct with minor, non-critical issues. Major errors and common edge cases are handled. Some less common scenarios might be overlooked. Price data is consistently and accurately pulled on-chain. |
| Fair | 6-10 | Pyth integration is partially functional but has noticeable errors or omissions. Error handling is basic, and several edge cases are not addressed, potentially leading to instability. Price data is not consistently pulled on-chain |
| Poor | 0-5 | Pyth integration is fundamentally flawed or incomplete. Error handling is minimal or absent; edge cases are largely ignored. Price data is not pulled correctly or is not utilized effectively. The core functionality related to Pyth is broken. |
This section evaluates the relevance, practicality, and potential impact of the problem your project addresses and the solution it proposes.
| Level of Achievement | Points | Descriptor |
|---|---|---|
| Excellent | 16-20 | The problem is clearly defined, significant, and highly relevant to current market needs or a specific user group. The solution is practical, realistic to implement, and offers a clear, innovative approach to the problem. The potential impact is substantial, offering tangible benefits and demonstrating a strong value proposition. |
| Good | 11-15 | The problem is well-defined and relevant to market needs. The solution is generally practical and realistic, with a clear approach. The potential impact is evident and offers clear benefits. |
| Fair | 6-10 | The problem is defined, but its relevance or significance could be clearer. The solution is somewhat practical, but there may be concerns about its feasibility or effectiveness. The potential impact is moderate, or the benefits are not clearly articulated. |
| Poor | 0-5 | The problem is poorly defined, lacks relevance, or is not aligned with market needs. The solution is impractical, unrealistic, or does not effectively address the identified problem. The potential impact is minimal, or the value proposition is unclear. |
This section assesses how crucial and effectively Pyth data feeds are integrated into the core logic of your project.
| Level of Achievement | Points | Descriptor |
|---|---|---|
| Excellent | 10-15 | The project fundamentally depends on Pyth data feeds; the core functionality would be impossible or severely crippled without them. Pyth's specific features (e.g., confidence intervals, low latency, broad asset coverage) are leveraged effectively and uniquely, providing a clear advantage over alternative data sources. A compelling explanation is provided for how Pyth enhances or enables the solution in a way that alternatives could not. |
| Good | 6-9 | Pyth data feeds are clearly beneficial and well-integrated into the project. Good use of Pyth’s features, demonstrating an understanding of its advantages. A clear explanation is provided for how Pyth enhances the solution, though alternatives might offer some similar functionality. |
| Fair | 3-5 | Pyth’s features are utilized, but not to their full potential or in a way that clearly differentiates from alternatives. The explanation for Pyth's role is present but not entirely convincing. The project might function similarly with other oracles. |
| Poor | 0-2 | Pyth’s features are used superficially, or their integration feels forced. Little to no leverage of Pyth’s unique features; alternatives could easily substitute or might even be more appropriate. No clear justification for why Pyth was chosen or how it significantly benefits the project. |
This section evaluates the clarity, effectiveness, and professionalism of your project demonstration and explanation.
| Level of Achievement | Points | Descriptor |
|---|---|---|
| Excellent | 10-15 | Verbal and visual communication is exceptionally clear, engaging, and highly effective. The demo/presentation is very well-organized, with a logical flow that is easy to follow. The technical aspects and business value of the project are articulated with outstanding clarity and persuasiveness. All questions are answered confidently and thoroughly. |
| Good | 6-9 | Verbal and visual communication is clear and effective. The demo/presentation is well-organized and flows logically. The technical aspects and business value are clearly articulated. Most questions are answered well. |
| Fair | 3-5 | Verbal or visual communication lacks clarity in some areas or is not consistently effective. The demo/presentation has some organizational issues or an unclear flow. Articulation of technical or business value is adequate but could be more precise or compelling. Some difficulty answering questions. |
| Poor | 0-2 | Verbal and visual communication is unclear, confusing, or ineffective. The demo/presentation is disorganized, lacks logical flow, and is difficult to follow. Inability to clearly articulate technical aspects or business value. Questions are not answered satisfactorily. |