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: README.md
+23-2
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,26 @@ In order to send write transactions to the ledger you need:
39
39
### Pool of Nodes
40
40
- A network of Tendermint-based validator nodes (Validators and Observers) maintaining the ledger.
41
41
- Every validator node (`dcld` binary) runs DC Ledger application code (based on Cosmos SDK) implementing the use cases.
42
-
- See the proposed deployment in [deployment](docs/deployment.png).
42
+
- See the proposed deployment in [deployment](docs/deployment.png) and [deployment-detailed](docs/deployment-detailed.png).
43
+
44
+
### Node Types
45
+
-**Full Node**: contains a full replication of data (ledger, state, etc.):
46
+
-**Validator Node (VN)**: a full node participating in consensus protocol (ordering transactions).
47
+
-**Sentry Node:** a full nodes that doesn't participate in consensus and wraps the validator node representing it for the rest of the network
48
+
as one of the ways for DDoS protection.
49
+
-**Private Sentry Node:** connected to other Validators or Sentry nodes only; should not be accessed by clients.
50
+
-**Public Sentry Node:** clients and other nodes can access it; basically the same as an Observer node.
51
+
-**Observer Node (ON):** a full node that doesn't participate in consensus. Should be used to receive read/write requests from the clients. Technically can be a Public Sentry node.
52
+
-**Light Client Proxy Node**: doesn't contain a full replication of data. Can be used as a proxy to untrusted Full nodes for single-value query requests sent via CLI or Tendermint RPC. It will verify all state proofs automatically.
53
+
-**Seed Node**: provides a list of peers which a node can connect to.
0 commit comments