FAQ

Most frequent questions and answers

Is Nyzo a token or a coin ?

Unlike many other projects you may know, Nyzo is not a token –  It’s a real coin and a very unique one too. Nyzo got developed entirely from the scratch and isn’t a fork from any existing blockchain – to deliver a fast and efficient blockchain with virtually unlimited possibilities for applications that utilize the Nyzo blockchain.

What is Proof-of-Diversity ?

Nyzo doesn’t relay on common known blockchain-techniques like Proof-of-Work (PoW) or Proof-of-Stake (PoS) – Nyzo introduces with Proof-of-Diversity (PoD) a fully new approach – PoD uses analysis of verification cycles to establish the authoritative form of the blockchain. It is a totally new proof system that relies on diversity of participation for strength.

READ MORE

How can i mine Nyzo ?

Nyzo is not minable – but absolutely earnable. You can earn Nyzo by creating Nyzo-Verifieres participating in the Nyzo-Mesh – rented on a cloud platform like Amazon Web Services (AWS), Microsoft Azure, Google Cloud, Hetzner or any other Cloud Provider. Nyzo is highly efficient and doesn’t need much computing power – so a small VPS is enough to get started. Of course, it’s also possible to host a verifier in your own home enviroment – but that’s way harder – the verifier will need to be online 24/7 and needs a public static IPv4 address too.

LEARN MORE

What is the Nyzo Mesh ?

The Nyzo-Mesh is basically the network containing incycle verifiers and verifiers waiting in the queue to join the cycle. Only incycle verifiers are eligible for earning Nyzo and verifying blocks on the blockchain. Joining the cycle is possible, if enough incycle-verifiers have voted for you or you got chosen through the lottery-system (since v502) by fortune.

What is a 'Sentinel' ?

A Sentinel protects an In-Cycle Verifer from dropping out of the cycle, if the Verifer is not able to produce a block in time while it’s his turn. For example: When a Verifier goes offline because of an hardware error or a DDoS attack – the Sentinel is monitoring the Verifier and will recognize that the Verifier isn’t able to produce the block. The Sentinel will send the block for the faulty Verifier instead and keep the Verifier in the Cycle.

Since v549 the Sentinel also protects queued Verifiers waiting for joinning the Cycle. In the past a faulty queued Verifier would just be skipped in the joining process, if iit couldn’t produce a block in due time. It’s always recommended to run atleast one Sentinel to protect your in- and out-of-cycle Verifiers.

How long does it take to get into the cycle?

That’s a though question. Basically that depends on participants waiting to join the Cycle and the current Cycle lenght. Since it’s a lottery system joining is based on pure luck. So it’s not possible to give a fixed estimated time. But it’s possible to calculate the probability of joining the mesh. A very good ressource for calculating the probability is NYZO.TODAY

My Verifier is yellow, what can i do?

When your verifier is Yellow it means that there is a tracking problem with it and it isn’t working properly. You should try to fix it as soon as possible, especially for incycle verifiers or you’re risking a drop out. First try to restart the verifier with following command:

sudo supervisorctl reload all

Check the mesh after a couple of minutes. If this doesnt work, follow the instruction from our

TROUBLESHOOTING GUIDE

My Verifier is red, what can i do?

Well, red isn’t good, right? When your verifier ist red it means that there is some communication problem with it. The mesh is not able to communicate with it and/or vice versa. Check if your VPS is online and reachable via SSH. It’s possible that your hoster have some trouble or your verifier got DDoS’ed. Try to restart your VPS with following command:

sudo reboot

Check the mesh after a couple of minutes. If this doesnt work, follow the instruction from our

TROUBLESHOOTING GUIDE