Sync upstream v11.2.7

[JOY (JOY)]

Upstream Sync - v11.2.7

Auto-merge with upstream v11.2.7 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.2.7 to trigger Docker build

Upstream release notes

---

Note

Medium Risk
Touches high-traffic API preload, HTTP pooling, proxy-implementation caching, and transaction participant loading. Behavior is mostly additive/perf, but mis-tuned pools or cache TTLs can change latency and proxy-detection freshness.

Overview
v11.2.7 adds GET /api/v2/transactions/{hash}/preview for OG/social embeds (opt-in ENS/metadata/input decode) and a set of API latency cuts.

ENS and metadata preloads now run concurrently through maybe_preload_ens_and_metadata, over a new Finch keep-alive client with separate pools for short preloads vs long proxy calls (MICROSERVICE_HTTP_POOL_SIZE / MICROSERVICE_HTTP_POOL_COUNT). Transaction detail loads participants in one deduped pass, skips ABIs where unused, batches address tags, and folds address existence checks into a single query. Empty “not a proxy” results for self-verified contracts use a longer TTL (CONTRACT_PROXY_EMPTY_IMPLEMENTATION_DATA_CACHE_TTL); method-id lookups are cached.

Eden: sponsored txs attribute fees to the fee payer, credit batched call recipients (including unindexed addresses), and include fee payer/calls in interpretation requests. Indexer address/coin-balance extraction follows the same call/fee-payer set. ZkSync address-transform doctests no longer treat internal-tx created_contract_code as deployed bytecode.

^{Reviewed by Cursor Bugbot for commit 139e324. Bugbot is set up for automated code reviews on this repo. Configure here.}

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[gemini-code-assist]

Code Review

This pull request upgrades Blockscout to version 11.2.7, introduces a lightweight transaction preview endpoint, optimizes ENS and metadata preloading using concurrent requests, and implements a pooled HTTP client using Finch to reuse connections. It also adds caching for contract methods and fixes state changes for Eden sponsored transactions. The review feedback highlights critical issues, including unresolved merge conflicts in common-blockscout.env and mix.lock, a bug in HttpClient where Finch.Error is not properly rescued, and several potential runtime crashes due to missing safety checks for nil values or unconfigured environment variables.

[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_c58c6bc5-00c5-48d5-b950-420a8f18a9d6)

[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_a9588607-baa6-4066-9ba7-06a0d0e9538b)

[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_9b37a20c-d99e-4527-a316-89a90d6aa259)

[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_7167e7cd-1b4a-4c4d-8a5a-4fd646969274)

[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_34248327-cebd-4ff2-b17f-e1a1bfb2641d)

[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_f64b5c6a-97bb-45b3-a636-bce966f6b9d8)

[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_965d4803-1105-4910-a95d-b1a6c5175c23)

[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_97553bac-5c98-498b-a8a5-0132cf28f7e9)

[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_acad6b6e-2ec3-4ca7-8a70-829fd14bed05)

[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_9309d0f9-a5e0-4473-8073-f5a022acab6e)

[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_66b3c76c-67ed-4592-962f-eb1323c78669)