behavioral-risk-screening-concepts
Educational map of behavioral risk screening-volume, velocity, and transit-style heuristics at address and transaction level. Use when the user asks about suspicious pattern detection, structuring-like activity, rapid fund movement, or AML-style behavior rules-not for tuning systems to evade monitoring or for legal conclusions.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-13
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- behavioral-risk-screening-concepts
- description
- Educational map of behavioral risk screening-volume, velocity, and transit-style heuristics at address and transaction level. Use when the user asks about suspicious pattern detection, structuring-like activity, rapid fund movement, or AML-style behavior rules-not for tuning systems to evade monitoring or for legal conclusions.
03 SKILL.md 正文
Behavioral risk screening (concepts)
Educational reference only. Heuristic alerts are not proof of crime. Investigate with crypto-investigation-compliance, address-clustering-attribution, and on-chain evidence. For label-based exposure (sanctions, scam tags), see risk-exposure-screening-concepts. Product specifics live in your vendor docs (phalcon-compliance-documentation where applicable).
Behavioral Risk Engine (idea)
A behavioral risk engine flags suspicious transaction patterns using statistics and rules (thresholds, windows, frequencies) rather than-or in addition to-static address labels. Baselines may be global, peer-group, or customer-specific. False positives are common; triage before escalation.
Address-level behavior (common templates)
Many compliance stacks offer address-centric rules similar to the following:
| Template | What it approximates | Notes |
|---|---|---|
| Large-value transfers | Outbound or aggregate volume far above a typical-user or rolling baseline | Often uses USD notional at observation time; threshold is configurable. |
| High-frequency transfers | Many transfers in a short window, sometimes many just below a reporting or alert threshold (“structuring-like” pattern in traditional AML language) | Requires count and time bounds; may filter by asset. |
| Transit / pass-through | Address receives then sends most funds quickly, acting as an intermediary | Used as a layering-style signal; legitimate payment processors can resemble this-context matters. |
Illustrative scenarios (hypothetical):
- A wallet sends a single outbound transfer whose notional is far above the configured large-value threshold.
- An address sends fifteen transfers of just under a chosen threshold within 24 hours.
- An address receives a large amount and forwards nearly all of it within minutes to other addresses.
Use valid chain identifiers in real work; examples here stay generic to avoid implying real flagged wallets.
Transaction-level behavior (common templates)
At single-transaction granularity, platforms often add:
| Template | What it approximates | Notes |
|---|---|---|
| Large-value transfer | Transfer amount exceeds a user-defined notional cap | May apply per asset, per corridor, or per counterparty class. |
| Rapid transit | Funds leave shortly after arrival along a monitored path (same tx chain or multi-hop within a time window) | “Rapid” is policy-defined (for example within N minutes). Overlaps with transit heuristics at graph level. |
Illustrative scenario: a transfer exceeds a $100k policy threshold, or value moves A → B within five minutes while policy treats ten minutes as the rapid-transit window.
Relationship to exposure screening
| Engine style | Focus |
|---|---|
| Exposure (see risk-exposure-screening-concepts) | Who the funds touched-labels, hops, taint-style exposure. |
| Behavioral (this skill) | How the address or tx behaves-size, speed, frequency, pass-through timing. |
Both may fire together; analysts should reconcile narratives and avoid double-counting the same fact pattern.
Guardrails
- Do not assist with structuring advice to evade reporting thresholds or gaming monitoring rules.
- Do not treat alerts as adverse media or legal findings without case-level review.
- Legitimate businesses (payroll, market makers, bridges) can trigger behavioral rules-use corroboration and off-chain context when available.
Goal: shared vocabulary for behavioral AML-style pattern concepts aligned with common commercial monitoring templates, without binding any specific product configuration.
04 同仓库更多 Skills
bastion
Programmable Trust Runtime for Autonomous Systems. Orchestrates identity, policy, privacy, durable execution, and multi-chain settlement.
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/secrets 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.
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.
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/Jito flows, rug or phishing patterns on Solana, or needs evidence-structured tracing reports with public data only.
solana-onchain-intelligence-resources
Companion to blockint-skills Solana work-official doc indexes and stacks for RPC/indexers, sanctions and address intel MCP, web research, agent payments, graph UIs, Solana Foundation dev skills, Solana Policy Institute (policy/regulatory education), optional open-source Scrapy collection (BlockchainSpider), Impersonator Solana (dApp dev/testing), 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.
solana-defi-vulnerability-analyst-agent
Guides discovery and documentation of Solana DeFi protocol risks from public code and chain state-Anchor/native 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/bonding-curve issues, or evidence-backed severity findings without exploits or private keys.