> For the complete documentation index, see [llms.txt](https://docs.soniclabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soniclabs.com/sonic/node-deployment/node-hardening/appendix-e-glossary.md).

# Appendix E: Glossary

Plain-language definitions of the terms used in this guide.

| Term                       | Meaning                                                                                                                                                   |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **RPC**                    | The interface apps use to ask the node questions ("what's this balance?") and send transactions.                                                          |
| **Namespace / API module** | A group of RPC methods, e.g. `eth`, `debug`. You choose which groups are enabled.                                                                         |
| **Tracer**                 | Code that runs alongside a transaction to report what it did. Built-in tracers ship with the node; custom JavaScript tracers are supplied in the request. |
| **systemd**                | The program that starts and supervises services on most Linux servers.                                                                                    |
| **Service file / unit**    | The file telling systemd how to run the node (`systemctl cat sonic` shows it).                                                                            |
| **Drop-in file**           | An extra file in `sonic.service.d/` that adds settings to a service without editing the original.                                                         |
| **Sandbox**                | Restrictions placed around a program so it can only do what it needs to.                                                                                  |
| **Private address ranges** | IP addresses used only inside networks: `10.x`, `172.16–31.x`, `192.168.x`, plus a few special ranges. Your internal servers live here.                   |
| **Metadata service**       | A special address (`169.254.169.254`) cloud servers use to fetch their own settings and credentials.                                                      |
| **Proxy**                  | A program that sits in front of the node, checks each request, and forwards only the allowed ones.                                                        |
| **Pivot**                  | When an attacker uses one compromised machine to attack others on the same network.                                                                       |
| **Statically linked**      | The program file contains everything it needs and doesn't load system libraries.                                                                          |
| **Capability**             | One specific piece of `root`'s power (e.g. using ports below 1024) that can be given to a non-root program on its own.                                    |
| **LTS**                    | "Long-term support": an operating system release that gets security updates for several years.                                                            |
| **Load balancer**          | A service (often from your cloud provider) that spreads incoming requests across several servers.                                                         |
| **Validator**              | A node that takes part in consensus by signing consensus messages. It runs no RPC.                                                                        |
| **Signing key**            | The validator's key for signing consensus messages, kept in the node's data folder. It can't move funds, but misuse gets the validator penalized.         |
| **Validator wallet**       | The account that registered the validator and holds its self-stake. It belongs off the server, preferably on a hardware wallet.                           |
| **Double-signing**         | Two nodes signing with the same validator key. The validator is removed from the network and its stake is slashed.                                        |
