What's new in Duniter 1.5.5
Aug 24, 2017
- Fix: in the UI, changing the CPU% had no effect.
New in Duniter 1.4.13 (Aug 14, 2017)
- First official release of branch 1.4
- Features:
- Forks are now resolved within half an hour. It could take several hours in version 1.3.
- Sandbox pulling is now more frequent (every 4 hours instead of once a day).
- Revocation is now immediately taken into account.
- The selected newcomer between concurrent newcomers is now random.
- Better port selection with automatic configuration and UPnP.
- Technical:
- The source code has been migrated from JavaScript to TypeScript
- Duniter modules have been migrated back into duniter core repository
- wotb module has been upgraded to v0.6.x, with new wot computations
- Fork blocks are now stored on first reception, instead of storing them only on pulling
- Fixed bugs:
- Fix a major bug with membership renewal which were causing forks
- The /wot/requirements-of-pending/ URL is now quicker to respond
New in Duniter 1.3.12 (Jun 26, 2017)
- Allow revocations to be written correctly in the blockchain.
New in Duniter 1.2.1 (Apr 7, 2017)
- New major release bringing many new features:
- Swimming pools - swimmer:
- The swimming pool mechanism has changed: from now on, every member has an individual swimming pool on the whole network limited to 12 certifications. There is no longer a global pool for certifications.
- Non-members can no longer issue pool certification (it was possible until then).
- Any certification accepted by a node also records identity no matter what happens.
- A certification will therefore definitely create the certified identity on the node where the certification is accepted.
- This mechanism is important for anyone to register under the aegis of a member. It is sufficient that the new registrant sends his identity by any means whatsoever to a "godfather", so that it certifies it and sends this on a knot. The identity will then be created and replicated over the entire network.
- Replication of pools: swimmer:
- Now, each node will attempt to replicate the pool of other nodes at regular intervals. Replication occurs about every quarter of an hour and only affects identities with at least 1 pool certification.
- Replication only affects the Pools Trusted Canvas part, in the entire registration folder, but not the transactions.
- Other:
- Cesium goes from version 0.10.2 => 0.11.4
- Duniter weighs 15% to 25% lighter than before
- The keychain of your node is now located in the keyring.yml file of the data folder (~ / .config / duniter_default / default)
- Technical:
- Possibility to change the level of logs with the option --logslevel
- Some commands now prevent if they can be run node lit
- Possibility to know the status of the node with the status command
- Demo functions are now in a Duniter module
- When Duniter webstart is started, Duniter stops if the port is already in use
- The URL / wot / requirements now offers the whole registration file
- The URL / wot / requirements-of-pending / 3 returns the set of identity records with at least 3 certifications. URL greedy, limited to 30 minutes calls, 1 per second.
- The URL / tx / sources also returns the conditions field for each source
- Applying network patches GTest.
New in Duniter 1.0.0 (Mar 17, 2017)
- Official starting of Ğ1 currency!
New in Duniter 0.90.1 (Jan 24, 2017)
- Temporarily disable DOS protection, too much restrictive.
- Will be re-included later on with better parameters.
New in Duniter 0.90.0 (Jan 24, 2017)
- This version aims at validating the current Duniter code: the protocol has been stabilized, and GTest implements this protocol.Hence, Duniter 0.90 is the very last version before a first « real » currency.
- New features in this version are:
- engine's code has been rewritten according to the large rewriting of Duniter protocol (0.90)
- DOS (Denial of Service) protection
- module API, allowing external developers to extend the core of Duniter (adding services, for example RSS feed of the currency events, ...)
New in Duniter 0.80.0 (Jan 4, 2017)
- This version 0.80.0 is backward compatible with 0.60.0: these two versions can rub shoulders on the network, the protocol has not changed in the background.
- But this 0.80.0 marks the arrival of a new heart for Duniter, revised from top to bottom, in order to leave as little space as possible for bugs and allowing better maintenance. The protocol was greatly rewritten on this occasion. If you regularly experience desynchronizations or failures to resynchronize your node, then this version could change the deal!
- But this version also brings other new features:
- Cesium latest version 0.5.2
- Adding a module API (formerly a "specialized node") to extend the core
- Compilation fully compatible with yarn
- Best network hook at the launch of the application (avoids to fork alone in its corner)
- It also fixes some bugs like:
- Synchronization that fails
- The calculation of proof of work already outdated
- A bad refresh of the current block in the desktop application
- But the biggest change is clearly the new engine: its development required more than 80% of the time among the new and corrected bugs.
New in Duniter 0.50.0 (Nov 9, 2016)
- Changes:
- This new version tickets1 fence 14, which here is a quick list and details:
- DUP 0.5
- Change difficulty rule: the exclusion mechanism was abolished
- there was a potential loophole regarding identities, the blockstamp was not checked
- Network
- simplification of the IPv4 and IPv6 configuration
- a node can now be configured only in IPv6
- Debian package
- No. of the package version is now correct
- API
- Add the date of certification / wot / lookup
- DUP 0.5:
- The protocol was amended to included a major change now, nodes are no longer excluded from evidence of work.
- Indeed earlier, when a node calculated a number of blocks, he saw himself simply excluded from the calculation of the next block. This meant that there was blocking minority situations: if a major fork on the currency, each fork was not guaranteed to continue independently.
- This is no longer the case. From now on, Duniter based exclusively on customizing the difficulty over a node located blocks compared to the other participants, the more difficulty increases. A major point is that this difficulty now depends on the median number of units issued by member in the current window.
- Specifically, imagine a blockchain calculated by 3 members, who issued respectively [3, 3, 10] blocks. While the median is 3, and the member that issued 10 blocks has an above-median problem ((10 + 1) / 3 = 3.66) 366% for the calculation of the next block. Plus it is located above the median, the more difficulty increases.
- 2 members have issued 3 blocks, themselves, have no penalty. As well as those not yet participating in the calculations.
- network configuration
- Following various exchanges on the forum, I wanted to review the network configuration screen for simplicity.
New in Duniter 0.40.0 (Oct 18, 2016)
- This version exploits the latest Duniter protocol v0.4, which is planned to be the first exploitation ready protocol version.
- Protocol changes:
- a new formula for Universal Dividend: DU(t+1) = DU(t) + c² * M / N
- a new formula for personalized difficulty, aiming at better sharing the blockchain writing among nodes
- Software changes:
- Duniter now exploits Node.js v6
- allows to have additional P2P protocols in the list of peer endpoints
New in Duniter 0.31.2 (Oct 4, 2016)
- Duniter passes in version 0.31 and brings several new features and several important fixes, namely:
- P2P synchronization with simplified selection
- Operating multicore CPU
- new calculation tile
- management of new names of network interfaces
- storage size Duniter Desktop window
- better sharing of network data
- ability to have multiple machines with the same key
- This version is fully compatible with the previous version 0.30, the installation of the new version will not destabilize your node nor cause of network outlets, this version is a continuation of the Protocol 0.3.
New in Duniter 0.30.17 (Sep 14, 2016)
- As many of you have noted, it's not the network side joy many forks appeared, including some nodes are stuck in an old version of the blockchain.
- This is due to a bug during the unstacking phase divergent groups with the branch to join, leaving Phase incorrect data in the database, which led your node to a validation error when stacking new blocks, and was going in circles!
- There is also a block propagation problem, including the precise origin is unknown. However the party responsible for routing documents was reviewed, so as to correct a potential bug.
- To repair your node
- 1. Update your node
- 2. Reset and resynchronization
- If the node is not part of the main branch, or if you doubt, then it should start on the right foot by giving your zero node and the synchronizing again.
New in Duniter 0.30.16 (Sep 12, 2016)
- Bug fix: The blockchain not advance from approximately 15h, units adamantly refuse the next block because of a bug3 which made turnover Universal Dividend (its passage power of 10 top) unacceptable. Of course, this bearing must be accepted because the conditions are met. This is his moment is for him, must roll!
New in Duniter 0.30.2 (Aug 22, 2016)
- Fixes a bug where a wrong block was generated, which was stucking the blockchain.
New in Duniter 0.30.0 (Aug 22, 2016)
- What changed under the hood
- Blocks:
- This document now uses Version 3 and brings 3 modifications:
- New dividend formula: DU(t+1) = (1 + c) x DU(t)
- Any block now has a limited size! But this limit is dynamic and only depends on the size the network tends to give.
- The V3 blocks no more accept V2 transactions. Also, V3 blocks cannot be followed by V2 blocks (so transactions made with current clients like Sakia/Cesium will stop working soon!).
- Transactions:
- This document now uses Version 3 and brings 4 main modifications:
- the document is now dated using a blockstamp as any other Duniter document
- any transaction has a 1 week delay to be written in the blockchain before expiring
- the change problem has been solved
- a transaction now has a maximum length of 100 rows including date, issuers, signatures, sources, unlocks, outputs and an eventual comment.
- The personalized difficulty:
- This algorithm also changes: before, the personalized difficulty (the one giving the hardness level to find the next block for a given issuer) used to depend of other block issuers in a window of 100 blocks. From now on, this limit is dynamic and depends on current issuers of blocks.
New in Duniter 0.22.0 (Aug 10, 2016)
- Last version of the 0.2 protocol! Includes 2 new screens to:
- Manage backups of the local node
- Change CPU power
- Nodes now have 2 main security features:
- DDOS protection: each node has usage quotas on each URI it serves via the BMA API
- Spam protection: each node has a limited sandbox size for incoming documents, and refuses those considered spam
- You can now create backups of your local node and restore them through the UI
- A configuration screen has been added to change the CPU power parameter.
New in Duniter 0.21.3 (Aug 2, 2016)
- Duniter evolving and now goes to 0.21 higher, bringing new features to its desktop application! In the program :
- The portfolio Cesium directly integrated Duniter!
- visualization synchronization phases
- Updates notifications available
- new window "About"
- display the currency name
- And many fixes!
New in Duniter 0.20.3 (Aug 1, 2016)
- A new bug of the same ilk as the previous occurred, preventing some nodes to produce new blocks. This version only fixes this problem.