Native TOR!!!!

O NO!
#crysx
It is still optional

nativetor=1 (nativetor=0 by default)
It will also include support for OBFS4
Phew!
Does that means we can compile it 'out' of the daemon?
Next week we are preparing to move from the old server to the new servers for CWI-Pool Denarius (and others that are left). MUCH faster and MUCH more reliable CWI-Pool system.
#crysx
The Tor C Library will be included in the v3.0.0 code, so it is compiled with denariusd or Denarius-QT, you will need the additional library libevent-dev to compile. By default denariusd/Denarius-QT will boot up with nativetor=0, so it does not run unless nativetor=1 is in your denarius.conf.
Sweet sounds awesome!

OK - that is the reason why I asked.
The issue with the Centos 7 x64 static install if you recall, is that libevent does NOT work properly, regardless of what we did to run (yes @enkayz - even with your help as you may remember also). What this meant at that stage was when the daemon finally did compile, the daemon was not stable and had to be restarted every hour just to have it running and render RPC calls properly, otherwise it refused them.
When you completely removed TOR (which a damned useless entity ANYWAY when it comes to Crypto), the daemon was not only stable, but compiled and run flawlessly. There was no need for restarts and as far as the pool is concerned, it was very stable.
Re-Introducing TOR is just a waste of time and effort, and does not play any 'real' benefit for the wallet or transactions. Believe me - I know. SweepStakeCoin is in the same boat and as soon as we can remove TOR from that code, it will not be soon enough. Utterly useless for the coins performance and functionality. Why are you bringing it back anyway mate?
#crysx