mots-transaction-semantics
Points to the MoTS (Know Your Transactions) open-source Python/Scrapy research codebase-EVM transaction acquisition, semantic-vector extraction, and Etherscan-backed action labels (WWW 2023). Use when the user cites the MoTS paper/repo, needs legacy spider names (blocks.eth, blocks.semantic.eth, labels.action), or wants to relate transaction semantics to blockchain-analytics-operations-not as a substitute for current BlockchainSpider docs, RPC ToS, or legal review.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-13
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- mots-transaction-semantics
- description
- Points to the MoTS (Know Your Transactions) open-source Python/Scrapy research codebase-EVM transaction acquisition, semantic-vector extraction, and Etherscan-backed action labels (WWW 2023). Use when the user cites the MoTS paper/repo, needs legacy spider names (blocks.eth, blocks.semantic.eth, labels.action), or wants to relate transaction semantics to blockchain-analytics-operations-not as a substitute for current BlockchainSpider docs, RPC ToS, or legal review.
03 SKILL.md 正文
MoTS - transaction semantic representation (research codebase)
Reference skill. Upstream states that MoTS is merged into BlockchainSpider-prefer the BlockchainSpider documentation for current spiders and maintenance. This skill documents the standalone MoTS repository for paper reproduction, historical commands, and skill discovery.
- Repository: github.com/wuzhy1ng/MoTS
- Paper (in repo): MoTS_WWW_2023_manuscript.pdf - Know Your Transactions: Real-time and Generic Transaction Semantic Representation on Blockchain & Web3 Ecosystem (ACM WWW 2023).
What the standalone repo implements
| Step | Spider (examples from upstream README) | Role |
|---|---|---|
| Acquisition | blocks.eth |
Collect txs from RPC over block ranges; types can include external, internal, erc20, erc721, erc1155. |
| Semantics | blocks.semantic.eth |
Same shape of inputs plus transaction semantic vectors (per upstream description). |
| Labels | labels.action |
Transaction semantics labels sourced via Etherscan-class APIs (block-range oriented in examples). |
Storage: outputs under ./data (per upstream README). Config: upstream points to APIKEYS, PROVIDERS, and CONCURRENT_REQUESTS in settings.py.
Install (clone upstream)
The dependency file is named requiremets.txt in the repository (upstream spelling). After clone:
pip install -r requiremets.txt
Confirm the filename on the branch you use-it may be renamed in a future commit.
Example command shapes (placeholders only)
# Block-range acquisition (replace RPC and range; confirm spider names in upstream README)
scrapy crawl blocks.eth -a start_blk=<N> -a end_blk=<M> -a types=external,internal,erc20,erc721,erc1155
# Semantic vectors + data (same placeholders)
scrapy crawl blocks.semantic.eth -a start_blk=<N> -a end_blk=<M> -a types=external,internal,erc20,erc721,erc1155
# Label-oriented crawl (Etherscan-class API key must be set per settings)
scrapy crawl labels.action -a start_blk=<N> -a end_blk=<M>
If end_blk is omitted in upstream examples, collection may follow the chain tip-mind RPC cost and rate limits.
How to combine with blockint
| Task | Skill |
|---|---|
| Current Scrapy toolkit, Solana + EVM breadth | blockchain-spider-toolkit (BlockchainSpider) |
| Analytics / AML framing of “transaction meaning” | blockchain-analytics-operations |
| EVM DeFi triage | evm-solidity-defi-triage-agent |
Guardrails
- Prefer BlockchainSpider for new work if upstream merge note still applies-avoid duplicating unmaintained forks.
- Configure your own
APIKEYSandPROVIDERS; never commit or paste live keys. - Respect Etherscan (and similar) ToS and rate limits; semantic labels are research artifacts, not compliance verdicts.
- Lawful use only; outputs are not a substitute for licensed analytics or legal conclusions.
Goal: a discoverable pointer to MoTS and its relationship to BlockchainSpider for blockint users researching transaction semantics and KYT-style representations.
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.