KudozPR rewards from GitHub activity
  • Overview
  • Campaigns
  • CRE executions
  • My rewards
  • New campaign
Repositories
  • token2049-decentralizing/core
    425
  • token2049-decentralizing/valid-palindrome
    28
  • token2049-decentralizing/two-sum
    24
Checking APIcre-runner.fly.dev
  1. CRE executions
  2. b06b1faf…
/

Execution b06b1fafCompleted

Settlement run for token2049-decentralizing/valid-palindrome#2 in Leetcode bug fix challenge, started 1 hour ago.
PR historyGitHub
Score
61/ 100
Eligibility
Eligible
Reward
0.61 USDCpaid on Solana
Duration
18s

Score breakdown

Evidence35 × 40% = 14.0Code review60 × 30% = 18.0Issue fit96 × 30% = 28.8
total 61 · min 50

Evidence

35 / 100 · 40%
  • Linked issue25/25
    #1
  • CI0/25
    no completed checks

Timeline

  1. QueuedOct 7, 2026, 16:31
  2. RunningOct 7, 2026, 16:31
  3. CompletedOct 7, 2026, 16:31

Workflow request

{
  "event": "merged",
  "head_sha": "2bee4a2105eb8f98c60e607c01c5768470397f78",
  "pr_number": 2,
  "repository": "token2049-decentralizing/valid-palindrome",
  "campaign_id": "942b24b6-7432-4b79-bcac-abfae37291df"
}
Execution ID
b06b1faf-89f6-48be-b293-857cca343d2f
Event
Merged (settlement)
Author
@9teMare
Paid to
H98i6E85Xbdv4XEPbbaGQJrkHmpnDbT3r7KvxGLMm5e
Payout tx
3vJhmPtJwDHy5CMwhYJqqC8mpmg5N65Kc1oojnEfVSMAhZciZq5p8SSJ7x398MuD8Gn5T7BqMW2tJsnSGk3ymVF8
Commit
2bee4a2
Approval
0/20
no approving review
  • Tests0/20
    no test files changed
  • Diff size10/10
    +3 / -0 lines
  • Code review

    60 / 100 · 30%
    • Correctness30/40
    • Tests0/25
    • Code quality20/25
    • Security10/10

    Issue fit

    96 / 100 · 30%
    • Issue relevance48/50
    • Value28/30
    • Scope20/20

    Eligibility

    • ✓Merged
    • ✕CI passedoptional
    • ✓Linked issue
    • ✓Min score61 / 50

    Where points were lost

    • Code review · TestsNo test was added or modified anywhere in the diff, so the claimed fix is unverified by any executable check.solve.py:11-13
    • Code review · CorrectnessThe new guard is behaviour-preserving rather than a real fix: the inner skip loops are already bounded by left < right, so left can never exceed right and the produced output is identical with or without these lines (including the '.,' example in the issue, which already returned True).solve.py:11-13
    • Code review · Code qualityThe early break duplicates the loop's existing termination condition, adding indirection to a hot two-pointer loop without documenting why the redundant guard is needed.solve.py:11-13
    Webhook
    927147b0-c26c-11f1-9736-da975e9ac9a3
    Evaluation hash
    0xaf59d750f8df58b62b43adf5b29697e85a1b71c9c9831d66a158c15b77bb8d35
    Policy hash
    0xb4872af5f5d1abd58c92eaee237a9e63df072677cdc8266db36c1cd551d8f3b0
    Runner
    080d6d9a597198