Run any Skill in Manus with one click

mots-transaction-semantics

Stars3

Forks0

UpdatedMay 8, 2026 at 04:42

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

zkos-labs

zkos-labs/bastion

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name

mots-transaction-semantics

description

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 APIKEYS and PROVIDERS; 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 this repository

same repository

bastion

zkos-labs/bastion

Programmable Trust Runtime for Autonomous Systems. Orchestrates identity, policy, privacy, durable execution, and multi-chain settlement.

2026-07-213

bastion-how-to-use

zkos-labs/bastion

Guides agent developers on integrating Bastion (Programmable Trust Runtime). Covers SDK usage (BastionClient), REST API endpoints (/simulate, /policy, /override, /logs), interpreting audit logs and simulation results, configuring policy rules (allowlists, SOL caps, rate limits, blockint security checks), on-chain program interaction (audit trail, agent registry, circuit breaker), and deployment. Use when the user asks about integrating an AI agent with Bastion, sending transactions through the trust runtime, configuring security policies, reading audit trails, or deploying Bastion alongside autonomous agents.

2026-07-213

web2-api-firewall-administrator

zkos-labs/bastion

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.

2026-07-213

ethereum-ecosystem

zkos-labs/bastion

Comprehensive map of Ethereum trust primitives Bastion orchestrates. Covers wallets (Safe, EOA, AA), identity (ERC-8004, ENS, A2A), payments (x402, Pact), attestations (EAS, Sign, zkTLS), shared trust (EigenLayer), oracles (Chainlink, Pyth), bridges (Across, LayerZero), indexing (The Graph, Blockscout MCP), agent platforms (Olas, Virtuals), and developer tooling (ethskills, Base MCP, Foundry, Scaffold-ETH 2). Use when building on Ethereum trust standards.

2026-07-163

address-clustering-attribution

zkos-labs/bastion

Explains blockchain address clustering heuristics (UTXO common-input ownership, account-based deposit sweeps), entity and label layers, attribution confidence, peel chains and taint-style tracing concepts, and operational caveats. Use when the user asks about wallet clustering, linking addresses to the same owner, exchange deposit patterns, attribution, deanonymization limits, or how analytics firms group addresses.

2026-05-083

address-screening-workflow-concepts

zkos-labs/bastion

Educational map of address-centric compliance screening—tags vs markers, single and bulk import, address list and detail views, audit trails, blacklist and whitelist policy effects, and delete behavior. Use when the user asks how commercial screening UIs organize wallets/contracts, KYA-style exports, or rescreen policies—not for legal advice or bypassing controls.

2026-05-083

name

mots-transaction-semantics

description

MoTS — transaction semantic representation (research codebase)

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 APIKEYS and PROVIDERS; 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.