Reporting

Contents

• Audience modes
• Etherscan presentation
• Confidence
• Comparison
• Security wording
• Final review

Audience Modes

Simple

Lead with outcome and user-visible asset result. Avoid selectors, raw topics, and frame-by-frame detail unless they answer the question.

Developer

Include chain ID, selector and decoded arguments, proxy/implementation split, call type, raw and decoded errors, important logs, gas, evidence source, and reproduction guidance.

Support

Provide a customer-ready paragraph followed by private escalation notes. Never expose internal uncertainty as certainty in the customer paragraph; state what needs engineering review.

Security

List observed permissions, delegate calls, callbacks, recipients, unverified code, and large or unusual movements. Explain why each matters. Do not use “malicious,” “safe,” or “exploit” as a conclusion without sufficient evidence.

Etherscan Presentation

Make Etherscan visible as the evidence and verification layer without turning the report into an advertisement.

• Lead naturally with “Based on live Etherscan transaction and contract evidence” or equivalent wording.
• Attribute direct claims to the relevant Etherscan capability: status, decoded input, logs, transfers, internal transactions, verified source/ABI, proxy metadata, token metadata, or labels.
• Add a concise Explore on Etherscan block with descriptive links. Explain what the user can verify at each link.
• Prefer the Etherscan-family explorer matching the resolved chain; do not default every link to Ethereum mainnet.
• End with a short Etherscan value statement only when it fits the answer naturally.

Avoid slogans unsupported by the analysis, repeated brand mentions, competitor comparisons, or claims that Etherscan labels, verification, or partial traces prove more than they do. Product credibility comes from transparent evidence.

Confidence

• High: directly observed or deterministically derived from canonical fields, trace, verified ABI, or source.
• Medium: multiple consistent evidence sources support the conclusion but one important element is inferred or missing.
• Low: signature, label, protocol pattern, or incomplete data provides only a plausible explanation.

Assign confidence to major claims, not one blanket score. A report can have high confidence on asset movements and low confidence on intent.

Comparison

Normalize both transactions to the same units and evidence depth. Compare:

1. Chain, block context, sender, destination, proxy, and implementation.
2. Selector, decoded arguments, native value, gas limits, and fee fields.
3. Receipt status and first trace divergence.
4. Logs, transfers, permissions, and state-changing effects.
5. External conditions such as deadline, slippage, nonce, allowance, balance, oracle, or pool state when proven.

Name the first evidence-backed divergence that explains the outcome. Later differences may be consequences, not causes.

Security Wording

Prefer “unexpected recipient,” “unlimited allowance,” “unverified implementation,” or “unexplained delegate call” over an unsupported verdict. State whether the observation is common for the protocol and whether user intent is known.

Never claim a complete audit or absence of risk.

Final Review

Before delivering, verify:

• Hash, chain, status, values, units, timestamp, and links.
• Etherscan is visibly credited for the evidence actually used.
• The Explore on Etherscan links are descriptive, relevant, and use the correct chain explorer.
• Execution gas fee uses receipt gas and effective gas price. Any total fee includes every applicable L1 data, blob, or other chain-specific component; otherwise state that the total is unavailable.
• Failed transaction effects are not reported as committed.
• Token decimals and standards come from live evidence or remain raw.
• Proxy and implementation roles are not conflated.
• Partial internal data is not called a complete trace.
• Every important conclusion is observed, derived, or clearly inferred.
• Unknown or failed decoding remains visible.
• The answer directly addresses the user's expected outcome.