[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/biz/ - Business & Finance


View post   

File: 517 KB, 700x700, 71xky009gte01.png [View same] [iqdb] [saucenao] [google]
7453357 No.7453357 [Reply] [Original]

Alex 'Sandy' Pentland shilled ENG today at MIT

Do with this what you will...

https://en.wikipedia.org/wiki/Alex_Pentland

https://blogs.wsj.com/cio/2015/12/30/lawrence-lessig-how-technology-policy-will-evolve/

>> No.7453397
File: 292 KB, 2400x1589, 1515330174153.jpg [View same] [iqdb] [saucenao] [google]
7453397

Hopefully we get a video out of this!

https://twitter.com/EnigmaMPC/status/961265781781778432

>> No.7453655

Bumping this for ungrateful biz

>> No.7453703
File: 44 KB, 600x600, IMG_4779.jpg [View same] [iqdb] [saucenao] [google]
7453703

one of the most undervalued coins right now, how are people still sleeping on this

>> No.7453952
File: 64 KB, 500x500, EnigmaMPC.jpg [View same] [iqdb] [saucenao] [google]
7453952

>>7453655
>>7453703
I really think people just don't grasp what it is...

https://www.youtube.com/watch?v=qeJn8YgDIlw

>> No.7454124

dude, they got hacked and raised their hardcap during ico. Naturally it tanked like the titanic.

>> No.7454152

>>7453703
Do you mean the project itself or the 'coin' with no value?

>> No.7454241

This was the coin that made me decide to get into crypto some are saying it could be 95$ per coin in 5 years

>> No.7454300

>>7454241
94.5 actually but pretty close indeed

>> No.7454356

>>7454124
ICO fud really, dealt with an eternity ago!

>>7454152
https://www.youtube.com/watch?v=bhE0T2tLaHE

>>7454241
5 yrs is a long time, if the market grows that will be a low ball!
Pure speculation though...

>> No.7454416

>>7453357
What I don't understand is this: why the fuck would any blockchain use ENG as a second layer? What's the incentive to make this happen?

>> No.7454478

"This makes is possible"

Doesn't even check.

>> No.7454715
File: 2.97 MB, 1920x1080, 1509037183433.png [View same] [iqdb] [saucenao] [google]
7454715

its almost as if he was holding bags
hmmmm

>> No.7454717

>>7454416
Scalability and Privacy.

https://www.reddit.com/r/enigmacatalyst/comments/7rb7ix/enigma_privacy_for_every_blockchain_get_started/

>>7454478
Maybe its a direct quote haha

>> No.7454774

"The requirement of trust on the participants is also an onerous one; note that, as is the case with many other applications, the participants have the ability to save the data and then collude to uncover at any future point in history. Additionally, it is impossible to tell that they have done this, and so it is impossible to incentivize the participants to maintain the system’s privacy; for this reason, secure multi-party computation is arguably much more suited to private blockchains, where incentives can come from outside the protocol, than public chains."

any counter to this fud?

>> No.7454896

>>7454774
answer me you zealous brainlets

>> No.7454983

>>7454717

The scalability part I'm not too sold on, yes it'll be nice to have tx/s done off chain, but you'll have software and hardware solutions like EOS or HPB that will do the job just as well, if not better for different blockchains that require 100's of thousands or millions of tx/s.

Bought a stack of ENG because they can split computation and transaction of data through multiple nodes, with each node processing only parts of the initial data, without having the data being compromised to any of the nodes that make the computation.

Incentive comes at adopting the protocol when the blockchain needs to deal with sensitive data, say medical records; with relative ease.

>> No.7455032

RLC/ENG/LINK marine reporting in.
After the flippening, all eth transactions will be ran through these protocols.

>> No.7455049

>>7454774
Not enigma fud at all.

From Vitalik Buterins Jan 2016 article.
https://blog.ethereum.org/2016/01/15/privacy-on-the-blockchain/

“Secret contracts are like smart contracts, in that they allow executing contracts (i.e., code) with high degree of integrity, which in simple words mean that no one can manipulate the results. However, unlike smart contracts, the underlying input data/state being processed is not visible to anyone, including the nodes in the Enigma network that actually carry out the computation.

Think of a smart contract that lives on the blockchain and tries to find correlations between specific genes and certain diseases. On any blockchain today, this equates to people sharing their genomic data openly for everyone to see. With secret contracts, their data would remain private, because it’s always encrypted.

The way these work under the hood is by one of several means - secure hardware, secure multiparty computation (MPC), or fully homomorphic Encryption (FHE). Enigma employs the first two to enable this with scale (FHE, while theoretically possible, is not likely going to be practical anytime soon).

Note that ZKP/zkSnarks (which are an amazing scientific achievement) are a complementary, but not a sufficient, solution to the problem of privacy. ZKP, in general, allow proving the correctness of a computation to others without revealing the underlying data - but the prover still needs full access to the data. This means that with ZKP someone has to see the data - so you can’t, for example accomplish the example above. There was also an exploration of such a system before called Hawk, which had to rely on a trusted manager with the privacy of the data for this exact reason.”

Source:
https://medium.com/@EnigmaMPC/computing-over-encrypted-data-d36621458447

>> No.7455066

>>7454896

Agreed that it is one of the flaws of having a decentralized masternode system where the system's privacy could be compromised through collusion, within the protocol. Say a whale accumulates a vast amount of ENG, and runs enough masternodes that risks the data breach.

But the founder did a recent AMA where he confirmed the amount of ENG required to run a masternode would be a dynamic system, where it can be changed. So theoretically to combat said whale with malicious intents, the team could lower the number of tokens required to be a MN, and further decentralize the system's privacy security by vastly increasing the numbers of participants that could run MN's.

>> No.7455090
File: 94 KB, 2031x492, F17B3964-0C89-4D42-9D79-6ADCBDC31D9B.jpg [View same] [iqdb] [saucenao] [google]
7455090

Nuff said

>> No.7455154

>>7455049
Or I guess the data is encrypted for every node the processes parts of the original data. But is this confirmed unhackable? There's some FUD regarding quantum computing and encryption right?

>> No.7455283

>>7455066
they would need to control a majority of the network. there would be no reason for all miners not to collude, because there would be no way to prove that they didn't. that's the problem.

however, it's possible that miners would refrain from collusion because ultimately it would cause the enigma network to fail in the long-run. but generally counting on long-sightedness in crypto incentives is a bad idea. my concern is that relying on this sort of game theory would be too risky for dapps that need to use very sensitive personal data.

>>7455049
doesn't address the problem in my post. this is just saying smpc works without considering collusion.

>> No.7455303

>>7455283
wouldn't*

>> No.7455327

>>7455283
Encryption of data to single nodes should be able to prevent this, rereading whitepaper now for this part, you got me curious myself.

>> No.7455330

>>7455066
>>7455154
Yeah that would require a lot of 'Bad' masternodes, discussed in the AMA as you mentioned.

Also Sandy pentland discussing here. (22m mark)
https://www.youtube.com/watch?v=1TGfZ55dOb4&t=22m20s

>> No.7455518

>>7455283
>doesn't address the problem in my post. this is just saying smpc works without considering collusion.
the underlying input data/state being processed is not visible to anyone, including the nodes in the Enigma network that actually carry out the computation.

Incredibly unlikely over 51% of the nodes will be bad actors.
https://www.youtube.com/watch?v=bhE0T2tLaHE&t=01m10s

>> No.7455747
File: 238 KB, 893x488, eng.jpg [View same] [iqdb] [saucenao] [google]
7455747

>>7455283
>>7455283
>>7455330

Page 4 of whitepaper dictates a minimal amount of parties required to decrypt the data. So the dynamic number of ENG required to be a MN could temporarily weed out the malicious attempts for a collusion attempts. Pic related.

Page 12 discusses security deposits with a penalty system of losing ENG/BTC to host masternodes to reduce attack attempts on MPC protocols.

>> No.7455900
File: 8 KB, 300x168, hmmmm.jpg [View same] [iqdb] [saucenao] [google]
7455900

>>7455747

Also on top of increasing MN's, they could also increase the t variable, thus by increasing the minimum required parties are required to decrypt the data, it should in theory, prevent collusion attempts.

But this question raises another question, how will they modify the t variable? Is it going to be voted in by the MN's as is with the dynamic system of requiring x amount of ENG to be a MN?

If a 51% attack already did occur, then the democratic approach will fail here. Hmmm.

>> No.7455991

>>7455747
i see. makes some sense. i think vitalik's concern was that nodes could save their portion of the data, so it would be impossible to determine that an attack had occurred.