← 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": "Exchange compliance profile with jurisdiction, VASP status, and services",
  "included_files": [],
  "name": "exchange-diligence",
  "skill_md_contents": "---\nname: exchange-diligence\ndescription: \"Exchange compliance profile with jurisdiction, VASP status, and services\"\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\nOriginal procedure tool scope: `refdata___get_asset_by_id`, `refdata___get_asset_mappings`, `refdata___get_entity_by_code`, `refdata___list_vasps`.\n\n# exchange-diligence workflow\n\n> See [CONNECTORS.md](../../CONNECTORS.md) for tool details.\n\n## Usage\n\nexchange-diligence workflow <user input>\n\n### Canonical codes (IMPORTANT)\n\nDo **not** pass free-form names. `COINBASE` is not a canonical code and does not resolve to the exchange. Use canonical Lukka codes:\n\n| Venue | Code |\n|-------|------|\n| Coinbase Pro | `CPRO` |\n| Coinbase (parent) | `CBSE` |\n| Coinbase Prime | `CPRM` |\n| Kraken | `KRAK` |\n| Binance | `BINA` |\n| Binance US | `BIUS` |\n| Gemini | `GMNI` |\n| Bitstamp | `BSTP` |\n| OKX | `OKX` |\n\nIf the user types a free-form name, translate it to the code above before calling.\n\n## Flow\n\n> **NOTE:** This command builds the exchange profile from entity + VASP + asset-mapping data.\n\n1. **Entity info**: `refdata___get_entity_by_code({ code: \"<user input>\" })` \n2. **VASP data**: `refdata___list_vasps({ limit: 100 })`  -> find the row where `lukkaEntityCode` == `<user input>`. VASPs are NOT filterable by `entityCode` (it only bridges to mappings, not VASPs) - filter client-side on `lukkaEntityCode`; paginate via `offset` if not on the first page.\n3. **Asset listings + services**: `refdata___get_asset_mappings({ entityCode: \"<user input>\", mappingStatus: \"Active\", limit: 100 })` \n   - Count active listings\n   - Aggregate `supportedFunctionList` across all mappings: for each flag (`tradingSupported`, `custodySupported`, `lendingSupported`, `savingsSupported`, `stakingSupported`), set to \"yes\" if *any* mapping has it `true`\n\n### Optional: `--flag-risky` mode (expensive - user must explicitly request)\n\n4. **Flag risky assets**: iterate mappings from step 3 and per row call `refdata___get_asset_by_id({ assetLid: \"{lukkaAssetId}\" })`  to inspect `assetDetails.potentiallySuspicious` / `potentiallyMemeCoin` flags.\n   - Do NOT run by default (100+ calls for large exchanges)\n\n## Output\n\n### Exchange Due Diligence: {exchange_name}\n\n**Entity Profile**\n- Code: {entityCode}\n- Type: {entityType}\n- Country: {country}\n- Status: {status}\n\n**Regulatory**\n- Jurisdiction: {jurisdiction} (primary; subsidiaries not enumerated)\n- AML/KYC Process: {amlKycProcess}\n- VASP Registration: {status from list_vasps} or \"N/A\" if no VASP registration found\n- Note: Regulatory registrations per jurisdiction are provided via `list_vasps` (match `lukkaEntityCode` client-side).\n\n**Services** (aggregated from `supportedFunctionList` across all active mappings)\n- Spot trading: {yes/no}\n- Derivatives: {yes/no}\n- Lending: {yes/no}\n- Staking: {yes/no}\n- Custody: {yes/no}\n- Savings: {yes/no}\n- Note: based on supported asset function flags aggregated across listings\n\n**Asset Coverage**\n- Active listings: {count} (from step 3 `get_asset_mappings`)\n\n> Suspicious/meme coin counts are not resolved by default (requires N individual asset lookups). Use `--flag-risky` to iterate all mappings and check `potentiallySuspicious` / `potentiallyMemeCoin` flags.\n\n**Risk Flags**\n- {flag descriptions from entity/VASP data}\n"
}

SHA-256 of public snapshot: f3ab78311b99348224bcef3ed7ce3b08ef17c431742c13f811f7822c03259e7f