Skip to content

fix(labs/trading-data): bump to 0.2.4 — Etherscan V2 API - #141

Merged
mashkovd merged 1 commit into
mainfrom
fix/labs-trading-data-024
May 6, 2026
Merged

mashkovd merged 1 commit into
mainfrom
fix/labs-trading-data-024

Conversation

@mashkovd

@mashkovd mashkovd commented May 6, 2026

Copy link
Copy Markdown
Member

Summary

End-to-end smoke against 0.2.3 returned the following from etherscan_gas_snapshot:

{"error":{"code":"etherscan_error","message":"NOTOK"}}

NOTOK is Etherscan's catch-all for "API key valid but request not accepted". Free-tier keys created at etherscan.io/myapikey after the V2 multichain migration only work against /v2/api?chainid=...; the legacy /api (V1) endpoint rejects them with NOTOK.

mctl-trading-data 0.2.4 (commit e057505, image already published) switches to V2 + chainid=1 (Ethereum mainnet) for both etherscan_gas_snapshot and etherscan_whale_transactions. No public response shape change — V2 still returns {status, message, result}.

Test plan

  • mctl-trading-data 0.2.4 PR-validation + docker-publish workflows green
  • After merge + reconcile: pod rolls cleanly to 0.2.4
  • In-cluster etherscan_gas_snapshot returns safe_gwei/standard_gwei/fast_gwei populated
  • In-cluster etherscan_whale_transactions returns recent Vitalik transactions or empty list
  • @codex review clean

End-to-end smoke against 0.2.3 returned `{"error":{"code":
"etherscan_error","message":"NOTOK"}}` from etherscan_gas_snapshot.
Free-tier keys created at etherscan.io after the V2 multichain
migration only work against `/v2/api?chainid=...`; the legacy
`/api` endpoint rejects them with NOTOK.

mctl-trading-data 0.2.4 (commit e057505) switches to V2 + chainid=1.
No public response shape change.
@mashkovd

mashkovd commented May 6, 2026

Copy link
Copy Markdown
Member Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

To use Codex here, create an environment for this repo.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Keep them coming!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

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