# Stream Payment - Sensors

#### Description

Data Collecting Machines work by streams. Every stream collects information for 10 minutes, meaning that in 1 hour there is a total of 6 streams made. Afterwards, 6 streams make 1 complete Block that is later processed for validation (via DriveMing and Validators).

#### Considerations

Stream Payments depend on the **total number** of active data collecting machines. In this first instance, we're going to analyze Sensors with the previous distribution.

### Example

Daily Token Unlock (sensors): 19,393.94\
Number of Sensors: 5,000

<figure><img src="/files/a1U4fdSectBwHYqS60zP" alt=""><figcaption></figcaption></figure>

In 1 day, a Data Collecting Machine should work for 8 hours (creating 8 complete blocks).\
That means that in 1 hour, Sensors earn 0.48 EDAT \
\= 3.88 / 8 = 0.48\
\
Nonetheless, 1 block is composed of 6 streams.\
The Sensor Reward per Stream is 0.08 EDAT\
\= 0.48 / 6 = 0.08

## Available Sensor Streams

If the Stream Payment for Sensors is 0.08 EDAT, then the total sensor streams that can be done in 1 day is 240,000.

<figure><img src="/files/Ehd2HHaRnnEJIBF4aZsS" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://envida-protocol.gitbook.io/envida/staking-and-rewards/data-collection-rewards/stream-payment-sensors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.