[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M720XHXM152FF4FR4JD6YJT6":3,"skill-same:01M720XHXM152FF4FR4JD6YJT6":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},"01M720XHXM152FF4FR4JD6YJT6","address-clustering-attribution",null,"Explains blockchain address clustering heuristics (UTXO common-input ownership, account-based deposit sweeps), entity and label layers, attribution confidence, peel chains and taint-style tracing concepts, and operational caveats. Use when the user asks about wallet clustering, linking addresses to the same owner, exchange deposit patterns, attribution, deanonymization limits, or how analytics firms group addresses.","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\u002Faddress-clustering-attribution\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: address-clustering-attribution\ndescription: Explains blockchain address clustering heuristics (UTXO common-input ownership, account-based deposit sweeps), entity and label layers, attribution confidence, peel chains and taint-style tracing concepts, and operational caveats. Use when the user asks about wallet clustering, linking addresses to the same owner, exchange deposit patterns, attribution, deanonymization limits, or how analytics firms group addresses.\n---\n\n# Address clustering and attribution\n\nEducational only. Do **not** assist with harassment, non-consensual doxxing, or sanctions evasion. High-stakes conclusions require **legal** and **compliance** process-not a vendor UI alone.\n\n## Why clustering exists\n\nAddresses are **pseudonymous**. **Clustering** infers that multiple addresses are **likely** controlled by the **same** real-world actor, so analysts can reason about “wallets” rather than isolated strings.\n\nAll clustering is **probabilistic**-wrong merges and missed links happen.\n\n## UTXO chains (e.g. Bitcoin)\n\n- **Common input ownership heuristic (CIOH)** - If two (or more) addresses appear as **inputs** to the **same** transaction, they are often assumed to be controlled by the **same** spender (standard wallet behavior). Exceptions exist (coinjoin, collaborative txs, some privacy techniques).\n- **Change outputs** - Many spends send value to a recipient **and** “change” back to a new address controlled by the sender; change-detection heuristics try to link those outputs to the same wallet cluster over time.\n\nPrivacy practices (coinjoin, careful coin selection) **weaken** naive clustering.\n\n## Account-based chains (e.g. EVM)\n\n- **Deposit–sweep patterns** - Exchanges often give users **unique deposit addresses**; funds later **sweep** to **hot\u002Fcold** pools. Analytics tools model “user deposit → exchange cluster” links using repeated patterns and timing.\n- **Smart contract wallets** - Multisig, account abstraction, and relayers can complicate “one EOA = one person” assumptions.\n\n## Entity, label, and tag (metadata layers)\n\n| Layer | Typical meaning |\n|-------|------------------|\n| **Entity** | A **cluster** of addresses grouped as one actor (person, fund, exchange)-often **multichain** |\n| **Label** | Name for a **specific** address (e.g. named hot wallet); may include **private** user labels |\n| **Tags** | Behavioral or risk descriptors (many per address)-often mixed **automation**, **analyst review**, **community** input |\n\n**Attribution** maps a cluster to a **real-world name** using OSINT, subpoenas, exchange cooperation, or leaks-**confidence varies**.\n\n## Flow tracing concepts\n\n- **Peel chains** - Series of rapid partial withdrawals\u002Fmovements sometimes used to **obfuscate**; pattern-based detection is **heuristic**.\n- **Taint \u002F proximity scoring** - Some tools score how closely funds relate to a **flagged** source along a path; **definitions differ by vendor** and are not legal verdicts.\n\n## Quality practices\n\n- Treat clusters as **hypotheses**; seek **independent** corroboration for accusations or compliance actions.\n- **Stale or wrong** labels and merges occur-especially after protocol upgrades or custodial restructuring.\n- **Mixer \u002F privacy** and **cross-chain bridges** break simple narratives-trace may be incomplete.\n\n## Related\n\nFor investigation **workflow** (OSINT steps), see **crypto-investigation-compliance**. For **platform use cases** (AML dashboards), see **blockchain-analytics-operations**. For **bridge-linked** and **multi-chain** unified clustering (graphs across chains, wrapped-asset normalization), see **cross-chain-clustering-techniques-agent**.\n","# Address clustering and attribution\n\nEducational only. Do **not** assist with harassment, non-consensual doxxing, or sanctions evasion. High-stakes conclusions require **legal** and **compliance** process-not a vendor UI alone.\n\n## Why clustering exists\n\nAddresses are **pseudonymous**. **Clustering** infers that multiple addresses are **likely** controlled by the **same** real-world actor, so analysts can reason about “wallets” rather than isolated strings.\n\nAll clustering is **probabilistic**-wrong merges and missed links happen.\n\n## UTXO chains (e.g. Bitcoin)\n\n- **Common input ownership heuristic (CIOH)** - If two (or more) addresses appear as **inputs** to the **same** transaction, they are often assumed to be controlled by the **same** spender (standard wallet behavior). Exceptions exist (coinjoin, collaborative txs, some privacy techniques).\n- **Change outputs** - Many spends send value to a recipient **and** “change” back to a new address controlled by the sender; change-detection heuristics try to link those outputs to the same wallet cluster over time.\n\nPrivacy practices (coinjoin, careful coin selection) **weaken** naive clustering.\n\n## Account-based chains (e.g. EVM)\n\n- **Deposit–sweep patterns** - Exchanges often give users **unique deposit addresses**; funds later **sweep** to **hot\u002Fcold** pools. Analytics tools model “user deposit → exchange cluster” links using repeated patterns and timing.\n- **Smart contract wallets** - Multisig, account abstraction, and relayers can complicate “one EOA = one person” assumptions.\n\n## Entity, label, and tag (metadata layers)\n\n| Layer | Typical meaning |\n|-------|------------------|\n| **Entity** | A **cluster** of addresses grouped as one actor (person, fund, exchange)-often **multichain** |\n| **Label** | Name for a **specific** address (e.g. named hot wallet); may include **private** user labels |\n| **Tags** | Behavioral or risk descriptors (many per address)-often mixed **automation**, **analyst review**, **community** input |\n\n**Attribution** maps a cluster to a **real-world name** using OSINT, subpoenas, exchange cooperation, or leaks-**confidence varies**.\n\n## Flow tracing concepts\n\n- **Peel chains** - Series of rapid partial withdrawals\u002Fmovements sometimes used to **obfuscate**; pattern-based detection is **heuristic**.\n- **Taint \u002F proximity scoring** - Some tools score how closely funds relate to a **flagged** source along a path; **definitions differ by vendor** and are not legal verdicts.\n\n## Quality practices\n\n- Treat clusters as **hypotheses**; seek **independent** corroboration for accusations or compliance actions.\n- **Stale or wrong** labels and merges occur-especially after protocol upgrades or custodial restructuring.\n- **Mixer \u002F privacy** and **cross-chain bridges** break simple narratives-trace may be incomplete.\n\n## Related\n\nFor investigation **workflow** (OSINT steps), see **crypto-investigation-compliance**. For **platform use cases** (AML dashboards), see **blockchain-analytics-operations**. For **bridge-linked** and **multi-chain** unified clustering (graphs across chains, wrapped-asset normalization), see **cross-chain-clustering-techniques-agent**.\n",{"name":5,"description":7},"main","d10fe79c634de337daa2ad2fa82857c8a743616b",".agents\u002Fskills\u002Faddress-clustering-attribution",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 address-clustering-attribution",{"tool":40,"command":41},"bunx","bunx skills add zkos-labs\u002Fbastion --skill address-clustering-attribution",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zkos-labs\u002Fbastion --skill address-clustering-attribution","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Faddress-clustering-attribution\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",[],[]]