You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/validators/README.mdx
+3-7Lines changed: 3 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,10 +13,8 @@ Stellar is a peer-to-peer network made up of nodes, which are computers that kee
13
13
14
14
This section of the docs explains how to run a validator node, which participates in consensus to validate transactions and determine network settings. A validator node _should not_ be used for network data access and transaction submission. There are two varieties of _non-validating_ nodes that can be used for those purposes, each of which has its own process for set up, interaction, maintenance, and monitoring. They are:
15
15
16
-
1.[**Horizon Nodes**](../data/apis/horizon/README.mdx) can be used for submitting transactions, as well as exposing a REST API service to query and retrieve network state.
17
-
2.[**Stellar RPC Nodes**](../data/apis/rpc/README.mdx) can be used for simulating and/or submitting transactions, as well as exposing an RPC service to query and retrieve current network state.
18
-
19
-
If you are interested in Horizon or RPC nodes, please explore those docs.
16
+
1.[**Stellar RPC Nodes**](../data/apis/rpc/README.mdx) can be used for simulating and/or submitting transactions, as well as exposing an RPC service to query and retrieve current network state. This is the best choice for real-time use-cases.
17
+
2.[**Galexie Nodes**](../data/indexers/build-your-own/galexie/README.mdx) can be used for retrieving and storing network data en masse for further processing. Notably, it does _not_ support transaction submission so is more suitable for indexers or analytics use-cases.
20
18
21
19
If you are interested in running a validator node — because you issue an asset that you would like to help secure through transaction validation, because you want to help increase network health and decentralization, or because you want to participate in network governance — then this section of the docs is for you. It explains the technical and operational aspects of installing, configuring, and maintaining a Stellar Core validator node, and should help you figure out the best way to set up your Stellar integration.
22
20
@@ -51,9 +49,7 @@ There are two types of validator nodes, and they perform the same basic function
51
49
52
50
<Alert>
53
51
54
-
In the past, there was also a **Watcher** node, which was designed to run alongside Horizon for transaction submission and observing ledger changes, but not participate in validation or history publication.
55
-
56
-
This architecture was **deprecated** as of [Horizon 2.0](https://www.stellar.org/developers-blog/a-new-sun-on-the-horizon), which bundles an optimized "Captive" Core for its operational needs.
52
+
Non-validating nodes, like Stellar RPC or Galexie, bundle an optimized "Captive" Core to serve their operational needs.
0 commit comments