Glancing over some of the recent speculations, let me clarify that DGEX has not ever claimed or mentioned the discussed bug of NXT sent to other address than what input to the client. Even if such a bug exists, DGEX losses are likely not related to that. They are related to other issues  - including the difficult to handle NXT network lag with 1000+ payments a day, unclear API deadline statuses in various stages of development etc. these fully acknowledged and now built into the risky business model.

Done.

https://forum.nxtcrypto.org/viewtopic.php?f=15&t=311&sid=ad4c1c402ca2067318b68e3ceb6c235f

Do you mind if I link to your video in my posts?

I saw the same thing and came straight here.  I hope he's on it.

+1

2014-01-04 19:42:54   0   0.000055   0
2014-01-04 19:38:16   0   0.000055   0
2014-01-04 19:38:16   0   0   0
2014-01-04 19:38:07   0   0.000055   0
2014-01-04 19:38:07   0   0.000055   0
2014-01-04 19:37:57   0   0.000055   0
2014-01-04 19:37:49   0   0.000055   0
2014-01-04 19:37:48   0   0.000055   0
2014-01-04 19:37:41   0   0   0
2014-01-04 19:37:40   0   0.000055   0
2014-01-04 19:37:28   0   0.000055   0

Just a temporary lowering of shields while implementing fees, some foolish trading 0's by themselves, nothing dangerous there 

NXT is dropping like a rock on CMC due to this new DGEX flaw.

This better be fixed asap!

7    Nxt   46,280 BTC   4.628e-05 BTC   999,997,986 NXT*   262 BTC   -35.79 %   

Just a temporary lowering of shields while implementing fees, some foolish trading 0's by themselves, nothing dangerous there