← Lukka Digital Assets IntelCONTENT HISTORY

Update to Lukka Digital Assets Intel

Snapshot Nov 4, 2026 · 18:11 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Lukka Digital Assets Intel and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "AML and VASP due diligence workflow patterns for digital asset compliance against the Lukka hosted MCP surface. Use when user asks about: AML risk, OFAC, VASP, due diligence, compliance review, address investigation, exchange compliance, or regulatory status.",
  "included_files": [],
  "name": "compliance-patterns",
  "skill_md_contents": "---\nname: compliance-patterns\ndescription: \"AML and VASP due diligence workflow patterns for digital asset compliance against the Lukka hosted MCP surface. Use when user asks about: AML risk, OFAC, VASP, due diligence, compliance review, address investigation, exchange compliance, or regulatory status.\"\n---\n\n## OpenAI connection notes\n\nTool identifiers below are raw operation names. The host may add a namespace;\nuse the matching advertised Global MCP tool. Resolve `<resolved-package-root>`\nto this plugin's installed directory before using paths. Workflow names identify\npackaged skills; they are not literal Claude slash commands.\n\n# Compliance Patterns\n\n**STANDALONE**: This skill provides AML/VASP compliance workflow patterns, risk categories, and exchange code conventions useful for structuring compliance reviews. **SUPERCHARGED**: When Lukka-AML, Lukka-RefData, and Lukka-UDA MCP servers are connected, it orchestrates live AML scoring, counterparty graph analysis, and VASP due diligence.\n\nWorkflow patterns against the hosted Lukka MCP servers: **Lukka-AML**, **Lukka-RefData**, **Lukka-UDA**. All tool names use the production wire format `<group>___<tool>`.\n\n> The hosted surface provides report generation (scoring, standard, enhanced, simplified) plus UDA on-chain data via Lukka-UDA.\n\n## Pattern 1: Address Investigation (default)\n\n```\n1. UDA___get_address_balance({ blockchain: \"eth\", address })         -> current holdings\n2. UDA___get_address_assets({ blockchain: \"eth\", address })          -> token coverage\n3. UDA___get_address_transactions({ blockchain, address,\n                                                    verbose:\"1\", limit: 100,\n                                                    get_newest:\"1\" })                -> recent activity preview\n4. AML___generateAmlScoringReport({ address, address_type: \"ETH\" })    -> light risk assessment\n```\n\n**Blockchain case**: Lukka-UDA uses lowercase (`eth`), Lukka-AML uses UPPERCASE (`ETH`).\n\n## Pattern 2: Deep AML Review (on request)\n\nAlways pipe Standard / Enhanced reports through the `large-data-processing` skill's `process_aml_report.py` - raw responses are 300-500 KB+ and overflow context.\n\n```\n1. cp \"<resolved-package-root>/skills/large-data-processing/references/process_aml_report.py\" /tmp/\n2. AML___generateAmlStandardReport({ address, address_type: \"ETH\" })   -> 325 KB report\n3. Save raw JSON to /tmp/aml_report.json\n4. python3 /tmp/process_aml_report.py /tmp/aml_report.json                            -> 2-3 KB summary\n5. (optional) AML___generateAmlEnhancedReport                         -> deepest detail (same pipe)\n```\n\n## Pattern 3: Counterparty Exposure\n\nFor counterparty exposure, use `generateAmlStandardReport` / `generateAmlEnhancedReport`\n(pipe through `process_aml_report.py`) - their payloads carry counterparty reasons with USD\nvalues. For raw address assets, use `UDA___get_address_assets`.\n\n## Pattern 4: VASP / Exchange Due Diligence\n\nUse canonical Lukka exchange codes. **Never** `COINBASE` - it is not a canonical code and does not resolve to the exchange. Use `CPRO` (Coinbase Pro), `CBSE` (Coinbase parent), `CPRM` (Coinbase Prime), `KRAK` (Kraken), `BINA` (Binance), `GMNI` (Gemini), etc.\n\n```\n# Build exchange profiles from get_entity_by_code + list_vasps + get_asset_mappings.\n1. refdata___get_entity_by_code({ code: \"CPRO\" })                 -> basic entity info\n2. refdata___list_vasps({ mappingStatus: \"Active\" })              -> VASP data, licenses\n   # filter client-side for lukkaEntityCode == CPRO (entityCode filter not reliably honored)\n3. refdata___get_asset_mappings({ entityCode: \"CPRO\",\n                                                       mappingStatus: \"Active\" })    -> listed assets + supportedFunctionList\n4. Per row: refdata___get_asset_by_id({ assetLid: \"{lukkaAssetId}\" })\n             -> inspect assetDetails.potentiallySuspicious / potentiallyMemeCoin\n```\n\nTo find suspicious listings, iterate `get_asset_mappings` results and inspect `potentiallySuspicious` / `potentiallyMemeCoin` flags client-side via `get_asset_by_id`.\n\n## AML Report Depths\n\n| Tool | Payload | Context impact | When to use |\n|------|---------|----------------|-------------|\n| `generateAmlScoringReport` | small | safe | Default / light screening. Available on all supported chains |\n| `generateAmlStandardReport` | 300-500 KB | MUST pipe | Investigation. Available on 30 chains (see below) |\n| `generateAmlEnhancedReport` | 500 KB+ | MUST pipe | Deep dive / escalation. Available on 30 chains (see below) |\n| `generateAmlSimplifiedReport` | small | safe | Light report. Available on 80 additional chains (see below) |\n\n### Report tier availability by chain\n\nUse SCORING for a light check on any chain. For a full or deep report use STANDARD/ENHANCED on the chains listed. SIMPLIFIED covers the additional chains listed below.\n\n- **SCORING** - available on all supported chains (light default).\n- **STANDARD / ENHANCED** - available on: `ADA, AVAX, BCH, BSV, BTC, CC, DASH, DOGE, DOT, DOT_AH, ETC, ETH, FIL, ICP, IOTA_MAINNET, IOTAEVM, LTC, MATIC, NEAR, NEO, RSK, SOL, TRX, VET, XDAI, XLM, XRP, XTZ, ZEC, ZKS`\n- **SIMPLIFIED** - available on: `ALGO, APT, ARBITRUM, ATOM, AZERO, BASE, BNB, BSC, CANTO, CELO, CHZ, CKB, COTI, CRO, CRONOS, DCR, DGB, DOGECHAIN, ECS, EGLD, EOS, ETHW, EVMOS, FET, FLOW, FTM, FUSE, GLMR, GRAM, HASH, HBAR, HT, IMX, IOTA, IOTX, KAVA, KCS, KDA, KLAY, KSM, LINEA, LSK, LUNA, LUNC, MINA, MNT, MOVR, NEO3, ONE, ONT, OP, PALM, PLS, QTUM, REEF, RON, ROOT, RUNE, SDN, SEI, SMR, STX, SUI, TAO, THETA, TLOS, TON, VIC, WAN, WAVES, WAX, XDC, XEC, XEM, XNO, XVG, XYM, ZEN, ZIL, ZKEVM`\n\n## AML surface scope\n\nThe hosted Lukka-AML surface provides **report generation** only: `generateAmlScoringReport` (light, any chain), `generateAmlStandardReport` / `generateAmlEnhancedReport` (30 chains, pipe through the processor), `generateAmlSimplifiedReport` (80 additional chains). Reports are stateless (no persistence between calls).\n\nFor needs outside report generation:\n- Sanctions/OFAC screening: read the scoring report's sanctions flags, or use an external OFAC list.\n- Bulk checks: call `generateAmlScoringReport` in parallel per address.\n- Address assets / raw transactions: use the Lukka-UDA tools (`get_address_assets`, `get_address_transactions`).\n\n## Key Rules\n\n1. **Default AML depth is scoring**. Escalate to Standard / Enhanced only on explicit user request, and always with the processor pipe.\n2. **Blockchain case**: Lukka-UDA=lowercase, Lukka-AML=UPPERCASE.\n3. **Canonical exchange codes**: `CPRO`, `CBSE`, `CPRM`, `KRAK`, `BINA`, `GMNI`. Never `COINBASE`.\n4. **Exchange profiles**: build from `get_entity_by_code` + `list_vasps` + `get_asset_mappings`.\n5. **Address assets**: use `UDA___get_address_assets`.\n"
}

SHA-256 of public snapshot: aa9f177056d991dc519338a060fb0dddcff31a8a5b6b980cd06f24713874f0bf