Releases: duniter/duniter
v0.20.3
v0.20.0
v0.20.0a33
New functionalities
Logs screen
Clic on the "Logs" menu and a window with the underlying node will be shown. Several options included! log level (info, warn, debug, ...), follow mode, pause mode, log size.
Auto-configuration window
This window shows up on start if the network configuration changed. Useful to have an always working node even for laptops!
Software version
The version of Duniter is now displayed in the window title bar, so you always know which software is running under the hood!
Bug fixes
Synchronization screen
The screen was not working with currencies including money, and lead to a never-ending loop in the sync process.
Data reset
The Node sometimes failed to reset data on Windows. Because this is Windows. Yep.
v0.14.2
v0.14.2a1
v0.14.1
0.14.1: Fix blockchain/difficulties URL.
* Fix blockchain/difficulties URL. * Add blockchain/difficulties § in summary.
v0.14.0
This release fixes several issues and provide new features:
Websockets
The API has changed:
- /websocket/block is replaced by /ws/block
- /websocket/peer is replaced by /ws/peer
This is a breaking change, however the previous websocket API was not used. It was using Socket.IO, and we prefered to completely remove any dependency to this lib. So a renaming was a clear message that the Socket.IO feature was pruned.
The new API uses classical websockets.
Automatic reconfiguration
It can now be used config --autoconf to automatically reconfigure the network parameters of the node. Previously, the --autoconf option was only available for init command which also reseted all the node's data.
Individual difficulties
A new HTTP method was added: /blockchain/difficulties. It gives the individual difficulty of every issuer in the last blocksRot blocks.
Example at: http://metab.ucoin.io/blockchain/difficulties
Memberships
The /bockchain/memberships method now sort the results by blockNumber, descendingly. Also a new field written was added to indicate wether the membership was written or not, and if it was it is valued with the block number in which the recording was made.
Example: http://metab.ucoin.io/blockchain/memberships/8Fi1VSTbjkXguwThF4v2ZxC5whK7pwG2vcGTkPUPjPGU
New Web of Trust module
The core of uCoin has been updated to use a C++ addon called wotb to compute Web of Trust constraints (for now, only the distance rule). This will avoid computation performances collapsing when the number of member strongly increase (hundred to million of members can be handled by wotb).
Logs
The logs have been filtered to only display major informations in the file. Also, the logs now display "near" proof-of-work found: for example when the PoW level is 5, we can see in the logs PoW with level 3-5:
Matched 3 zeros 000D71A34C30A5F15E0BF15556F43AFE68CD3A23 with Nonce = 160602 for block#49188
Matched 3 zeros 000138FD384C2830BDE0C1A948E80A43F1792006 with Nonce = 175740 for block#49188
Matched 4 zeros 0000DE99E7EDAC42611D4BF349F4DB6022E78D9B with Nonce = 179851 for block#49188
Matched 3 zeros 000B7AD1DE046B43420BDF28D19B7C9311E492B9 with Nonce = 183723 for block#49188
Matched 3 zeros 000B8F8941D6D831D24C87C2B78C906057950F4D with Nonce = 184068 for block#49188
Monetary mass issue
The monetaryMass field in database was valued at 0 for blocks generated by the node. This was not breaking the protocol, however it made the node unable to calculate new blocks with a UD. It had to wait for the network to find one.