Prizm network node is any device that makes a transaction or block data into the
network. Any device with the PZM software is treated as a node. Nodes can be divided into two types: marked and regular.
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.
As with other cryptocurrencies, the PZM Ledger (Ledger of
transactions) is built and stored in a linked series of blocks
known as the blockchain. This workbook provides a
permanent record of the transactions that have occurred,
and it also establishes the order in which the transactions
were made. A copy of the Blockchain is stored on each
node in the Prizm network, and each account that is not
blocked on the node (by providing the private key of this
account) has the ability to generate blocks, providing that
at least one incoming transaction in the account has been
confirmed 1,440 times. Any account that meets these
criteria is called an active account. In PZM, each block
contains up to 255 transactions, all of which are preceded
by a 192-byte Header that contains identifying parameters.
Each transaction in a block is represented by a maximum of
160 bytes, and the maximum block size is 32 KB.
The version of the block, the height of the block and the block ID
Block timestamp expressed in seconds from the Genesis block
The ID of the account that created the block, as well as the public key of the account
ID and hash of the previous block
Number of transactions stored in the block
The total amount of PZM represented by transactions and commissions in the block
Transaction data for all transactions included in the block, along with transaction IDs
Length of the payload block and a value of a hash function of the payload block
The base target value and cumulative difficulty for the block
Site (ENG): parovoz-prizm >>>
Branch 1000+ of the Prism Train >>>
Branch 36 600+ of the Prism Train >>>
