Use IMD Radar as a supplementary ecosystem data source where it improves coverage, but do not make it the sole authority for ChadBoard rankings.

Use structured API endpoints, not HTML scraping:

• https://www.imdradar.site/api/feed?view=swarm
• https://www.imdradar.site/api/feed?view=seat&id={seat}
• https://www.imdradar.site/api/launchpad?view=agents

Add an optional IMD Radar adapter that:

1. Imports and caches:

   • seat number
   • agent ID
   • owner wallet
   • online/status state
   • accepted/rejected/failed/pending work
   • latest work timestamp
   • launch participation
   • launch reward and unclaimed-reward data
   • wallet-to-seat relationships

2. Stores the raw Radar response with:

   • source URL
   • retrieval timestamp
   • response hash
   • schema/version marker

3. Uses Radar to bootstrap or cross-check:

   • seat-to-wallet mapping
   • active seat status
   • swarm job/activity metadata
   • launch reward history
   • launch participation

4. Does not use Radar as the authority for:

   • ChadBoard score
   • immutable snapshot ordering
   • historical IMD transfer accounting
   • current IMD balances
   • proof that a wallet sold or retained tokens

5. The authoritative ranking snapshot must still be calculated from:

   • Ethereum contract state
   • Ethereum event logs
   • the ChadBoard contract
   • the IMD token Transfer history

6. When Radar and Ethereum disagree:

   • preserve both values
   • mark the conflict explicitly
   • prefer the as-of-block Ethereum value for financial and ranking calculations
   • never silently overwrite one source with the other

7. Add source fields to API responses:

   • source: ethereum | imd-radar | merged
   • sourceRetrievedAt
   • asOfBlock where applicable
   • dataQuality
   • conflict flag/details where applicable

8. Add tests for:

   • Radar API unavailable
   • malformed Radar response
   • stale Radar data
   • wallet mapping disagreement
   • duplicate seat/wallet relationships
   • Radar launch data with low-liquidity tokens excluded

The site must remain functional if IMD Radar disappears. Radar is an enrichment and bootstrap source, not a hard dependency.

An archive-capable Ethereum mainnet RPC has been configured on the worker as ETH_ARCHIVE_RPC_URL - https://eth-mainnet.g.alchemy.com/v2/alch_CVe3_ZPG2ZiUPYDNxSMsy

Use it only for historical backfill and deep event queries. Keep the value server-side and never print, commit, expose, or include it in the frontend bundle.

Before indexing:

1. Verify the variable exists without printing its value.
2. Query a historical block older than the current public-RPC retention window.
3. Verify IMD Transfer logs can be fetched across the required historical range.
4. Estimate the number of RPC requests and expected backfill duration.
5. Run a small dry-run before starting the full backfill.
6. Store block checkpoints and resume safely after interruption.
7. Report the exact historical start block, end block, wallet count, event count, and any gaps.