From: Cepreil Be:moo To: "jeffrey E." Subject: Re: Date: Wed, 03 Feb 2016 12:18:24 +0000 In US! If he can (you wrote only for me so I did not talk to anyone) with me and my friend who is involved 2016-02-03 15:10 GMT+03:00 Jeffrey E. >: Where ? with whom? . I will do anything that is helpful to you. / He is very well respected with both black and white hat hackers On Wed, Feb 3, 2016 at 7:06 AM, Cepreil Bensocoli > wrote: is it possible to meet with him? 2016-01-30 17:08 GMT+03:00 jeffrey E. <1 For you alone Forwarded messa e From: Vincenzo lozzo Date: Saturday, 30 January 2016 Subject: To: "Jeffrey E." <1 >: It's hard to tell w/o proper code/documentation (couldn't find much online). In general the four things are: 1) the devil is in the details, meaning that even if in theory it's all solid the implementation might have bugs. There's no definitive technical solution for that though 2) anything that is "custom" (eg: they have a custom wife protocol) is a red flag because it means that it hasn't been properly vetted and might be broken/buggy 3) there aren't enough details online to tell but it seems to me that to speed up the blockchain verification they partially centralize the network by using their own "supemodes" (essentially the wallets talk to the supemodes vs the actual blockchain). The security of those servers seems key to me and they gloss over it online 4) the mesh network implementation is completely up in the air (judging from what's public) and it could go horribly wrong. So that needs further verification Also (5), in general the disadvantage of distributed /open things is that it is a lot easier to steal money vs a closed network (like swift). Are you looking to invest into this thing? If so , suggest a few things: A) because problem (1) above is not completely solvable, they need to have a plan. Part of it is technical (do continuous code auditing, pentesting, on board proper crypto people, etc), the other part