Documentation

Block validation

Start becoming an Ntity validator.

On this page

Introduction to becoming an Ntity validator

Validation is one of the most important elements for the sustainability of a blockchain. The PoA protocol is eco-friendly: it does not require much computing power and it is economical in electricity, as a simple Raspberry Pi computer (3, 4 or 5) is enough for validation.

The time made available to the Ntity network is rewarded according to the allocation for the validators.

The rules

The total number of anonymous nodes cannot exceed 33% of the network nodes, in order to prevent a 51% attack and keep the network sustainable.
Each anonymous node must have a unique public IPv4.
For each hour of validation, the validators receive a corresponding NTT sum, distributed equally among all validators. After a certain point, beyond 99 years, validators only benefit from the incentives linked to gas costs.
The minimum average uptime is 75% per day.
The reward is given once per day (every 8'640 blocks).
First come, first served: to register and become a validator, you need to deploy an Ntity:AddPeer certificate.
A running-in period was necessary to stabilize the blockchain: up to block 15'000'000 only Cryptolex-owned nodes were used, and no rewards were given.

Rewards

For example, in year 2 with 50 validators and a rate of 63'360 NTT/day, each validator receives 1'267 NTT/day.

Estimated year	From block	~NTT/day	Period supply
Nov 2021 – Apr 2025	running-in period	0	0
1	15’000’000	69’120	24’883’200
2	18’110’400	63’360	22’809’600
3	21’220’800	58’080	20’908’800
4	24’331’200	53’240	19’166’400
5	27’441’600	48’803	17’569’200
6	30’552’000	44’736	16’105’100
7	33’662’400	41’008	14’763’008
8	36’772’800	37’591	13’532’758
9	39’883’200	34’458	12’405’028
10	42’993’600	31’587	11’371’276
11	46’104’000	28’955	10’423’669
12	49’214’400	26’542	9’555’030
13	52’324’800	24’330	8’758’778
14	55’435’200	22’302	8’028’879
15	58’545’600	20’444	7’359’806
16	61’656’000	18’740	6’746’489
17	64’766’400	17’179	6’184’282
18	67’876’800	15’747	5’668’925
19	70’987’200	14’435	5’196’514
20	74’097’600	13’232	4’763’472
21	77’208’000	12’129	4’366’516
22	80’318’400	11’118	4’002’639
23	83’428’800	10’192	3’669’086
24	86’539’200	9’343	3’363’329
25	89’649’600	8’564	3’083’051
26	92’760’000	7’850	2’826’130
27	95’870’400	7’196	2’590’620
28	98’980’800	6’596	2’374’735
29	102’091’200	6’047	2’176’840
30	105’201’600	5’543	1’995’437
31	108’312’000	5’081	1’829’150
32	111’422’400	4’658	1’676’721
33	114’532’800	4’269	1’536’994
…	…	…	…
~99
	Validators total supply		298’598’400

Technical requirements

To take part in the Ntity validation process, you need an Ethereum client compatible with the PoA and Clique protocols. Several clients are available:

Geth (v1.13, with Clique)
Nethermind
Besu by Hyperledger (not fully tested yet)

Getting started

How to create an Ntity node (GitHub)
Docker images (amd64 / arm32 / arm64) (Docker Hub)

Validation with Raspberry Pi

The Docker images above also run on a Raspberry Pi (arm32 / arm64), to create your own Ntity node.

Ntity Box v1

Here is the first version of the Ntity Box: feel free to customize it and share your box! Download the Ntity Box STL file on GitHub.