[ANN][ZEN] ZENCASH: Permanent, Distributed, and Fully Anonymous cryptocurrency

It's a bit unclear for me now...

Please can someone confirm to me how many nodes we can run with 1 ip ??

Based on white paper :

5.6 Zen Secure Nodes
The nodes are the key systems that maintain the Blockchain, accept transactions from
wallets, validate miner solutions, and act as the decentralized computing and communi-
cations system for cryptocurrencies. In Zen, all information transmitted to and from the
Secure Nodes is encrypted with valid certificates using TLS version 1.3 and further pro-
tected with Perfect Forward Secrecy (PFS). As part of the Secure Node capability, the
ZenCash application improves functionality by:
•
Extending RPC to enable AES encrypted data to reside in shielded transactions.
•
Extending RPC to enable perfect forward secrecy handshakes between public keys.
Secure nodes that meet all requirements will be rewarded the Secure Node portion of the
mining in a queued manner. Secure nodes need to monitor the #secure node channel. The
Secure Node payment system is intended to be operated in an auditable manner with clear
standards to maximize operability and minimize issues.
1. Basic infrastructure functions performed by Secure Nodes:
(a) Ensure all network communications are encrypted between nodes.
(b) Maintain full Zen blockchain.
(c) Provide certificate-based encryption connections for ZenCash wallet applica-
tions.
2. Secure Nodes meeting the requirements outlined below receive 3.5% of block coinbase
reward in a way that rewards uptime at full functionality:
(a) Operate node software on a capable system as specified by infrastructure re-
quirements

Recommended memory is more than 4 GB.
(b) Maintain entire ZenCash blockchain on the system.
(c) Provide a valid SSL certificate to the ZenCash Node software to use for com-
municating with other nodes and wallets.
(d) Keep at least 42 ZenCash on the server in a t
address for staking.
(e) Monitor the SecureNode channel for challenge messages from SecureNodeHQ
approximately every 10 minutes (in a z
transaction message field).
(f) Respond to challenge with identifying information of the Secure Node.
(g) Challenge response will be a combination of two things:
i. Send a shielded message to SecureNodeHQ containing public t
address and
GNUnet document location in message field.
ii. Publish a document to GNUnet signed with private t
address including:
A. Public t
address of staking Zen, which will also be used for reward
payment.
B. SSL certificate and IP address.
C. Block header from blockchain.
D. Other information that may be necessary to make sure it is a unique
server.
(h) Each Zen Secure Node must also be a peer on the GNUnet systems to publish
the challenge response anonymously and support the anonymous publications
from other elements of the system.
(i) Other potential requirements that may come up in future to allow ZenCash
system to use the Secure Nodes for consensus and computing power.
3. Zen Secure Node Payment System (Z-SNPS):
(a) Z-SNPS operated by a Zen DAO.
(b) Z-SNPS will track challenge responses from each Secure Node.
(c) Secure Nodes will be tracked and published by their t
addresses.
(d) Mined block will pay the 3.5% reward to the ZC-SNPS system, which will pe-
riodically distribute the ZenCash to Secure Nodes based on their uptime in the
defined time-period.
Because Zen will have this distributed computing network in the form of compensated
Secure Nodes, these nodes may be required to provide other computing services for the
network depending on the evolution of community consensus.