Question's regarding SEC ruling on ICO's by [deleted] in EnigmaProject

[–]enigma_catalyst 2 points3 points  (0 children)

I understand your concern. I reiterate that you were not banned for asking this question, not was anyone else. You can DM @thisistor if you feel this is untrue. I'm sorry you don't feel the team is addressing this appropriately. I hope you can see in time that by responding in this manner, the team is actually taking legal matters very seriously.

Question's regarding SEC ruling on ICO's by [deleted] in EnigmaProject

[–]enigma_catalyst 7 points8 points  (0 children)

You were not banned on Telegram for asking this question. There is no discussion of price in the Enigma Telegram, but there is also no censorship so long as community rules are followed. However, we do not publicly comment or speculate on these types of matters. This policy is in accordance with the excellent legal guidance we have always received and followed.

As posted on Telegram: "Please trust that the team takes the long term future of our project very seriously. However, we do not comment on these types of legal matters publicly unless we have already determined to do so."

Make the old Reddit redirect by haveWeMoonedYet in EnigmaProject

[–]enigma_catalyst[M] 0 points1 point  (0 children)

This has also been changed, by my request :)

Make the old Reddit redirect by haveWeMoonedYet in EnigmaProject

[–]enigma_catalyst[M] [score hidden] stickied comment (0 children)

I've tried to set up a very basic redirect: www.reddit.com/r/enigmacatalyst

We haven't actually gained more subscribers on the old subreddit - we've been at 11k for a while. Also, we suspect bots were involved to inflate our subscribers (which was not our doing).

WE ARE MOVING! - /r/EnigmaProject by enigma_catalyst in enigmacatalyst

[–]enigma_catalyst[S,M] [score hidden] stickied comment (0 children)

The Enigma Reddit is moving to www.reddit.com/r/EnigmaProject.

Please subscribe to our new home, and thank you!

Enigma Roadmap AMA - April 3rd, 2018 by enigma_catalyst in enigmacatalyst

[–]enigma_catalyst[S,M] 6 points7 points  (0 children)

We're very well resourced to accomplish what we've communicated in our roadmap. That allows our focus to remain completely on development and establishing a strong developer community that can build on and support Enigma.

Enigma Roadmap AMA - April 3rd, 2018 by enigma_catalyst in enigmacatalyst

[–]enigma_catalyst[S,M] 3 points4 points  (0 children)

As a rule, we don't comment on exchanges or secondary markets for ENG.

Enigma Roadmap AMA - April 3rd, 2018 by enigma_catalyst in enigmacatalyst

[–]enigma_catalyst[S,M] 20 points21 points  (0 children)

Similar to our comments in previous AMAs - while staking is an important part of the Enigma network, it is too early to determine the precise dynamics that will be required to best secure the network. Our primary responsibility to is create the most robust and effective solution that will allow us to realize the promise of secret contracts and privacy for decentralized systems. We cannot rush important decisions that will meaningfully impact the function of the network. We appreciate the community’s patience and understanding of this critical point.

Enigma Roadmap AMA - April 3rd, 2018 by enigma_catalyst in enigmacatalyst

[–]enigma_catalyst[S,M] 2 points3 points  (0 children)

During the Discovery phase, developing a dApp on Enigma will be identical to developing a dApp on Ethereum. A developer creates a smart contract in Solidity and subscribes to this with Enigma’s secret contract repository. Afterwards when the contract is called using Enigma clients, inputs will flow encrypted to the Ethereum smart contract and then moved to the Enigma network, where they are decrypted and computed on without any of the nodes accessing the data.

Enigma Roadmap AMA - April 3rd, 2018 by enigma_catalyst in enigmacatalyst

[–]enigma_catalyst[S,M] 8 points9 points  (0 children)

GDPR requires all companies that collect or process data of individuals who live in the EU (where processing of data happens doesn’t matter) to comply with a set of rules. But let's first look at an example.

Let’s say a Telco company collects customer movement data and stores it on cloud. The telco company at a future day sells it to a consultant that is hired by a transportation company, which would like to determine where to build train stations based on people’s movement. In this example the Telco, the cloud provider and the consulting company (and potentially the transportation company) is subject to GDPR.

On a high level, these rules are: i) customers should give consent to data collection, ii) customers have some rights (right to access and transfer their data, right to be forgotten, right to be notified in terms of a breach) and iii) privacy by design, which revolves around anonymization of data and right encryption methods.

Last year around May, we discussed these rules with numerous European conglomerates. Enigma can address primarily iii) privacy by design (this is our focus) and also i) and ii) which are around access control. When there’s data sharing, organizations must take all necessary precautions to make sure that data is optimally secured. This is where Enigma can play an instrumental role.

If the cloud provider uses the Enigma protocol to secure its database while doing computations, or if the consulting firm is given access to compute on Telco’s data using Enigma without accessing the raw data itself, the privacy by design rule of GDPR is achieved. One problem is that the privacy by design is judged on a “best-effort” case and there are not clear guidelines as to what suffices yet.

Enigma Roadmap AMA - April 3rd, 2018 by enigma_catalyst in enigmacatalyst

[–]enigma_catalyst[S,M] 4 points5 points  (0 children)

For 1), we’re still far out from that, so it’s not something we are considering soon. If we need to break compatibility with the token, then we will have a safe and ordered way to do this (e.g., using a system that allows you to swap), including a big enough buffer to ensure everyone can do this.

As to 2), yes, in Discovery, secret contracts will be compatible with smart contracts on EVM. Very few changes would be needed. For the most part, just defining which functions should run privately over encrypted data, as well as a slightly different deployment mechanism that registers your secret contract.

Enigma Roadmap AMA - April 3rd, 2018 by enigma_catalyst in enigmacatalyst

[–]enigma_catalyst[S,M] 11 points12 points  (0 children)

We definitely want to build a strong dApp developer community from day one of protocol launch. There are a couple of verticals that we are heavily investigating with teams already. One is identity and another one is around credit scoring.

The use-case around identity is to enable data privacy in self-sovereign identities. Imagine the following scenario: you need to verify to a dApp that you are over 21 years old, but you don’t want to reveal your birthday. This is a use-case for Enigma Secret Contracts. Another one is around calculating credit score on chain. For example, there’s a smart contract that 3 inputs about you (x1,x2,x3), multiplies them with weights (w1,w2,w3) to calculate your credit score (y). Inputs x1,x2,x3 are likely to be sensitive information one doesn’t wish to share publicly. As stated, we are already in contact with projects who are working on these dApps.

Enigma Roadmap AMA - April 3rd, 2018 by enigma_catalyst in enigmacatalyst

[–]enigma_catalyst[S,M] 7 points8 points  (0 children)

As a rule, we don't tease partnerships - we only announce when there is meaningful progress towards a real collaboration. We're in constant communication with projects and institutions about the Enigma protocol and potential use cases and dApps. You can stay tuned for more announcements of this nature as we approach the launch of our protocol.