I have been away for a long time. When evolution will be released? Its like 1 year delay now of some sort.
Dash roadmap is as follows :
* v0.13 : currently on Testnet getting tested as final release candidate, so should be out relatively soon. This update will bring three DIPS to the Dash network : Special Transactions (DIP002), Deterministic Masternode Lists (DIP003) and
Simplified Verification of Deterministic Masternode Lists (DIP004). It will also bring a ton of improvements to InstantSend (Automatic InstantSend on simple transactions) and PrivateSend (multi-session mixing, makes mixing much faster).
Since these DIPS are going to be activated via combination of a BIP9-like deployment (bit 3) and new spork (`SPORK_15_DETERMINISTIC_MNS_ENABLED`), it could take awhile before our whole network has been upgraded.
* v0.14 : in development on Testnet, smaller update, focussed mostly on Long Living Masternode Quorums
* v1.0 : Dash Evolution release on all platforms
v0.13 was suppose to hit Mainnet in Q4, 2018 but it got delayed and split into v0.13 & 0.14.
Best is to bookmark following page and look it up from time to time :
http://www.dashroadmap.org/
v0.13.0 - Automatic InstantSend, which will improve the speed of most transactions at no additional cost;
~90% of transactions will be InstantSend. A logical question arises. Why not 100%?
Because it will only apply to those transactions that have 4 inputs or less (which is about 90%).
InstantSend
-----------
With further improvements of networking code it's now possible to handle more load, so we are changing
InstantSend to be always-on for so called "simple txes" - transactions with 4 or less inputs. Such
transactions will be automatically locked even if they only pay minimal fee. According to stats, this
means that up to 90% of currently observed transactions will became automatically locked via InstantSend
with no additional cost to end users or any additional effort from wallet developers or other service
providers.
I knew about the 4 inputs or less.
Why only with 4 inputs, not ALL transactions?
If we can 90%, why not do 100%?
Good question, maybe one of the Dash devs can provide an answer if they happen to still read this forum (some do).
A wild guess of mine would be that its maybe a network-load related issue : they managed to improve network efficiency, so that the network can handle more load and they are confident that the network can handle the transactions with 4 or less inputs but maybe they are less confident
that the network can handle the increased load of transactions when all inputs are included ? So they put a restriction on it for now? Just a guess...
