- Home
- Skills
- Web3 & Crypto
- Cross-Chain Bridge Transaction Investigator
Works with the AI Agents you already use
Cross-Chain Bridge Transaction Investigator
Trace, correlate, and debug cross-chain bridge transactions using multi-chain evidence and log decoding.
$29.99
Cross-Chain Bridge Transaction Investigator
Example session with this skill installed
Investigate a stuck bridge transfer from Ethereum (1) to Polygon (137) using Stargate. Source hash: 0x5c8e...d421. I have the raw logs but no destination hash yet.
- Read your context and instructions
- Compiled the cross-chain bridge transaction
I have analyzed the source transaction on Ethereum and attempted to correlate it with Polygon chain data. The transfer appears to be stalled at the attestation stage.
Cross-Chain Bridge Transaction Investigation Report
- Protocol: Stargate Finance
- Source/Destination: Ethereum (1) -> Polygon (137)
- Source Hash: 0x5c8e...d421
- Message ID: 40291...882
- Analysis Time: 2024-05-20 14:30 UTC
Executive Summary
The source transaction was successfully finalized on Ethereum. Stargate SendMsg events were emitted, but no corresponding CreditChainPath or execution event is visible on the destination chain within the expected 20-minute window.
Transfer Identity
| Field | Value |
|---|---|
| Token | USDC (0xa0b8...e1fe) |
| Amount | 5,000.00 |
| Sender | 0xf39f...2266 |
| Recipient | 0xf39f...2266 |
| Match Confidence | High (Message ID verified) |
Event Timeline
| Stage | Chain | Transaction/Event | Block | Status | Confidence |
|---|---|---|---|---|---|
| Source Submitted | Ethereum | 0x5c8e...d421 | 19827341 | Success | High |
| Initiation Event | Ethereum | SendMsg | 19827341 | Emitted | High |
| Destination Execution | Polygon | N/A | N/A | Missing | Medium |
Log Decoding
- Contract: 0x8731... (Stargate Bridge)
- Event:
SendMsg(uint16 dstChainId, uint8 functionType, bytes recipient, uint256 amount) - Decoded: dstChainId: 109 (LayerZero ID for Polygon), amount: 5000000000.
Likely Failure Points
- Relayer Delay: The LayerZero relayer has not yet delivered the message to the destination endpoint.
Gas Spike: Destination execution may be pending due to insufficient gas settings for current Polygon network conditions.
Asset Status
Status: Locked (Source) / Pending (Destination).
Funds are securely locked in the Ethereum bridge vault; no mint/release evidence found on Polygon.
Next steps
- Check the LayerZero Scan tool using the Message ID to see if the message is in 'Verifying' state.
- Monitor the destination recipient address for a late
CreditChainPathtransaction. - If 60 minutes pass, contact Stargate support with the Message ID provided above.
Connects securely to your tools. The creator never sees your data.
About this skill
Tracing stuck or failed bridge transfers across chains is a manual, error-prone process involving fragmented data and inconsistent event naming. This skill automates the investigation by correlating source and destination evidence to find exactly where a cross-chain message stalled. It reconstructs the bridge lifecycle from raw logs and transaction receipts while maintaining strict evidence-based reasoning.
What it does
- Trace transfers by correlating source and destination transaction receipts, message IDs, and nonces.
- Decode logs using verified ABIs to extract transfer initiation, attestation, and execution events.
- Reconstruct lifecycles to map the sequence from source submission to final asset release or minting.
- Identify bottlenecks by calculating elapsed time between stages and comparing them against documented protocol expectations.
- Hypothesize failure points such as finality issues, relayer delays, or destination reverts based on on-chain evidence.
How it works
- Initialize the investigation by providing chain IDs, bridge protocol details, and known transaction hashes or message IDs.
- Analyze the source chain receipt for status, gas details, and bridge-specific initiation events.
- Correlate data across chains using transfer IDs or embedded hashes to locate the corresponding destination activity.
- Generate a structured investigation report detailing the event timeline, log decoding, and asset status.
Frameworks & tools
Works with any EVM-compatible or non-EVM chain data provided via RPC results, explorer links, or raw receipts. Supports protocol-specific ABIs for event decoding.
Why this beats prompting it yourself
Generic LLMs often hallucinate transaction statuses or confuse source and destination chain contexts. This skill enforces a rigorous evidence-linked workflow that distinguishes between "missing evidence" and "proof of failure," ensuring you don't chase false positives during debugging.
Use cases
- Debug stuck transfers for users by finding exactly which relayer or attestation stage is pending.
- Audit bridge integrations by verifying that events are firing correctly with the expected nonces and parameters.
- Support operations by generating reproducible reports for engineering teams to resolve protocol-level stuck messages.
Known limitations
Cannot sign transactions or access private keys. Accuracy depends on the availability of verified ABIs and indexed explorer data for both chains.
Requires raw logs or receipts for analysis. Cannot execute or replay transactions. Investigation quality depends on data availability from block explorers or RPC providers.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 20 days ago
Permissions
No special permissions declared or detected