what do you think ?

[
 No wonder vertoe and Amanda left. 

oh boy



and so it begins...

any1 looking to buy a baikal cube? dont have a lan connection at home and cant figure out how to enable wifi on the baikal cube.

What I ment to say with regards to the fix of InstantSend is that update 12.2 is still work in progress and that the code that handles this specific fix is therefore in theory still subject to changes. Personally I think they did already fixed it in 12.2

Also the InstantSend vulnerability was described in more detail at the Dash Conference : https://www.youtube.com/watch?v=d8ExmIqRqOk
(see the 40 minutes marker)

Basicly it has to do with how InstantSend can revert back to previous blocks (even after it got confirmed through proof of work).
A masternode owner with six masternodes could take advantage of that by calculating high scores for their own masternodes
by making a lot of InstantSend transactions offline.

Currently the fix to that vulnerability is :

* making it impossible for Instantsend to revert back to older blocks
* the calculatescore now includes a need for 15 confirmations, before it can calculate the score. This means a pack of 6 masternodes can not calculate/influence their score
   offline anymore.  

InstantSend is currently disabled through a spork and will be fixed in Dash update 12.2

Note 1 : as the fix is still work in progress, the code could still be subject to changes.
Note 2 : above mentioned InstandSend vulnerability and the planned fix is what i summarized from the presentation, it could be subject to misinterpretation from my side.

Preview of new Dash functionalities, to be implemented the coming months (revealed at the Dash conference) :

* global brokerage service (free bank transfers)
* integration into a host of new exchanges
* access to approx 20 new fiat currencies
* additional ATM manufacturer
* multistore discount application, integrated with some of the largest retailers
* healthcare usecase

Instantsend to be incorporated into almost all of them.