Show smart contract information

[hanwencheng]

The four live smart contract info can't be show in the explorer:

AgentKeysScope = 0x14C23B5D1cE20c094af643a20e6b0972dAD12aa8
SidecarRegistry = 0x76D574a107727bE87fc1422661A030FEFda70786
K3EpochCounter = 0x8396dEc50ff755d6DE7728DABB00Be2eFBCdf4dF
CredentialAudit = 0x1801ded1a4FBD8c9224Ab18B9EcbB293B8674c06

check the smart contract information, which should aligned with Etherscan, but it would be better if we can see the solidity code.

[crossagent-production-app]

CrossAgent status

Status: PR created
Task: github-litentry-subscan-essentials-3
Runtime task: task_bf38c07cafa64c6c
Base branch: cross-agent

Identity mode. Posted by the configured GitHub API identity (mode=github-app-installation-token, source=github-app-installation-token, login=crossagent-production-app[bot]).

Issue: #3
PR: #9

Operator Links

• Admin Panel task trace: /api/tasks/task_bf38c07cafa64c6c
• Evidence gate: /api/tasks/task_bf38c07cafa64c6c/completion-check

Detected By

• GitHub PR Fix EVM contract address lookup casing #9 references this issue.

Next Owner

• Reviewer / repo owner

Next Action

• Review the PR checks, evidence, and remaining risks before merge.

Generated at: 2026-05-19T17:07:30.260Z

[Ilya0527]

"Show contract info" / "aligned with Etherscan" / "see solidity code" are three different data flows that get conflated in explorer UX:

1. Bytecode + storage — read directly from chain. If this is blank for the 4 addresses, the indexer isn't recognising them as contracts. On EVM-on-Substrate chains this is usually an H160-vs-H256 address-format mismatch in the lookup, or the EVM module's storage prefix is wrong for the target runtime.

2. Verified source — needs an off-chain verification service. public etherscan.io won't have these addresses (Litentry's parachain isn't indexed there). "Aligned with Etherscan" really means "aligned with whichever Etherscan-fork or Sourcify endpoint serves the chain." Are these 4 contracts verified there at all? If not, no UI work helps.

3. ABI / decoded events — separate again, usually shipped alongside verified source.

A common drift mode: the indexer stores the bytecode hash from chain-state at deploy time; the verifier returns metadata keyed on a recomputed hash (often keccak of constructor-stripped runtime code). The two never match for specific contracts even though both sources insist they're for the same address — UI shows "unknown" and the operator assumes the indexer is broken.

Quick triage: curl the verification endpoint for one of the four and check 200-with-source vs 404. That separates "indexer drift" from "just unverified" in one shot. Which verification source is subscan-essentials configured against here — Sourcify, a Litentry-specific Etherscan-fork, or something else?

Diagnosis: ALEF-PAT-004 | Confidence: 0.5 | See standard: https://n50.io/patterns/004

[crossagent-production-app]

CrossAgent status

Status: PR created
Task: github-litentry-subscan-essentials-3
Runtime task: task_bf38c07cafa64c6c
Base branch: cross-agent

Identity mode. Posted by the configured GitHub API identity (mode=github-app-installation-token, source=github-app-installation-token, login=crossagent-production-app[bot]).

Issue: #3
PR: #9

Operator Links

• Admin Panel task trace: /api/tasks/task_bf38c07cafa64c6c
• Evidence gate: /api/tasks/task_bf38c07cafa64c6c/completion-check

Detected By

• GitHub PR references this issue.

Next Owner

• Reviewer / repo owner

Next Action

• Review the PR checks, evidence, and remaining risks before merge.

Generated at: 2026-05-19T17:23:17.088Z