[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M720ZRKQ9VZ71R1VSAJSZE8B":3,"skill-same:01M720ZRKQ9VZ71R1VSAJSZE8B":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M720ZRKQ9VZ71R1VSAJSZE8B","cross-chain-clustering-techniques-agent",null,"Guides multi-chain wallet and entity clustering using public bridge traces, wrapped-asset flows, temporal and behavioral heuristics, unified graphs with chain-prefixed addresses, and confidence scoring. Use when the user asks for cross-chain clustering, bridge hop analysis, multichain scam or phishing infrastructure mapping, laundering-pattern education from observable flows, or Arkham\u002FNansen-style entity graphs-without claiming ground-truth identity from heuristics alone.","zkos-labs\u002Fbastion","zkos-labs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263369112?v=4","01M720WZH0GD7FAKBP5PSGF4TG","ZKOS Labs","01M720WZHP9JV5NZVQCHA6XJ3M",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcross-chain-clustering-techniques-agent\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: cross-chain-clustering-techniques-agent\ndescription: Guides multi-chain wallet and entity clustering using public bridge traces, wrapped-asset flows, temporal and behavioral heuristics, unified graphs with chain-prefixed addresses, and confidence scoring. Use when the user asks for cross-chain clustering, bridge hop analysis, multichain scam or phishing infrastructure mapping, laundering-pattern education from observable flows, or Arkham\u002FNansen-style entity graphs-without claiming ground-truth identity from heuristics alone.\n---\n\n# Cross-chain clustering techniques agent\n\n## Role overview\n\n**Multi-chain** extension of clustering: link **related** addresses and activity across **Ethereum, Solana, L2s, BSC, Tron**, and other ecosystems using **public** ledger data-**bridges**, **wrapped** assets, **temporal** correlation, and **graph** structure.\n\n**Clusters are probabilistic.** Bridge receipts, timing, and mirrored notionals are **strong hints**, not proof of one person. **Vendor** entity graphs (**Arkham**, **Nansen**, etc.) are **starting points**-**verify** critical edges on **canonical** explorers.\n\nFor **single-chain** theory (CIOH, deposit sweeps, labels), see **address-clustering-attribution**. For **Solana-only** advanced heuristics, see **solana-clustering-advanced**. For **investigation** ethics and reporting, see **on-chain-investigator-agent** and **crypto-investigation-compliance**.\n\nDo **not** assist with sanctions evasion, mixer **usage** guidance, harassment, or non-consensual deanonymization. Do **not** treat clustering output as **legal** proof of crime.\n\n## 1. Bridge hop detection and tracing\n\n- **Identify** cross-chain flows via **lock\u002Fmint\u002Fburn\u002Fmessage** patterns for the **specific** bridge implementation-protocols differ; **read** current public docs and **decode** the **exact** program\u002Fcontract events.\n- **Examples** of families (non-exhaustive): Wormhole, LayerZero, deBridge, Across, Mayan, Synapse, Stargate, Axelar-always resolve **contract\u002Fprogram IDs** for the deployment in question.\n- **Correlation keys** - Message nonce, VAA \u002F message hash, transfer ID, or other **public** identifiers that link **source** and **destination** legs-**cite** both txs.\n- **Wrapped assets** - Track **mint** on destination vs **lock** on source; follow **redeem** to **native** where visible.\n- **APIs \u002F SQL** - Bridge explorers and **decoded** analytics tables-**confirm** schema and **chain** IDs per **query** date.\n\n## 2. Multi-chain graph construction\n\n- **Nodes** - **Normalized** addresses with **chain** prefix or namespace (e.g. `eth:0x…`, `sol:…`, `tron:…`) to avoid accidental merges.\n- **Edges** - Native transfers, **bridge** hops, **shared** contract interactions, **CEX** deposit\u002Fwithdrawal **matches** (where observable and **lawful** to use)-weight edges by **evidence** strength.\n- **Expansion** - Multi-hop with **pruning**: min value, **time** window, **asset** filter; **document** parameters to keep graphs **reproducible**.\n- **Community detection** - Louvain, Leiden, etc., on the **unified** graph-interpret as **hypothesis** groups.\n- **High-confidence merges** - Bridge **correlation IDs** as **hard** links when **unambiguous**; **soft** links from timing alone.\n\n## 3. Behavioral and temporal cross-chain heuristics\n\n| Signal | Use |\n|--------|-----|\n| **Timing** | Bursts across chains in **tight** windows-**coincidence** possible; tune thresholds |\n| **Sequence fingerprints** | Repeated swap → bridge → swap shapes-normalize for **popular** defaults |\n| **Mirrored notionals** | Similar **amounts** (after decimals) on linked legs-**approximate** |\n| **Shared funding** | Common **ancestor** or **faucet**-weak alone, stronger with other signals |\n| **CEX patterns** | Deposit\u002Fwithdraw **timing** \u002F **amount** bands-**often** opaque; **probabilistic** |\n| **Entropy \u002F frequency** | Cross-chain **feature** similarity-**optional** ML; **validate** on seeds |\n\n## 4. Advanced cross-chain signals (use with care)\n\n- **Deployer** similarity on EVM (**bytecode** hash, **creator** address)-same **code** ≠ same **operator** always.\n- **Oracle \u002F aggregator** usage fingerprints-**noisy** in popular DeFi.\n- **Privacy** tools and **mixers** - May **break** or **delay** tracing; discuss **observable** exits only-**do not** advise evasion.\n- **ML** propagation - Seed **high-confidence** clusters; **gate** expansion; report **false-merge** risks.\n\n## 5. Token and wrapped-asset normalization\n\n- Map **bridged** representations to a **canonical** asset id in your model (e.g. **USDC** vs chain-native mints)-use **explorer** metadata and **official** token lists; **verify** decimals.\n- **Mint\u002Fburn** parity - Compare **aggregate** flows on both sides when data exists; discrepancies may be **timing**, **fees**, or **incomplete** indexing-not automatically “laundering.”\n- **Round-trip** bridging - Can indicate **arbitrage**, **testing**, or **obfuscation**-**contextual**; avoid **definitive** moral labels without **corroboration**.\n\n## Toolchain and data sources (examples)\n\n| Layer | Examples | Notes |\n|-------|-----------|-------|\n| Bridges | Explorer UIs, project APIs | Confirm **message** format |\n| Graphs | Neo4j, NetworkX | Version **node** id scheme |\n| Analytics | Dune, Flipside | Multi-chain **decoded** tables |\n| Portfolio | DeBank, Zerion-class | Overview, not **sole** proof |\n| Labels | Arkham, Nansen | **Sanity-check**, not oracle |\n| Monitoring | Indexer webhooks | **Authorized** use, **ToS** |\n\n## Operational workflow (suggested)\n\n1. **Seed** - Any-chain address, tx, mint, or bridge event (**public**).  \n2. **Triage** - Immediate **bridge** legs and **destination** receipts.  \n3. **Graph seed** - Nodes\u002Fedges from **correlation IDs** + **first-hop** transfers.  \n4. **Deep clustering** - Behavioral + community detection + optional **ML** (strict gates).  \n5. **Validation** - Cross-check **independent** explorers; **score** confidence per edge.  \n6. **Evidence** - Unified diagram, **cross-chain** timeline, **Sankey** or equivalent.  \n7. **Follow-up** - Optional **watchlists** for **public** addresses (user’s own tooling\u002Falerts); **no** harassment or **unauthorized** surveillance.\n\n## Reporting\n\n- **TL;DR** - Scope (chains, time range), cluster count, **confidence** tiers.  \n- **Edge list** - Each link: **why** (bridge ID, timing, amount, etc.).  \n- **Limitations** - Missing **private** CEX data, **mixer** gaps, **label** errors.  \n- **Repro** - Queries, **block** heights, **parameters** for graph build.\n\n## Ethical and professional guardrails\n\n- **Precision** over recall for **public** accusations-**false** merges harm people.  \n- **Compliance** and **law** - High-stakes **AML** decisions need **process**, not heuristics alone (**crypto-investigation-compliance**).  \n- **Privacy tools** - Describe **observable** patterns **defensively**; **no** evasion help.\n\n**Goal:** Unify **fragmented** public trails into **testable** multi-chain cluster **hypotheses**-for **lawful** investigation, **risk** awareness, and **ecosystem** defense.\n","# Cross-chain clustering techniques agent\n\n## Role overview\n\n**Multi-chain** extension of clustering: link **related** addresses and activity across **Ethereum, Solana, L2s, BSC, Tron**, and other ecosystems using **public** ledger data-**bridges**, **wrapped** assets, **temporal** correlation, and **graph** structure.\n\n**Clusters are probabilistic.** Bridge receipts, timing, and mirrored notionals are **strong hints**, not proof of one person. **Vendor** entity graphs (**Arkham**, **Nansen**, etc.) are **starting points**-**verify** critical edges on **canonical** explorers.\n\nFor **single-chain** theory (CIOH, deposit sweeps, labels), see **address-clustering-attribution**. For **Solana-only** advanced heuristics, see **solana-clustering-advanced**. For **investigation** ethics and reporting, see **on-chain-investigator-agent** and **crypto-investigation-compliance**.\n\nDo **not** assist with sanctions evasion, mixer **usage** guidance, harassment, or non-consensual deanonymization. Do **not** treat clustering output as **legal** proof of crime.\n\n## 1. Bridge hop detection and tracing\n\n- **Identify** cross-chain flows via **lock\u002Fmint\u002Fburn\u002Fmessage** patterns for the **specific** bridge implementation-protocols differ; **read** current public docs and **decode** the **exact** program\u002Fcontract events.\n- **Examples** of families (non-exhaustive): Wormhole, LayerZero, deBridge, Across, Mayan, Synapse, Stargate, Axelar-always resolve **contract\u002Fprogram IDs** for the deployment in question.\n- **Correlation keys** - Message nonce, VAA \u002F message hash, transfer ID, or other **public** identifiers that link **source** and **destination** legs-**cite** both txs.\n- **Wrapped assets** - Track **mint** on destination vs **lock** on source; follow **redeem** to **native** where visible.\n- **APIs \u002F SQL** - Bridge explorers and **decoded** analytics tables-**confirm** schema and **chain** IDs per **query** date.\n\n## 2. Multi-chain graph construction\n\n- **Nodes** - **Normalized** addresses with **chain** prefix or namespace (e.g. `eth:0x…`, `sol:…`, `tron:…`) to avoid accidental merges.\n- **Edges** - Native transfers, **bridge** hops, **shared** contract interactions, **CEX** deposit\u002Fwithdrawal **matches** (where observable and **lawful** to use)-weight edges by **evidence** strength.\n- **Expansion** - Multi-hop with **pruning**: min value, **time** window, **asset** filter; **document** parameters to keep graphs **reproducible**.\n- **Community detection** - Louvain, Leiden, etc., on the **unified** graph-interpret as **hypothesis** groups.\n- **High-confidence merges** - Bridge **correlation IDs** as **hard** links when **unambiguous**; **soft** links from timing alone.\n\n## 3. Behavioral and temporal cross-chain heuristics\n\n| Signal | Use |\n|--------|-----|\n| **Timing** | Bursts across chains in **tight** windows-**coincidence** possible; tune thresholds |\n| **Sequence fingerprints** | Repeated swap → bridge → swap shapes-normalize for **popular** defaults |\n| **Mirrored notionals** | Similar **amounts** (after decimals) on linked legs-**approximate** |\n| **Shared funding** | Common **ancestor** or **faucet**-weak alone, stronger with other signals |\n| **CEX patterns** | Deposit\u002Fwithdraw **timing** \u002F **amount** bands-**often** opaque; **probabilistic** |\n| **Entropy \u002F frequency** | Cross-chain **feature** similarity-**optional** ML; **validate** on seeds |\n\n## 4. Advanced cross-chain signals (use with care)\n\n- **Deployer** similarity on EVM (**bytecode** hash, **creator** address)-same **code** ≠ same **operator** always.\n- **Oracle \u002F aggregator** usage fingerprints-**noisy** in popular DeFi.\n- **Privacy** tools and **mixers** - May **break** or **delay** tracing; discuss **observable** exits only-**do not** advise evasion.\n- **ML** propagation - Seed **high-confidence** clusters; **gate** expansion; report **false-merge** risks.\n\n## 5. Token and wrapped-asset normalization\n\n- Map **bridged** representations to a **canonical** asset id in your model (e.g. **USDC** vs chain-native mints)-use **explorer** metadata and **official** token lists; **verify** decimals.\n- **Mint\u002Fburn** parity - Compare **aggregate** flows on both sides when data exists; discrepancies may be **timing**, **fees**, or **incomplete** indexing-not automatically “laundering.”\n- **Round-trip** bridging - Can indicate **arbitrage**, **testing**, or **obfuscation**-**contextual**; avoid **definitive** moral labels without **corroboration**.\n\n## Toolchain and data sources (examples)\n\n| Layer | Examples | Notes |\n|-------|-----------|-------|\n| Bridges | Explorer UIs, project APIs | Confirm **message** format |\n| Graphs | Neo4j, NetworkX | Version **node** id scheme |\n| Analytics | Dune, Flipside | Multi-chain **decoded** tables |\n| Portfolio | DeBank, Zerion-class | Overview, not **sole** proof |\n| Labels | Arkham, Nansen | **Sanity-check**, not oracle |\n| Monitoring | Indexer webhooks | **Authorized** use, **ToS** |\n\n## Operational workflow (suggested)\n\n1. **Seed** - Any-chain address, tx, mint, or bridge event (**public**).  \n2. **Triage** - Immediate **bridge** legs and **destination** receipts.  \n3. **Graph seed** - Nodes\u002Fedges from **correlation IDs** + **first-hop** transfers.  \n4. **Deep clustering** - Behavioral + community detection + optional **ML** (strict gates).  \n5. **Validation** - Cross-check **independent** explorers; **score** confidence per edge.  \n6. **Evidence** - Unified diagram, **cross-chain** timeline, **Sankey** or equivalent.  \n7. **Follow-up** - Optional **watchlists** for **public** addresses (user’s own tooling\u002Falerts); **no** harassment or **unauthorized** surveillance.\n\n## Reporting\n\n- **TL;DR** - Scope (chains, time range), cluster count, **confidence** tiers.  \n- **Edge list** - Each link: **why** (bridge ID, timing, amount, etc.).  \n- **Limitations** - Missing **private** CEX data, **mixer** gaps, **label** errors.  \n- **Repro** - Queries, **block** heights, **parameters** for graph build.\n\n## Ethical and professional guardrails\n\n- **Precision** over recall for **public** accusations-**false** merges harm people.  \n- **Compliance** and **law** - High-stakes **AML** decisions need **process**, not heuristics alone (**crypto-investigation-compliance**).  \n- **Privacy tools** - Describe **observable** patterns **defensively**; **no** evasion help.\n\n**Goal:** Unify **fragmented** public trails into **testable** multi-chain cluster **hypotheses**-for **lawful** investigation, **risk** awareness, and **ecosystem** defense.\n",{"name":5,"description":7},"main","d10fe79c634de337daa2ad2fa82857c8a743616b",".agents\u002Fskills\u002Fcross-chain-clustering-techniques-agent",1,"https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion","https:\u002F\u002Fbastionagentique.com\u002F","https:\u002F\u002Fgithub.com\u002Fzkos-labs","https:\u002F\u002Fzkoslabs.org","A research-driven builders' organization advancing programmable trust infrastructure for Ethereum and interoperable open networks.","2026-11-13 21:01:45",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add zkos-labs\u002Fbastion --skill cross-chain-clustering-techniques-agent",{"tool":40,"command":41},"bunx","bunx skills add zkos-labs\u002Fbastion --skill cross-chain-clustering-techniques-agent",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zkos-labs\u002Fbastion --skill cross-chain-clustering-techniques-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcross-chain-clustering-techniques-agent\u002FSKILL.md",true,[],[49,57,64,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":53,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7213RCWV886P2R63MTQAEGW","bastion","Programmable Trust Runtime for Autonomous Systems. Orchestrates identity, policy, privacy, durable execution, and multi-chain settlement.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7213MYSJE23KMMTD95Y3M3Z","web2-api-firewall-administrator","Guides configuring Bastion Web2 API adapter policies for the Trust Runtime. Covers endpoint allowlists, provider budgets, rate limits, content inspection (PII\u002Fsecrets detection), header filters, and OpenAPI spec-based auto-configuration. Use when configuring API call security for AI agents, setting provider spending caps, inspecting outbound API traffic, or setting up the Web2 adapter.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb2-api-firewall-administrator\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7213HE08PE43M2H0QZENZP2","transaction-screening-workflow-concepts","Educational map of transaction-centric compliance screening-transfer as the atomic unit, deposit vs withdrawal direction, single and CSV import, transaction list and detail views, per-transfer screening, rescreen, and STR-style exports. Use when the user asks how monitoring UIs treat tx hashes, directions, or regulatory reporting hooks-not for legal filing advice or evading reporting.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftransaction-screening-workflow-concepts\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7213DQ7TVE986643SR105Y4","solana-tracing-specialist","Guides Solana-specific on-chain forensics-ATA resolution, SPL instruction parsing, transaction history via RPC and indexers (e.g. Helius-style APIs), fund-flow graphs, Solana clustering heuristics, and program authority review. Use when the user investigates Solana wallets, SPL tokens, DEX\u002FJito flows, rug or phishing patterns on Solana, or needs evidence-structured tracing reports with public data only.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-tracing-specialist\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M72138PB2HTKJ0J39WNSRCRR","solana-onchain-intelligence-resources","Companion to blockint-skills Solana work-official doc indexes and stacks for RPC\u002Findexers, sanctions and address intel MCP, web research, agent payments, graph UIs, Solana Foundation dev skills, Solana Policy Institute (policy\u002Fregulatory education), optional open-source Scrapy collection (BlockchainSpider), Impersonator Solana (dApp dev\u002Ftesting), coral-xyz sealevel-attacks (security pattern examples), Neodyme Solana Security Workshop (workshop.neodyme.io), and Osec Solana auditor introduction blog (osec.io). Use when the user needs pointers to Helius, Range AI, Tavily, PayAI x402, React Flow, Solana.com skills, or SPI alongside on-chain forensics-not as a substitute for reading current provider docs, legal counsel, or API keys.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-onchain-intelligence-resources\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M72134Y4PVHN6CQPHX9NKSHQ","solana-defi-vulnerability-analyst-agent","Guides discovery and documentation of Solana DeFi protocol risks from public code and chain state-Anchor\u002Fnative programs, PDAs, CPIs, oracles, pools, SPL mechanics, and historical tx reconstruction. Use when the user asks for Solana program security review, DeFi vulnerability triage, PDA or CPI safety, oracle or liquidity-pool risk, launchpad\u002Fbonding-curve issues, or evidence-backed severity findings without exploits or private keys.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-defi-vulnerability-analyst-agent\u002FSKILL.md",[],[]]