Today6 questions

Yesterday31 questions

TESTING. Select the 15 highest-scoring eligible hackathon submissions using only the section titled “All submissions: individual evidence and gaps” in this report: https://github.com/Identity-md/research/blob/main/jobs/e2b921c9-35eb-48bb-add4-2e8f42d944b2/files/artifacts/report.md Score every eligible submission using these five criteria: IMD integration: integer score from 0 to 30. Ecosystem impact and financial utility: integer score from 0 to 25. Originality and protocol innovation: integer score from 0 to 20. Technical architecture, security and risk management: integer score from 0 to 15. Demonstrated functionality and reproducibility: integer score from 0 to 10. The total score is the sum of these five integers. Minimum total: 0. Maximum total: 100. Do not use fractions, percentages, multipliers or rounding. Assess only evidence in the specified report section. Do not browse external sources. Give higher scores for demonstrated, substantive IMD integration, useful financial infrastructure, innovative design, credible security practices and verified functionality. Do not award points solely for intended features or project descriptions. Select the 15 eligible submissions with the highest total scores. Break ties by higher IMD integration score, then higher demonstrated functionality score, then project ID in ascending alphabetical order. Return exactly these fields for each selected submission: project ID, project name, IMD score, ecosystem score, originality score, technical score, functionality score, total score, and a brief evidence-based justification. Sort the final list by total score from highest to lowest. If fewer than 15 submissions are confirmed eligible, return all confirmed eligible submissions. Do not invent missing facts or claim that a score is an independently verified measurement.

not signed

TESTING Select up to 15 eligible hackathon submissions using the rules below. EVIDENCE SOURCE: Use only the section titled “All submissions: individual evidence and gaps” in this report: https://github.com/Identity-md/research/blob/main/jobs/3e6b2e22-8fc0-4b3e-b3c8-53c453effc7d/files/artifacts/report.md ELIGIBILITY: Include a submission only if the permitted evidence establishes that it meets the hackathon eligibility requirements. If eligibility cannot be determined, exclude it from the selected set and flag it for human review. Do not treat missing evidence as proof of misconduct. SCORING: Assess each eligible submission using evidence available in the specified section as of the report's recorded assessment date. Award integer points only, with no fractions or rounding. Working functionality and reproducible deployment: 0–20 points. Technical quality, security and reliability: 0–15 points. Depth and practical importance of IMD integration: 0–25 points. Originality of implementation: 0–15 points. User value and ecosystem benefit: 0–25 points. TOTAL SCORE: Add the five criterion scores. The minimum is 0 and the maximum is 100 points per submission. ASSESSMENT RULES: Reward demonstrated functionality, meaningful technical dependence on IMD, practical usefulness, originality and credible implementation evidence. Give higher scores to projects where IMD is essential to the core functionality rather than merely mentioned or superficially integrated. Distinguish verified evidence from claims, proposed features and missing documentation. Apply identical criteria to every submission. Do not invent facts or use evidence from external sources. SELECTION: Select the 15 eligible submissions with the highest total scores. If fewer than 15 submissions are eligible, select all eligible submissions. Do not assign ranks or positions.

not signed

TESTING Select the 15 strongest eligible hackathon submissions. Do not rank the selected submissions or assign positions. Evidence source: Use only the “All submissions: individual evidence and gaps” section of https://github.com/Identity-md/research/blob/main/jobs/3e6b2e22-8fc0-4b3e-b3c8-53c453effc7d/files/artifacts/report.md. Judging criteria: Apply the eligibility requirements and judging rubric in https://github.com/Identity-md/research/blob/main/jobs/e9efec16-56f3-40d3-9243-52c453effc7d/files/artifacts/report.md. Score each submission out of 100 points: Working functionality and reproducible deployment: 20 points. Technical quality, security and reliability: 15 points. Depth and practical importance of IMD integration: 25 points. Originality of the implementation: 15 points. User value and ecosystem benefit: 25 points. Award whole-number points only. Give strong consideration to projects that demonstrate substantive, technically meaningful use of IMD, a working product, clear practical utility and credible evidence of implementation. Distinguish demonstrated functionality from claims, plans and incomplete documentation. Reward integrations that make IMD essential to the product's operation rather than merely mentioning or superficially connecting to it. Use only evidence from the specified “All submissions: individual evidence and gaps” section. Do not consult external sources or other submission lists. Select the 15 eligible submissions with the strongest overall evidence and scores. Do not rank them, assign positions or present them in order of merit. List the selected project IDs in alphabetical order, alongside their total scores out of 100 and a brief explanation of the evidence supporting each selection.

not signed