> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Modes and types

> Understand Chainstack node deployment modes including full, archive, elastic, dedicated, and trader node types with their capabilities and trade-offs.

## Types

Chainstack supports 2 types of nodes for public chains: elastic node and dedicated node. Elastic 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.
* 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](/docs/warp-transactions).

<Note>
  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](https://github.com/Blockstream/electrs) — available as a [Bitcoin dedicated node customization](/docs/features-availability-across-subscription-plans#node-customization). [Contact us](https://chainstack.com/contact/) 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](/docs/tron-tooling#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](/docs/request-units).
</Note>

<Info>
  ### Advanced options on paid plans

  Dedicated nodes, archive nodes, debug & trace APIs are available on [paid plans](https://chainstack.com/pricing/).
</Info>