Skip to main content
A foundation node is a non-validating Intention node that ingests, executes, and exposes the full per-block state of the protocol. It is the canonical way to consume the Verifiable Execution Stream — a complete, byte-deterministic, cryptographically verifiable feed of every transaction, event, fill, mark-price update, funding payment, and liquidation produced by the chain.
Status: not yet published. The foundation node software will be released alongside the public testnet. Until then, treat the descriptions below as planning documentation.

​
Why run a foundation node

  • Strongest delivery guarantees. Foundation nodes replay execution locally and produce byte-identical records to every other honest node. This is what makes the historical data and the live stream trustworthy without a centralized indexer.
  • Lowest-latency feed. The VES is delivered as soon as a block is committed, without an intervening hosted gateway.
  • Full attribution. Every record carries the per-transaction attribution required by PTAD, so downstream accounting is auditable end-to-end.

​
What this page will contain

When the node ships, this page will document:
  • System requirements. CPU, memory, disk, and network requirements for steady-state operation.
  • Installation. Build and run instructions for the reference foundation node.
  • Configuration. Network endpoints, VES output configuration, and storage tuning.
  • Bootstrapping. How to bootstrap state from a published epoch snapshot and replay forward.
  • Operations. Monitoring, log review, and the relationship between foundation-node operations and the validator monitoring discipline.
For early integration questions, email contact@intention.xyz.