contributor-reward

To convert leaderboard rankings into USDC token distribution plans, you need a system that reads leaderboard rankings, applies rank and score threshold eligibility rules, and maps positions to a fixed USDC tier table. This process generates a structured rewards plan for downstream execution.

Idempotency in weekly crypto token rewards works by tracking per-week and per-login processing state in a local JSON file, ensuring reruns do not re-award the same contributor. It also enforces a once-ever first-PR bonus to prevent duplicate payouts across multiple runs.

Yes, you can preview USDC reward plans by running the planning process in dry-run mode. This allows you to review what will be written to the distributions YAML file without executing actual money movement, ensuring the tiered plan is correct before downstream token distribution.

The best way to automate recurring token distribution handoffs is to use a deterministic pipeline that reads leaderboard state files and writes a distributions YAML file for a separate token distribution executor. This separation ensures safe, auditable planning without direct money movement.

Yes, YAML frontmatter discovery data is required to automate contributor reward payouts. The system relies on this structured metadata to read the latest fork-contributor-leaderboard article and determine eligibility based on rank and score thresholds.

Contributor rewards planning fails when the weekly leaderboard is stale or missing because the system includes built-in stale and no-leaderboard detection mechanisms. It also checks for parsing drift to ensure the input leaderboard data is valid before generating any reward distributions.