Chainstack plans to deprecate Trader Nodes on December 1, 2026. We recommend moving your workloads to Global Nodes before then, as described in Trader Node deprecation.
Types
Chainstack supports 2 types of nodes for public chains: Global Node and Dedicated Node. Global Nodes are available for all networks by default. To get a Dedicated Node, you’ll have to contact us directly.Modes
For most of the available public chains, Chainstack supports deploying nodes in the following modes:- Full — a node that stores full blockchain data. However, it has limitations to how many blocks are available for querying.
- Extended — a full node that keeps more history than a standard full node, but not a complete archive. See Extended history.
- Archive — a node that stores full blockchain data and an archive of historical states, which makes it possible to query any block since the chain genesis.
- Trader — a node that propagates transactions to the global mempool at high speed. See Trader Nodes.
On smart-contract-enabled chains, a Full node keeps recent state; an Archive node adds all historical state from genesis. Bitcoin has no per-block historical state — chain state is the UTXO set, derived from the chain itself — so there is no separate Archive class. Chainstack Bitcoin nodes are non-pruned with
txindex enabled: every block and every transaction from genesis is queryable. Full does not mean pruned.Historical address queries (transaction history, balance at a past block) need an indexer like electrs — available as a Bitcoin Dedicated Node customization. Contact us to enable it.Archive semantics can also vary by protocol — for example, TRON archive mode serves the complete block and transaction history but not historical state, because java-tron has no state-at-block queries. See TRON historical data availability.Node mode describes data retention, not pricing. Requests are billed by request class — on some protocols every request bills as full even on archive-mode nodes. See Request units.Subscribing to pending transactions works in either mode, and the archive mode does not enable the txpool_content, txpool_contentFrom, and txpool_inspect pool-inspection methods — the node type decides those. See What gives you mempool access.