Skip to content

Add testnet rewards summary for Q2 2026 - #184

Merged
kdembler merged 1 commit into
mainfrom
testnet-rewards-2026-Q2-summary
Oct 12, 2026
Merged

kdembler merged 1 commit into
mainfrom
testnet-rewards-2026-Q2-summary

Conversation

@kdembler

Copy link
Copy Markdown
Contributor

Adds src/points/testnet-rewards/2026-Q2.summary.json, the record of how the Q2 2026 testnet rewards were computed.

  • Contract: 0xc05DbE56F6f144159Bf43E04829dC2d790aE1E5D
  • Root: 0xf0ed8bdd…715d45
  • Total: 157,492.44 SQD across 20 wallets
  • Price: $0.035716, with 25 workers × $225

periodEnd here is 2026-06-29, the last day actually counted: the Q2 query used timestamp < 2026-06-30. The live current.json still shows 2026-06-30 for display, and this PR does not touch it.

From now on, publish in the testnet-rewards script (subsquid-network-contracts#88) writes one <quarter>.summary.json per quarter, next to current.json and the per-contract tree archive. build reads the previous quarter's summary to show how the new quarter compares, so cdn is the only record of what was paid.

I generated the file with publish against the live Q2 contract. Its root and token checks pass, and its balance covers all unclaimed rewards. The per-contract archive src/points/0xc05D….json already on main came out byte-identical.

🤖 Generated with Claude Code

Records the parameters behind the Q2 2026 distribution (0xc05DbE56…1E5D):
price 0.035716, 25 workers x $225, data window 2026-04-01 to 2026-06-29,
root, total and wallet count. The testnet-rewards script in
subsquid-network-contracts now writes one of these per quarter and reads
the previous one to compare quarters.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kdembler
kdembler merged commit b2e7af4 into main Oct 12, 2026
1 check passed
@kdembler
kdembler deleted the testnet-rewards-2026-Q2-summary branch October 12, 2026 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant