Topic: [ANN]NADO 0.20 - PoW fairness, PoS efficiency, neither of both - page 2. (Read 2277 times)

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!

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

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!

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.

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

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.

> change mining algorithm at block 20000

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

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! ===

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

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

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

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.

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"

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

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

Please join the nado discord server and ask in the support channel.

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.

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).

my addr has changed

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]