The Enigma October Development Update is now available.
The audit started as planned on November 4th, 2019, and is currently underway. Getting the Enigma Protocol codebase reviewed and audited by an external firm is an important milestone that Enigma is accomplishing during this month of November. Plus the majority of the development team is now working on the infrastructure that Enigma will need to deploy for testnet and mainnet.
During the month of October, the Enigma Contract repository saw the most substantial additions in the Enigma Protocol. One of the recent additions was the automatic conversion between ENG and ETH when a secret computation includes a callback to Ethereum.
More to follow!
The primary goal for the month of October was to stabilize Enigma’s codebase across all its repos to get ready for an external audit.
The audit started as planned on November 4th, 2019, and is currently underway. Getting the Enigma Protocol codebase reviewed and audited by an external firm is an important milestone that Enigma is accomplishing during this month of November, and the focus now shifts to working closely with the auditors responding to their requests for information and clarification, as well as taking action on their recommendations to make code improvements as needed.
In parallel, the majority of the development team is now working on the infrastructure that Enigma will need to deploy for testnet and mainnet. Enigma is building this infrastructure using Kubernetes.
Enigma has yet another workstream open engaging with a different external firm that is developing a Block Explorer for the Enigma network using Graph Protocol. During the month of October, the Enigma Contract repository saw the most substantial additions in the Enigma Protocol:
- Upgradeability of the Enigma Contract is one of the critical features that Enigma needs to put in place before launching a public network. Enigma is doing its best to have a secure and robust contract that will act as the “source of truth” for its network, Enigma is testing it extensively, and it is now going through an external audit. There is always a risk that something needs to be patched, amended or corrected in the future. This is why the functionality to carry out an upgrade was introduced in Contract PR#157.
- A recent addition was the automatic conversion between ENG and ETH when a secret computation includes a callback to Ethereum. All the computation fees in the Enigma network are denominated in ENG tokens, and one single payment/transaction is all that is needed to submit that task to the network for processing. Thus, in those cases that involve a callback to Ethereum as part of that computation, a transaction paid in ETH gas is required, and automatic conversion between ENG and ETH takes place to that extent: Contract PR#168.
- As a result of the development of the Block Explorer mentioned above, Enigma had to add additional fields to some events that are emitted by the Enigma contract so that that information can be conveniently displayed in the Block Explorer: Contract PR#167
Additionally, new features were introduced or modified that affected multiple repositories:
- Enigma finalized the functionality to revert the state when the result of a computation fails to get committed on-chain. In that case, even when the computation succeeded inside the enclave and the state was updated accordingly, the state needs to be reverted because the Enigma contract is not successfully recording that state change. Given that the Enigma contract is its “source of truth”, the enclaves need to get in sync with it. Implemented in Core PR#224 and P2P PR#231; with subsequent tests introduced in Core PR#240 and Contract PR#166, and subsequently patched in P2P PR#243 and P2P PR#250.
- Through an internal review, Enigma discovered that it was theoretically possible to have a collision in the hashing algorithm that the Key Management node uses when an array is involved. This was identified as a possible security flaw because that hash is used to validate variables that are transmitted over the network, and that validation relies on the lack of collisions. The modified hashing algorithm was implemented in Core PR#217 and Contract PR#161.
- Last but not least, a coordinated release across its three repositories was pushed out, releasing updated Docker images that Enigma’s community of Secret Contract developers relies on for their work: Contract PR#165, Core PR#237, and P2P PR#240, and announced on Enigma’s developer forum.
Enigma is joining the @MPCalliance along with many other respected privacy-focused organizations. All of them are focused on the security and privacy of the personal and professional data.
Tor Bair, Head of Growth and Marketing for Enigma, presents on how to build and inspire communities of any kind, with a focus on the blockchain and cryptocurrency space. Drawing from Enigma’s successes and mistakes, Tor breaks down how to navigate the highs and lows of community-building — and how to know when you’re on the right, sustainable path.
• Launch on a public ethereum test network
• ‘Genesis game’
Partnerships and team members
Social Media Metrics
The charts above show the decline in the number of Twitter and Telegram followers.
Telegram — Telegram HQ for the Enigma Project.
Secret Nodes Community Telegram — a community-led group of individuals who care about privacy, data ownership, and are dedicated to supporting secret node runners.
Twitter — The official announcements channel. The average number of retweets is 40 for one post. Publications with 30–100 likes.
Reddit — Threads with 6–20 comments, 10–30 upvotes.