Skip to main content
Skip to content
Case File
efta-02395736DOJ Data Set 11Other

EFTA02395736

Date
Unknown
Source
DOJ Data Set 11
Reference
efta-02395736
Pages
2
Persons
0
Integrity

Summary

Ask AI About This Document

0Share
PostReddit

Extracted Text (OCR)

EFTA Disclosure
Text extracted via OCR from the original document. May contain errors from the scanning process.
From: Vincenzo lozzo Sent: Sunday, January 31, 2016 9:40 AM To: jeffrey E. Subject: Re: Hmm I realized that yesterday I might h=ve drown you in too much tech details, sorry. I th=nk the short answer is: aside from the mesh network (which is doubtful and a=bit weak, mostly for lack of details) the rest mostly sounds good/feasible i= theory. The practice might be, and almost always is, weaker. </=iv> The stuff I said yesterday are the things I would st=rt going after first if I were tasked to attack it. Sent f=om my 1phone On Jan 30, 2016, at 13:27, V=ncenzo lozzo <[email protected]</=» wrote: <mailto:[email protected]> =div>Sent from my 1phone On Jan 30, 2016,=at 13:16, Vincenzo lozzo <a: mailto: wrote: It's h=rd to tell w/o proper code/documentation (couldn't find much online). In ge=eral the four things are: 1) the devil is in the details, meaning th=t even if in theory it's all solid the implementation might have bugs. Ther='s no definitive technical solution for that though 2) anything that=is "custom" (eg: they have a custom wifi protocol) is a red flag because it=means that it hasn't been properly vetted and might be broken/buggy </=iv> =) there aren't enough details online to tell but it seems to me that to spe=d up the blockchain verification they partially centralize the network by u=ing their own "supernodes" (essentially the wallets talk to the supernodes v= the actual blockchain). The security of those servers seems key to me and t=ey 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 t=at needs further verification Also (5), in general the disadvantage o= distributed /open things is that it is a lot easier to steal money vs a cl=sed network (like swift). EFTA_R1_01427338 EFTA02395736 Are you looking to invest into this thing? If so= , I'd suggest a few things: A) because problem (1) above is no= completely solvable, they need to have a plan. Part of it is technic=l (do continuous code auditing, pentesting, on board proper crypto people, e=c), the other part is legal/financial and pr. Specifically they should have=some kind of insurance and they should have a pr disaster recovery plan. A b=g disadvantage of decentralized system is that you don't have anybody to tr=st and you don't have a closed network that can make stealing money hard, t=ey need to address that B) realistically nobody is going to attack t=em until they become significant enough from a financial standpoint. This g=ves them time to work on A. That said they should avoid making enemies (the="disgruntled" hacker type) </=iv> Hope this is useful, if you get more stuf= from them I'm happy to look into it more. Also if you do invest I can help=them with (A) if needed. It's a very dumb platitude but "security is=a process" is true. Unrelated: checkout =dge.org <http://edge.org> , I think you'll like it. Th=re's a short video with Minsky that is absolutely fantastic Sent from my (phone =br>On Jan 30, 2016, at 11:26, jeffrey E. <[email protected] <mailto:jeevacation@=mail.com» wrote: (https://mycelium.com/phone/index.html <https://mycelium.com/phone/ind=x.html> ). =nbsp; what are its weak points? &=bsp; please note The information contained in this communication is=br>confidential, may be attorney-client privileged, may constitute insid= information, and is intended only for the use of the addressee. It is t=e property of JEE Unauthorized use, disclosure or copying of this =ommunication or any part thereof is strictly prohibited and may be unlaw=ul. If you have received this communication in error, please notify us i=mediately by return e-mail or by e-mail to [email protected] <mailto:jeevacation=gmail.com> , and destroy this=communication and all copies thereof, including all attachments. copyrig=t -all rights reserved 2 EFTA_R1_01427339 EFTA02395737

Technical Artifacts (7)

View in Artifacts Browser

Email addresses, URLs, phone numbers, and other technical indicators extracted from this document.

Phone2395736
Phone2395737
URLhttp://edge.org
URLhttps://mycelium.com/phone/ind=x.html
URLhttps://mycelium.com/phone/index.html

Forum Discussions

This document was digitized, indexed, and cross-referenced with 1,400+ persons in the Epstein files. 100% free, ad-free, and independent.

Annotations powered by Hypothesis. Select any text on this page to annotate or highlight it.