> For the complete documentation index, see [llms.txt](https://docs.silos3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silos3.com/node/overview/payout.md).

# Payout

### Introduction

Storage Node Operators are compensated for the resources used by SILO Orbitals for their nodes every month. Our payout policy and details can be found in the [SILO Node Operator Terms and Conditions](https://www.silos3.com/legal/supplier-terms-conditions/). In the event of a conflict between this documentation and the Node Operator Terms & Conditions, the Node Operator Terms & Conditions shall govern.

***

### Understanding How Storage Nodes are Paid on the SILO Network

This document explains how Storage Node Operators are compensated for storing data and providing bandwidth. Node Operators are paid for the actual resources used by SILO-operated Orbitals. Any Orbitals operated by third parties not associated with SILO may have different terms, rates, and payment methodologies.

***

### Paid Resources

SILO Nodes share unused hard drive capacity and bandwidth with the SILO network and are compensated for the following:

1. **Storage of Storage Materials on Space:**\
   Compensation for the storage space used by Orbitals and users. This is calculated in GB-hours per month and paid monthly at the rates listed below.
2. **Egress related to Nexus Clients:**\
   Compensation for bandwidth used when users retrieve data from the network through registered Nexus applications. This is calculated in GB of bandwidth utilized and paid monthly at the specified rates.
3. **Egress related to file repair:**\
   Compensation for bandwidth used when SILO Orbitals retrieve data from Storage Nodes for the purpose of file repair. This is calculated in GB of bandwidth utilized and paid monthly at the specified rates.
4. **Audit Bandwidth:**\
   Compensation for bandwidth used when SILO Orbitals retrieve data to perform audits. This is calculated in GB and paid monthly at the specified rates.

***

### Exclusions

Storage Node Fees will not be paid for the following types of resource usage:

* **Storage of Garbage Data:** Data on a Storage Node that was not removed after deletion by a Nexus client. Such data will be removed by the SILO garbage collector function.
* **Other Resources:** SILO will not compensate for any other resources not explicitly identified above.

***

### Current SILO Node Payout Rates

| **Payment Category**       | **Rates (as of Jan 1st, 2025)** |
| -------------------------- | ------------------------------- |
| Storage (per TB per Month) | **$2.03**                       |
| Egress (per TB)            | **$2.70**                       |
| Audit/Repair (per TB)      | **$2.70**                       |

***

#### Important Note

All payouts are made in **SILO tokens**. For example, if your payout totals $100, you will receive $100 worth of SILO tokens. The SILO token's value will be calculated based on its current price as listed on [CoinGecko](https://www.coingecko.com/) or a recognized CEX exchange at the time of the payout.

***

For detailed information on how data storage and bandwidth are measured, refer to [SILO Pricing Documentation](/home/pricing.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.silos3.com/node/overview/payout.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.