status-im
/
eth2.0-pm
mirror of https://github.com/status-im/eth2.0-pm.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #65 from b-m-f/patch-1 

Update call_020.md
This commit is contained in:
Danny Ryan 2019-08-29 11:11:58 -06:00 committed by GitHub
parent d209ce3df8 48b891f93b
commit 6e41fcf383
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
eth2.0-implementers-calls/call_020.md
View File

@ -321,7 +321,7 @@ The throughput of what the execution environments have to do.
* We are looking at how to use rollups for Ethereum 2.0 on a way to execute transactions on any shard from any rollup.
* We are going to look at a simple case first which is transfer between rollups and we have one proposal ready and we are going to discuss that with Barry Whitehat next week to see where we can merge efforts.
#Protocol Labs
## Protocol Labs
[Timestamp 46:12](https://youtu.be/Y8rhSbtY-Pg?t=2772)
**Danny**: We have a couple guys here from Protocol Labs.
@ -333,7 +333,7 @@ The throughput of what the execution environments have to do.
* Last call we had a question “What security is being provided by TLS vs what the application layer will need to provide?”
* Assuming that is a correct question:
**Raúl Kripalani**: Transport Level Security is necessary to, first of all, not be subject to miner middle tax.
**Raúl Kripalani**: Transport Level Security is necessary to, first of all, not be subject to [Man in the middle attacks](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
* That could potentially alter the payload that is being transported.
* To be able to authenticate the peer that you are interfacing with.
* If you have for example a public key for that peer then when you authenticating them when you are establishing the connection you are handshaking and are able to certify that you are really speaking with them.