mots-transaction-semantics
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.
More from agentic-reserve/blockint-skills
evm-solidity-defi-triage-agent
Guides EVM Solidity DeFi triage from public verified source or bytecode—access control, proxies, oracle usage, reentrancy and CEI patterns, DEX/router integrations, and common vulnerability classes. Use when the user asks for Ethereum or L2 smart contract security review, Solidity audit triage, OpenZeppelin proxy risks, or EVM-specific DeFi patterns—not for live exploits or private keys.
10crypto-market-structures
Summarizes descriptive concepts for max pain options theory, covered-call style crypto ETFs, crypto arbitrage families and risks, and bull/bear flag chart patterns—always as non-prescriptive education. Use when the user asks about max pain, premium income ETFs, arbitrage, funding rates, flash loans, or bull/bear flags in crypto trading context.
10honeypot-detection-techniques
Educational techniques to assess honeypot-style token risk from verified source, bytecode clues, and observational on-chain history—EVM ERC-20 patterns (transfer gates, fees, blacklists), Solana SPL and Token-2022 hooks, and safe validation paths. Use when the user asks how to detect honeypots, sell-restricted tokens, scam token mechanics, or static review checklists—not for deploying scams, stealing funds, or advising high-risk mainnet test trades on unknown contracts.
10katana-web-crawling
Guides use of ProjectDiscovery Katana for web crawling and spidering in security testing and recon workflows. Covers installation, standard vs headless mode, scope and rate limits, JSONL output, and piping from httpx or URL lists. Use when the user mentions Katana, projectdiscovery/katana, web crawling, spidering, endpoint discovery, attack surface mapping, or chaining crawlers in automation pipelines.
10solana-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.
10solana-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.
10