Sync upstream v11.3.0 (merge conflicts)

[JOY (JOY)]

Upstream Sync - v11.3.0

Auto-merge with upstream v11.3.0 failed. Version/workflow conflicts were auto-resolved,
but the following files have code conflicts that need manual resolution:

docker-compose/envs/common-blockscout.env
mix.lock

To resolve:

1. Check out this branch locally
2. Resolve remaining conflicts
3. Push and merge this PR
4. Then create tag v11.3.0 to trigger Docker build

Upstream release notes

---

Note

High Risk
Large release changing counter semantics, API preload behavior, stats fields, JSON-RPC batching, and indexer/cache propagation—operators must review new env vars and expect different DB/cache load patterns during deploy and backfill migrations.

Overview
Syncs Blockscout to upstream v11.3.0 (app versions and changelog). This is a broad performance and caching release across API, indexer, and JSON-RPC, plus OP Stack and several RPC fixes.

Query and API loading: Address participants (from/to/contract roles) are loaded in one deduplicated pass via Chain.preload_address_participants/4 across v2 address/transaction/token endpoints, main page, v1 token transfers, and realtime notifiers—replacing repeated per-role necessity_by_association preloads. join_associations/2 is reworked so to-many associations are not joined in ways that break limit pagination (fixes short pages for uncle blocks and block lists). Many address routes now use Address.check_address_exists and hash-based coin balance fetch instead of full address loads.

Counters and stats: Address and token transaction/holder/gas counters move to incremental consolidation (AddressCounters, TokenCounters, consolidators, backfill migrators) with many new CACHE_* and MIGRATION_* env vars; several legacy counter TTL env vars are deprecated. total_gas_used is removed from chain stats API/schema and the dashboard tooltip (GasUsageSum dropped from controllers).

Chain/indexer/RPC: OP Stack post-exec (0x7D) and L1 attributes (0x7E) transactions get JSON-RPC normalization, receipt handling, and UI/API transaction types. JSON-RPC batches are split and routed by URL type (e.g. eth_call vs default), with batch responses matched by id. Other fixes include hex block numbers in eth_getBalance, CryptoCompare API key support, async cache propagation (Explorer.Chain.Cache.Propagator), scam-address ETS cache, and websocket paths that skip work when nothing is subscribed.

Note for this fork: PR metadata indicates remaining merge conflicts in docker-compose/envs/common-blockscout.env and mix.lock outside the summarized upstream diff.

^{Reviewed by Cursor Bugbot for commit 369c3a3. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_e1edd484-2c02-4f74-aefc-6fc831b7fd52)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_ff6dbb9c-c897-4b22-bbe8-59f92cf338e3)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_95c0ecbe-61a4-4718-b377-b7e1838925fd)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_868e3dd4-5045-46d7-b13a-6764d7dd25f5)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_9f5fe362-31b4-4adc-a542-b5f86cd3c1dc)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_4edff92e-43b6-444a-abe1-0872b074b7f9)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_e7e97e95-8774-4717-bcf1-9cfa67706ade)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_6df55ce2-5b5a-4d53-99fb-4718d09f4afa)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_5bb27319-bcfe-40f8-a447-0c57437d8ab8)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_db9b19b5-f148-4c43-bfdc-b81b0e1039d9)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_85b49168-da36-4c9a-98fa-02742d50aca8)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_a00ae2e0-782b-4cff-b51a-537a72ad43a9)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_3c5bbd97-fe82-4023-b31d-c902f42842f8)