Bitcoin Forum

www.nodeisok.com (http://www.nado.live/)

Notice

NADO mainnet is released.

Installation

Linux

Direct installation


Alternate direct installation one-liner

Virtual environment installation
To go back to your screen, use To update your NADO installation, use from the directory where you have it installed.

Windows
There is a release page in GitHub (https://github.com/hclivess/nado/releases), which is periodically updated when major changes occur. The easiest way to run NADO for Windows users is to use the nado.exe binary from there.

It is also possible to install Python on Windows (https://www.python.org/downloads/) and run NADO directly. Command line instructions:
Direct installation

First download (https://github.com/hclivess/nado/archive/refs/heads/main.zip) the master branch from GitHub and extract the archive. Run the command line as Administrator and enter the following commands:
To run NADO, execute the following command: python3.10 nado.py

After installation, go to your browser and announce your peer to one of the nodes like this: http://127.0.0.1:9173/announce_peer?ip=144.91.103.83 (http://127.0.0.1:9173/announce_peer?ip=144.91.103.83). For this, you should have port 9173 open (https://www.google.com/search?q=port+forwarding+guide) so the node is accessible from the internet if you want to receive rewards. After this step, synchronization should start shortly.

Wallet
You can download the official NADO wallet here (https://github.com/hclivess/nado-microwallet) or on the release page of NADO (https://github.com/hclivess/nado/releases).
Remote access

After running the node, you can access it at http://127.0.0.1:9173 (http://127.0.0.1:9173/) from where all API calls used by the node itself are accessible. Here are some examples:

● http://127.0.0.1:9173/get_account?address=ndo6a7a7a6d26040d8d53ce66343a47347c9b79e814c66e29 (http://127.0.0.1:9173/get_account?address=ndo6a7a7a6d26040d8d53ce66343a47347c9b79e814c66e29)

Private key storage
In previous versions, private key was stored in the folder where NADO is installed, under private directory, specifically in the keys.dat file. With the latest version, this file is stored in user's home directory, in Linux and in Windows.

Is there anything unique?
Yes. No mining, minting, block production happens in every node at once, based on the deterministic principles of the blockchain. This is possible because block production is separated from the consensual layer. This removes all the selfish miner incentives, which cause issues like transaction exclusion in traditional PoW systems.

What is NADO?
NADO is short for Tornado. It is just another blockchain written from scratch with a highly experimental consensus algorithm, which was created to provide effortless mining for all participants with a public IP address. NADO is not a classic proof-of-work blockchain like Bitcoin. Unlike most other crypto, its focus is on accessibility to rewards for everyone. It has a fully elastic reward mechanism, rewarding users only when transactions are happening on the chain. Users can burn their share of tokens in order to increase their chances of winning more rewards in the future.

What's the reason for NADO?
NADO is a take on one of the newer trends, where users do not use graphics cards or specialized hardware for mining, nor do they have to own a large portion of tokens in order to be rewarded. It is inspired by IDENA and NYZO, while attempting to bring the barrier of entry even lower than those two by not requiring solving of puzzles or highly efficient machines for users to remain in a reward distribution cycle.

What does NADO do differently?
In NADO, every user generates new blocks at the same time. This is possible because users are not rewarded for mining blocks but for keeping the network running. After generating a block and receiving a reward, chances of receiving more block rewards are temporarily lowered based on the public IP address. Every IP address can only have one block generating node. While this excludes users without public addresses, it prevents node spamming to a degree.

Sounds interesting, can you elaborate?
There are multiple cycles for every block. It starts with accepting peers and transactions directly. In the second stage, transactions and peers are stored in a buffer for the following block so that transactions can stabilize across the network. NADO prefers decentralization to efficiency, which means it exposes consensus more than the individual node, which makes it more resilient regarding SPOF but less efficient.

But is there a premise?
The premise of NADO is that users stop being interested in decentralized value distributing projects because it becomes progressively more difficult for them to join them or remain as time goes on. The main reason for users to leave is not the lack of adoption, but the mismatch between adoption, distribution and inflation. Distribution is the single one most important aspect of a cryptocurrency project as proven in the success of NANO, where no single entity was capable of obtaining a high amount of tokens through monopolizing token distribution.

● Constant rewards are counterproductive: Users will keep running their nodes even though they are not receiving rewards in a particular moment because there is no block reward for a particular block because network activity is low. Fighting inflation is more important than hoping for users to not stop running nodes.

● Elastic distribution was one of the key promises of Vertcoin, one of the most popular cryptocurrencies of 2014. NADO puts these promises into practice.
● Litecoin was created as a Bitcoin with fair distribution. None of the projects mentioned above put large effort into marketing and were extremely popular nonetheless.
● Barrier of entry is directly correlated to fairness of distribution. This is an idea on which Steve Jobs built his entire business. Removal of hassles in Apple operating systems and simplicity of their mobile devices led to widespread adoption simply because there were no hurdles to adoption.
● Interestingly enough, some of the most successful "cryptocurrency projects" where pyramid schemes that had zero technology in them: Bitcoinnect and Onecoin. All users had to do there was to go on a website and click a button to invest money into something that did not exist. Why did they do it? Because it was easy.
● Combining great and accessible technology with perfect distribution and effective marketing is the key to successful adoption.


Why not only use the existing projects?
● With PoW, the problem is in the arms race.
● With PoS, the problem is in the rising price.
● With PoD, the problem is in the increasing difficulty to re-join mesh with more participants.

Proof of what?
Every node in the NADO ecosystem keeps track of what opinions other nodes have by sharing state checksums for current block producer pools, transaction pools, peer pools and block hash pools. Participants add credibility over time to those who share their opinions on what the state of the network is. The security principle is that any attacker needs to be connected to the network for a longer time than the legitimate nodes and postpone the attack until their network participation duration is longer than that of other nodes - to perform a 51% attack. If the legitimate nodes stay in the network longer than the attackers, it is impossible to attack.

Burn-to-Bribe system and governance
In the beginning, all users have the same chance at receiving a reward every block. If they succeed, they are issued both tokens and a penalty. This penalty lowers chance of further finding rewards in relation to users who have not been rewarded yet, but it can be negated by burning a portion of the coins they generated or obtained otherwise. Currently, the model is set up in 1:100 ratio, which means that 1 portion of burn negates 100 portions of penalty. Both penalty and burn are counted from the smallest unit of NADO, so the lowest penalty resolution is 0.0000000001 and the lowest burn/bribe resolution is 0.0000000010. This system was created as an additional measure against inflation after implementation of elastic distribution and burned tokens are used for governance purposes.

To burn your NADO, send it to the following address:
What about security?
There are no guarantees for security of NADO, mainly because of its highly experimental character. Compared to more excluding networks like Bitcoin, security will always be lower as the main focus is on lowering the entry level for new users to make mining as inclusive as possible.
How many decimals are there and what are the units called?

1 NADO can be split into 1,000,000,000 units.

Got some sci-fi tech mumbo jumbo?
● Cryptography: Edwards-curve Digital Signature Algorithm (Ed25519)
● Link hashing: BLAKE2b
● Block capacity: Capped at 250KB per minute
● Block reward: Between 0 and 5 depending on network usage
● Transaction throughput: 7 raw transactions per second
● Proof of Fidelity with aspects of majority and diversity
● noSQL MessagePack file-based atomized database system
● Optional MessagePack formatting in API
● Shared mining protocol
● Periodic intervals to enforce consensus stabilization
● Burn-to-Bribe deflationary incentive and governance
● The logo is a vortexed version of the Impossible Toroidal Polyhedron

Where can I learn more?

www.nodeisok.com (http://www.nado.live/)

It looks interesting. As I understand it, in order to mine this coin, you just need to launch the NADO application?

that is true, you just need to launch the application with your ports open towards the world - similar to NYZO but different

https://i.imgur.com/pt8cjSc.png (https://github.com/hclivess/nado/releases/tag/0.12)

0.12 Mainnet

• Rollback mechanism adjustments
• Peers loaded dynamically on startup
• Semaphore for asynchronous requests to prevent node overwhelming
• Quality of life logging and terminal output improvements
• Unreachables added to node API
• requests and aiohhtp replaced with tornado's native async libraries
• Various API improvements
• Outgoing peers limited to 24
• Dictionary collisions removed

https://github.com/hclivess/nado/releases/tag/0.12

Nice project, I have installed on windows and used the microwallet, it says the connection is timed out could not get balance from (ip here): HTTP connection pool timeout Read timeout, should I be doing anything / is it mining? I don't see any commands published seems new and fresh

Having some really bad problems that I can't fix - if anyone can help that would be great:

ports are open from 80-1000 and 1000-10000 - all firewalls disabled

Could not connect to get balance from 185.184.192.210: HTTPConnectionPool(host='185.184.192.210', port=9173): Read timed out. (read timeout=1)
Could not obtain fee: HTTPConnectionPool(host='185.184.192.210', port=9173): Read timed out. (read timeout=3)
Could not connect to get balance from 78.102.98.72: HTTPConnectionPool(host='78.102.98.72', port=9173): Max retries exceeded with url: /get_account?address=ndo5a4e39634ac027dbf6c9fb4ed48acdbc4668918207f0eb (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x0000018BEACAB9D0>, 'Connection to 78.102.98.72 timed out. (connect timeout=1)'))
Could not obtain fee: Expecting value: line 1 column 1 (char 0)
Could not connect to get balance from 144.91.103.83: HTTPConnectionPool(host='144.91.103.83', port=9173): Read timed out. (read timeout=1)
Could not obtain fee: HTTPConnectionPool(host='144.91.103.83', port=9173): Read timed out. (read timeout=3)
Could not connect to get balance from 5.189.152.114: HTTPConnectionPool(host='5.189.152.114', port=9173): Read timed out. (read timeout=1)
Could not connect to get balance from 144.91.103.83: HTTPConnectionPool(host='144.91.103.83', port=9173): Read timed out. (read timeout=1)
Could not obtain fee: HTTPConnectionPool(host='144.91.103.83', port=9173): Max retries exceeded with url: /get_recommended_fee (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x0000018BEACBFEE0>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it'))
Could not obtain fee: Expecting value: line 1 column 1 (char 0)
Could not obtain fee: Expecting value: line 1 column 1 (char 0)
Could not obtain fee: Expecting value: line 1 column 1 (char 0)
Could not obtain fee: Expecting value: line 1 column 1 (char 0)
Could not obtain fee: Expecting value: line 1 column 1 (char 0)
Could not obtain fee: Expecting value: line 1 column 1 (char 0)
Could not obtain fee: Expecting value: line 1 column 1 (char 0)
Could not obtain fee: Expecting value: line 1 column 1 (char 0)
Could not obtain fee: Expecting value: line 1 column 1 (char 0)
Could not obtain fee: Expecting value: line 1 column 1 (char 0)

This looks like a connectivity issue, where are you located? You can use a different node to announce. Try one of these: http://78.102.98.72:9173/peers
If it is the wallet that's causing you issues, I just added async code from node to wallet as well - selecting peers is now based on accumulated trust credit
Good luck

Also I would like to ask everyone to update their node before block 12000, we will have a fork to adjust mining to not prioritise burners over new addresses

https://github.com/hclivess/nado/releases
0.14 - Goatmilk is good for you Latest
- New burning bonus mechanism that prevents miners for going below bonus of new addresses, replaces the original 1/3 block burn competition idea
- Several terminal output improvements

How do you know if you are fully functional?  I am getting My Block Hash: then a block hash and such but I don't know what it should "look" like to understand if everything is functional.

Am I to understand  "NODE IS OK!" means I am good?

Yes, when you get that message it means you are good.

Heeeeeelp please!!!!!

 2022-12-09 07:31:24,337 INFO Period: 3
2022-12-09 07:31:24,337 DEBUG My Block Hash: e14ca95c2dc20e7fd18187c1bc304fbe495d13fa07cd8b280ffcc25583b77301
2022-12-09 07:31:24,347 DEBUG Majority Block Hash: None
2022-12-09 07:31:24,347 DEBUG My Transaction Pool Hash: None
2022-12-09 07:31:24,349 DEBUG Majority Transaction Pool Hash: None
2022-12-09 07:31:24,349 DEBUG My Block Producer Hash: None
2022-12-09 07:31:24,351 DEBUG Majority Block Producer Hash: None
2022-12-09 07:31:24,351 INFO Block Hash Agreement: 0%
2022-12-09 07:31:24,353 INFO Transaction Hash Agreement: 0%
2022-12-09 07:31:24,355 INFO Block Producer Agreement: 0%
2022-12-09 07:31:24,355 DEBUG Transaction pool: 0 + 0 + 0
2022-12-09 07:31:24,365 DEBUG Active Peers: 0
2022-12-09 07:31:24,365 DEBUG Block Producers: 0
2022-12-09 07:31:24,367 WARNING Emergency Mode: False
2022-12-09 07:31:24,368 WARNING Seconds since last block: 1969
2022-12-09 07:31:24,369 WARNING Buffer protection: False
2022-12-09 07:31:24,371 WARNING Unreachable: 0
2022-12-09 07:31:24,380 INFO Loop durations: Core: 0; Consensus: 0; Peers: 20
2022-12-09 07:31:24,746 WARNING Criteria for block production not met
2022-12-09 07:31:25,762 WARNING Criteria for block production not met
2022-12-09 07:31:26,765 WARNING Criteria for block production not met
2022-12-09 07:31:27,777 WARNING Criteria for block production not met
2022-12-09 07:31:28,786 WARNING Criteria for block production not met
2022-12-09 07:31:29,788 WARNING Criteria for block production not met
2022-12-09 07:31:30,804 WARNING Criteria for block production not met
2022-12-09 07:31:31,807 WARNING Criteria for block production not met
2022-12-09 07:31:32,090 INFO Gathered 0/2 peers in 1 steps, 2 failed
2022-12-09 07:31:32,090 INFO Loaded 0 reachable peers from drive, 2 failed
2022-12-09 07:31:32,814 WARNING Criteria for block production not met
2022-12-09 07:31:33,096 INFO No peers, reloading from drive
2022-12-09 07:31:33,098 INFO Testing ['78.102.98.72', '83.217.128.243']
2022-12-09 07:31:33,818 WARNING Criteria for block production not met

I think it's ok.
just had to wait!!


2022-12-09 10:34:13,026 INFO Period: 2
2022-12-09 10:34:13,026 DEBUG My Block Hash: 3f83217179a06d155b41f64408b7a62521f7e420e04569655d4a032d26ab6a9c
2022-12-09 10:34:13,026 DEBUG Majority Block Hash: 3f83217179a06d155b41f64408b7a62521f7e420e04569655d4a032d26ab6a9c
2022-12-09 10:34:13,027 DEBUG My Transaction Pool Hash: 92a0494738b04662b849d63530ac63e0321a0789b786c13b918bdc54800afa5e
2022-12-09 10:34:13,027 DEBUG Majority Transaction Pool Hash: None
2022-12-09 10:34:13,027 DEBUG My Block Producer Hash: 8084086db1e5799ecdd357ce1812386e1b580a7de7ad73cfdf56dd8742633164
2022-12-09 10:34:13,027 DEBUG Majority Block Producer Hash: 870a08b9ff096961fb7e45a25fe8997de3e646e787b93faa2cccf02c31750961
2022-12-09 10:34:13,027 INFO Block Hash Agreement: 100.0%
2022-12-09 10:34:13,027 INFO Transaction Hash Agreement: 0%
2022-12-09 10:34:13,028 INFO Block Producer Agreement: 62.5%
2022-12-09 10:34:13,028 DEBUG Transaction pool: 9 + 0 + 0
2022-12-09 10:34:13,028 DEBUG Active Peers: 24
2022-12-09 10:34:13,028 DEBUG Block Producers: 46
2022-12-09 10:34:13,028 WARNING Emergency Mode: False
2022-12-09 10:34:13,028 WARNING Seconds since last block: 55
2022-12-09 10:34:13,029 WARNING Buffer protection: False
2022-12-09 10:34:13,029 WARNING Unreachable: 2
2022-12-09 10:34:13,029 INFO === NODE IS OK! ===

is not!!!????

But I don't know where are my coins to win!!!??? ??? :'( :'(

>> Please Update your nodes <<

0.16 - Finding Wally (https://github.com/hclivess/nado/releases/tag/0.16)
- Critical block producer selection bug fix
- All nodes must upgrade

Hop on discord https://discord.gg/vnWTBym3wM (https://discord.gg/vnWTBym3wM), devs are there and they are really active.

Github commits: https://github.com/hclivess/nado/commits/main

Dec 10, 2022
- make own account the default
- update to value stored in memserver

Dec 11, 2022
- move get_from_status_pool to data_ops
- add protocol check
- add exception for remote peer address detection
- rename shadowed values
- move to pool ops
- allow graceful shutdown from local ip without key
- add user transaction buffer to api
- better error output

Dec 12, 2022
- make linewallet send transaction to multiple nodes
- calculate average trust only when there are values

Dec 13, 2022
- Emit penalty list via event bus
- Allow peer_limit to be configurable
- Expose penalties endpoint
- Remove verbose debug log
- Remove event listener on terminate
- minor changes to error reporting
- Fix exception logging in compounder

Windows defender is stopping me from downloading the wallet .

Greetings, there has been an issue with the compiler, which prevented Windows users from using the latest wallet.

With help of a guy from Blizzard and Riot Games, we were able to resolve the issue and Windows users can now enjoy the latest code.

https://github.com/hclivess/nado/releases/download/0.17/NADO_MicroWallet_setup.exe

this includes
- proper keys storage/usage (critical)
- massively improved connectivity and transaction broadcasting
- correct refresh rate

Please update

I've had this for 3/4 days....





2022-12-19 14:30:40 ERROR Error in consensus loop: 'NoneType' object is not subscriptable None
2022-12-19 14:30:41 INFO Period: None
Traceback (most recent call last):
  File "C:\PROGRA~2\NADO\loops\message_loop.py", line 32, in run
TypeError: 'NoneType' object is not subscriptable
2022-12-19 14:30:41 ERROR Error in message loop: 'NoneType' object is not subscriptable None
2022-12-19 14:30:41 INFO Failed to get latest block info: Expecting value: line 1 column 1 (char 0)
2022-12-19 14:30:41 INFO Error: 'NoneType' object is not subscriptable
Traceback (most recent call last):
  File "C:\PROGRA~2\NADO\loops\core_loop.py", line 441, in run
  File "C:\PROGRA~2\NADO\loops\core_loop.py", line 75, in normal_mode
  File "C:\PROGRA~2\NADO\loops\core_loop.py", line 59, in update_periods
  File "C:\PROGRA~2\NADO\block_ops.py", line 342, in get_since_last_block
TypeError: 'NoneType' object is not subscriptable
2022-12-19 14:30:41 ERROR Error in core loop: 'NoneType' object is not subscriptable None
2022-12-19 14:30:41 INFO Failed to get latest block info: Expecting value: line 1 column 1 (char 0)
Traceback (most recent call last):
  File "C:\PROGRA~2\NADO\loops\consensus_loop.py", line 166, in run
  File "C:\PROGRA~2\NADO\loops\consensus_loop.py", line 109, in refresh_hashes
  File "C:\PROGRA~2\NADO\block_ops.py", line 342, in get_since_last_block
TypeError: 'NoneType' object is not subscriptable
2022-12-19 14:30:41 ERROR Error in consensus loop: 'NoneType' object is not subscriptable None

---

with the update my balance is lost.




2022-12-19 14:36:55 INFO Key location: C:\Users\user\nado\private\keys.dat
2022-12-19 14:36:56 INFO Testing ['107.148.19.173', '137.175.66.89', '137.175.79.115', '155.248.229.212', '57.128.83.124', '65.108.130.175', '31.44.6.118', '31.44.6.227', '23.94.101.175', '89.25.168.204', '66.59.196.39', '154.38.163.42']
2022-12-19 14:36:56 INFO Compounder: Failed to get status from http://89.25.168.204:9173/status: HTTP 403: Forbidden
2022-12-19 14:36:58 INFO Compounder: Failed to get status from http://155.248.229.212:9173/status: [Errno 10061] Unknown error
2022-12-19 14:36:58 INFO Compounder: Failed to get status from http://31.44.6.227:9173/status: [Errno 10061] Unknown error
2022-12-19 14:37:06 INFO Compounder: Failed to get status from http://31.44.6.118:9173/status: [Errno 10061] Unknown error
2022-12-19 14:37:06 INFO Gathered 8/3 peers in 1 steps, 4 failed
2022-12-19 14:37:06 INFO Loaded 8 reachable peers from drive, 4 failed



[moderator's note: consecutive posts merged]

my addr has changed

Make sure to backup the 'private' folder which holds your address key pair.

When receiving error messages like the one below, it could help to completely remove the nado folder and install from scratch using the latest release (remember to back the 'private' folder before you remove the nado folder).

Error api-ms-win-crt-runtime-l1-1-0.dll . Visual C++ is installed, even several times with the removal of the old version. Windows 7.

Please join the nado discord server (https://discord.gg/6aEBWTvcTV) and ask in the support channel.

too late I lost all my coins with this update....!!!!

how you lost it?? if you have keep the keys.dat never lost coins!!!!

Did your address change? If it did, you still have your keys.dat in your wallet folder. That's your original wallet.
Code is relatively stable right now and key locations are unlikely to change in the future. If you find your old keys, you can copy them to

~/nado/private/keys.day
or
c:\users\...\nado\private\keys.dat

always make backups (and restore backups to confirm)

Your old keys are wherever you installed your wallet, so probably "C:\Program Files (x86)\NADO MicroWallet\keys.dat"

We are currently experiencing a network unstability due to a loopback bug. The code has been fixed and new features added, such as forced sync. You can force your node to sync from a single IP until it reaches a majority consensus with:


Also some of the most important parts are being streamlined and restructured, so code is easier to improve. Thank you for your patience.

Visual C++ is notorious with versioning. I recommend installing a different version. You need one that is compatible with latest Nuitka.

You should use version at least 14.2:

https://nuitka.net/doc/user-manual.html#windows-standalone-program-redistribution

0.18 - Moulin Rouge
https://github.com/hclivess/nado/releases/tag/0.18

2022-12-24 16:21:52 INFO === NODE IS OK! ===
2022-12-24 16:21:52 INFO Loop durations: Core: 0; Consensus: 0; Peers: 23
2022-12-24 16:21:56 ERROR Failed to get status from 127.0.0.0: Timeout while connecting
2022-12-24 16:21:56 ERROR Unable to reach 127.0.0.0 to get their address: 'bool' object is not subscriptable
2022-12-24 16:22:00 INFO block_producers out of sync with majority at critical time, replacing from trusted peer
2022-12-24 16:22:02 INFO Period: 2

2022-12-24 17:31:32 INFO === NODE IS OK! ===
2022-12-24 17:31:32 INFO Loop durations: Core: 0; Consensus: 0; Peers: 1
2022-12-24 17:31:36 INFO Switched to period 1
2022-12-24 17:31:39 ERROR Failed to get status from 127.0.0.0: Timeout while connecting
2022-12-24 17:31:39 ERROR Unable to reach 127.0.0.0 to get their address: 'bool' object is not subscriptable
2022-12-24 17:31:39 WARNING Added 0000:0000:0000:0000:0000:0000:0000:0001 to block producers
2022-12-24 17:31:39 WARNING Added 127.1.1.1 to block producers
2022-12-24 17:31:39 WARNING Added 127.1.1.2 to block producers
2022-12-24 17:31:39 WARNING Added 127.1.1.3 to block producers
2022-12-24 17:31:39 WARNING Added 127.0.0.2 to block producers
2022-12-24 17:31:42 ERROR Failed to get status from 0.0.0.0: [Errno 10049] Unknown error
2022-12-24 17:31:42 ERROR Unable to reach 0.0.0.0 to get their address: 'bool' object is not subscriptable
2022-12-24 17:31:42 INFO Period: 1
2022-12-24 17:31:42 DEBUG My Block Hash: 0ee15cc7a35db347aeca10036329bf1b5cff0b3f6c81c266a5eb79de5e9f4669
2022-12-24 17:31:42 DEBUG Majority Block Hash: 0ee15cc7a35db347aeca10036329bf1b5cff0b3f6c81c266a5eb79de5e9f4669
2022-12-24 17:31:42 DEBUG My Transaction Pool Hash: None
2022-12-24 17:31:42 DEBUG Majority Transaction Pool Hash: None
2022-12-24 17:31:42 DEBUG My Block Producer Hash: 62fcbe62284fa9f5f960fb945104a601b1202a45b931efaf8e3bc346ad899979
2022-12-24 17:31:42 DEBUG Majority Block Producer Hash: 78dbdef8b4f7f356a94f86b0d4f38ff39d37be442aab66d785abb2eac95dbb78
2022-12-24 17:31:42 INFO Block Hash Agreement: 70.83333333333333%
2022-12-24 17:31:42 INFO Transaction Hash Agreement: 0%
2022-12-24 17:31:42 INFO Block Producer Agreement: 20.833333333333332%
2022-12-24 17:31:42 DEBUG Transaction pool: 0 + 0 + 0
2022-12-24 17:31:42 DEBUG Active Peers: 24
2022-12-24 17:31:42 DEBUG Block Producers: 80
2022-12-24 17:31:42 WARNING Emergency Mode: False
2022-12-24 17:31:42 WARNING Seconds since last block: 27
2022-12-24 17:31:42 WARNING Buffer protection: False
2022-12-24 17:31:42 WARNING Unreachable: 64
2022-12-24 17:31:42 INFO === NODE IS OK! ===

> change mining algorithm at block 20000

Please update your nodes!
https://github.com/hclivess/nado/commit/71755e569e08902cd59409531989abcd3ad41581

The nado blockchain underwent a hard fork at block number 20000. After this point, transactions must include a target block in order to be included in the blockchain. Additionally, blocks cannot be older than the previous block.

All nodes on the network simultaneously create blocks and propose them to the network. The network then uses hash matching to determine the validity of the blocks, transactions, and block producer agreement. The majority of hashes will be considered valid. Nodes that are a part of the majority do not need to propagate blocks, as they have already created them. However, other minority nodes need to catch up and sync to the latest valid block. A block reward is given to the winner of a specific address mining algorithm.

If a node is unable to reach a particular node, that node will be removed from the block producer list and will not be considered for block production. When that node remains in the network and connectivity improves, it will be restored to the block producer list after a certain period of time.

Getting these errors

2023-01-13 23:59:27 ERROR Failed to validate spending during block preparation: ndo7289424823adc2d816daba6de88bf6a3fb6859f2e4bb8d spending more than owned in a single transaction
2023-01-13 23:59:27 ERROR Block preparation failed due to: ndo7289424823adc2d816daba6de88bf6a3fb6859f2e4bb8d spending more than owned in a single transaction
2023-01-13 23:59:27 WARNING Block production skipped due to: ndo7289424823adc2d816daba6de88bf6a3fb6859f2e4bb8d spending more than owned in a single transaction
2023-01-13 23:59:28 INFO Maximum reached cascade depth: 1
2023-01-13 23:59:28 INFO 146.59.150.90 knows block d4722a1b33a35e3511d496353d97883f35c22fe5860518efbfc55ae78d2d1e16
2023-01-13 23:59:29 WARNING Preparing block
2023-01-13 23:59:29 ERROR Failed to validate spending during block preparation: ndo7289424823adc2d816daba6de88bf6a3fb6859f2e4bb8d spending more than owned in a single transaction
2023-01-13 23:59:29 ERROR Block preparation failed due to: ndo7289424823adc2d816daba6de88bf6a3fb6859f2e4bb8d spending more than owned in a single transaction
2023-01-13 23:59:29 WARNING Block production skipped due to: ndo7289424823adc2d816daba6de88bf6a3fb6859f2e4bb8d spending more than owned in a single transaction
2023-01-13 23:59:30 INFO Maximum reached cascade depth: 1
2023-01-13 23:59:30 INFO 168.235.69.106 knows block d4722a1b33a35e3511d496353d97883f35c22fe5860518efbfc55ae78d2d1e16

There was a protocol change today.
Please update and purge existing blocks.

attach to node screen then stop the node (ctrl + c)

then let the node sync again.

0.2 - Chronos

This release completely reworks how block_time is understood in NADO, removing possible exploits and situations that have historically led to nodes desyncing. New mode switch is included for periods, nodes no longer add other lower protocol nodes to status pool, etc. Beware, a count of blank blocks have been generated for this system to work properly (starting at around 65,000).

https://github.com/hclivess/nado/releases/tag/0.2

There are no further big changes planned for the nearest future, thanks everyone for testing!

best promised project in crypto world!!!
also the  HCLivess  its very skilled give a try to check it people!!!

Version 0.2 runs fine on my server. Development is fast and it's all pretty easy to understand and to play with since it's written in Python. I like it!

Hi guys , i gave lots of try but node still not syncing and not finding any good peers ?! Any idea to help or solve ?! When I announce my ip to peers it says unreachable ! Please help

check if your port: 9173 its open if not you need to open the port

also you can join id discord to get more help!!!

https://discord.gg/EmjPn4f9

Thanks, after updating to 0.2 my node now runs and syncs perfectly!  :)

Nado Stability Release - 0.20.1 - Tranquility

This is a rollup stability update with some convenience features

- Peers now shuffle
- Rules for sync source have been changed
- Trust pool changes are no longer in real time so failure is impossible
- Flag display for sync selector
- Penalty in account display
- Culling mechanism fairer transaction throughput
- Separation on ops to their respective directory
- readable switch for API account view

https://github.com/hclivess/nado/releases/tag/0.20 (https://github.com/hclivess/nado/releases/tag/0.20)

Nado discord server is being newly organized by KaffinPX.
Discord Link: https://discord.gg/4X5BQShz (https://discord.gg/4X5BQShz)

Note: Please update your Nado node as soon as possible
- txid check above block 95000

After the update if you see "NODE IS OK" then your running node qualifies to mine nado.

Release: 0.21 - First Base
https://github.com/hclivess/nado/releases/tag/0.21 (https://github.com/hclivess/nado/releases/tag/0.21)

switch from tornado http client to aiohttp due to mem leak

https://github.com/hclivess/nado/commit/77fc179c7acb10558c35d4f4f62c4a50128caaaa

Nado Release: 0.23 - Northern Wind

- Implemented /health
- Added pympler
- Replaced Tornado AsyncHTTPClient with aiohttp to eliminate memory leak
- Memory leak is confirmed eliminated through testing

https://github.com/hclivess/nado/releases/tag/0.23 (https://github.com/hclivess/nado/releases/tag/0.23)


Nado - competitive fairness & energy efficient

Automate linewallet!

Release 0.24 - Lucky Numbers
Please update before block 111111

https://github.com/hclivess/nado/releases/tag/0.24 (https://github.com/hclivess/nado/releases/tag/0.24)

- Fees finally come into effect
- Upgraded peer trust loading to reflect relevant numbers
- Trust selection is now based on medians, not averages
- Supply calculations and endpoint (only for nodes that resync)
- Added support for WSGI
- Upgrades to capabilities of linewallet, including full automation
- More diagnostics for users in terminal output (in case Node is not OK)
- Added pympler dependency for Windows exe users

Nado Release: 0.25

- Proper decimal conversion
- Fee in microwallet is now displayed in decimals as requested
- Supply output
- Improvements in peer handling

https://github.com/hclivess/nado/releases/tag/0.25

Switch to enable loading of all peers, not only top 50 trusted peers.
https://github.com/hclivess/nado/commit/c74be0ef30136e0f662a46dd7e9db69c82c6868a (https://github.com/hclivess/nado/commit/c74be0ef30136e0f662a46dd7e9db69c82c6868a)

Nado Explorer Released

Official Nado Explorer: https://explorer.nodeisok.com/ (https://explorer.nodeisok.com/)
Fallback Nado Explorer: https://nado.network/ (https://nado.network/)

Github Explorer Open Source Code: https://github.com/hclivess/nado/blob/main/explorer.py (https://github.com/hclivess/nado/blob/main/explorer.py)

Coming Soon: Epic Enclaves - Nado & Bismuth Blockchain Game
A turn-based strategy game with strong RPG elements, item properties, and battles based on probability, focused on resource management and MMO experience, accommodating an unforeseen amount of players in a browser with API to integrate freely into any other platforms.

https://epicenclaves.com/ (https://epicenclaves.com/)

Epic Enclaves Test Game started - Winner Prize: 100 NADO

Here are the conditions for the Epic Enclaves tournament, starts September 1st:

After 14 days:

- the person with most EXP receives the full prize of 100 NADO

- they must be in state "alive: True" (not dead)

- PvP is encouraged but not mandatory (10% of exp transferred)

- the tournament will happen on the test server http://5.189.152.114:8888/

- the following structures don't work yet: Mine, Laboratory, Archery Range

Feedback at the Nado Discord server! Let the games begin.

And the Epic Enclaves Winner is: AFE

Congratulations!
Prize payment has been sent to the winner.
https://explorer.nodeisok.com/get_transaction?entry=b805d967ef2467517a5b1b34cc4d24a6b2898714692b662f4208090f3e0de78b (https://explorer.nodeisok.com/get_transaction?entry=b805d967ef2467517a5b1b34cc4d24a6b2898714692b662f4208090f3e0de78b)

sort of forgot about this thread so I updated the website etc

also you can play http://epicenclaves.com now
win prizes - blockcian integration pending for nfts
now im mainly concerned with game mechanics

Tournament: highest level weapon
Prize: 250 nado
Duration: 2 weeks

Game Link: https://epicenclaves.com/ (https://epicenclaves.com/)