Thor Skill

CRITICAL RULES

1. Read reference files FIRST. When the user's request involves any topic in the reference table below, read those files before doing anything else. Briefly mention which files you are reading so the user can confirm the skill is active.
2. Information priority: (a) Reference files in this skill — always the primary source. (b) The thor repo source code at

   github.com/vechain/thor/v2

   for implementation details. (c) Web search — only as a last resort for topics NOT covered in references.
3. Prefer working directly in the main conversation. Plan mode and subagents do not inherit skill context and may produce stale answers.
4. After compaction or context loss, re-read this SKILL.md to restore awareness of the reference table.

Scope

• Architecture and package structure of the Go codebase
• Consensus: PoA v1/v2, PoS (Galactica), BFT finality
• Built-in contracts: Authority, Energy, Staker, Params, Prototype, Executor, Extension
• REST API endpoints and WebSocket subscriptions
• Storage: LevelDB, SQLite logdb, trie, pruning, node types
• P2P networking: discovery, block/tx propagation
• Cross-cutting flows: block production, transaction lifecycle, reward distribution, staking/delegation, chain sync
• Solo mode for local development
• Contributing to the thor codebase: build, test, add endpoints, fork config

• vechain-core — SDK usage, fee delegation, multi-clause transactions, dual-token model
• vechain-kit — VeChain Kit hooks, components, wallet connection, social login
• smart-contract-development — Solidity, Hardhat, testing, security
• stargate — NFT staking, validator delegation, VTHO rewards

Operating procedure

1. Identify the question type

• PM/architecture question → read

  architecture.md

  + relevant flow files
• Contributor question → read

  contributing.md

  + relevant package reference
• "How does X work?" → read the matching flow file(s)
• API question → read

  api.md

• Node operations → read

  architecture.md

  (node types, flags, ports)

2. Read before answering

3. Answer with context

• Reference specific packages, types, and files from the thor codebase
• For flows, trace through the packages step-by-step
• For PM audiences, lead with the high-level summary before diving into implementation
• For contributors, include package paths and key type names

Reference files