# Network node

**Network node Prizm is any device that makes a transaction or block data into the network. Any device with the PZM software is treated as a node.**&#x20;

![](/files/-MSLfbvCMwgv-VlZIrSL)

{% hint style="info" %}
Nodes can be divided into two types: **marked** and **regular.**
{% endhint %}

A marked node is simply a node that is marked with an encrypted token received from the account's private key; this token can be decoded to show the specific PZM account address and balance that are associated with the node. The label placement act on a node adds a layer of accountability and trust, so that marked nodes are more reliable than those that do not have markings on the network. The more the balance of account is linked to a marked node, the more confidence is given to this node. While an attacker might want to mark a node to gain trust on the network and then use that trust for malicious purposes, the barrier to entry (the cost of PZM needed to build adequate trust) prevents such abuse.

Each node in the PZM network has the ability to process and transmit both transactions and block information. Blocks are scanned as they are received from other nodes, and in cases where a block check is not performed, the nodes can be "blacklisted" temporarily to prevent the dissemination of invalid block data.

Each node has built-in DDOS protection mechanisms (Distributed Denial of services) that limit the number of network requests from any user to 30 per second.


---

# 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://prizm.gitbook.io/pzm/wp/network-node.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.
