HackMD
    • Create new note
    • Create a note from template
    • Sharing Link copied
    • /edit
    • View mode
      • Edit mode
      • View mode
      • Book mode
      • Slide mode
      Edit mode View mode Book mode Slide mode
    • Customize slides
    • Note Permission
    • Read
      • Only me
      • Signed-in users
      • Everyone
      Only me Signed-in users Everyone
    • Write
      • Only me
      • Signed-in users
      • Everyone
      Only me Signed-in users Everyone
    • Commenting & Invitee
    • Publishing
      Please check the box to agree to the Community Guidelines.
      Everyone on the web can find and read all notes of this public team.
      After the note is published, everyone on the web can find and read this note.
      See all published notes on profile page.
    • Commenting Enable
      Disabled Forbidden Owners Signed-in users Everyone
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Invitee
    • No invitee
    • Options
    • Versions and GitHub Sync
    • Transfer ownership
    • Delete this note
    • Note settings
    • Template
    • Save as template
    • Insert from template
    • Export
    • Dropbox
    • Google Drive Export to Google Drive
    • Gist
    • Import
    • Dropbox
    • Google Drive Import from Google Drive
    • Gist
    • Clipboard
    • Download
    • Markdown
    • HTML
    • Raw HTML
Menu Note settings Sharing Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync Transfer ownership Delete this note
Export
Dropbox Google Drive Export to Google Drive Gist
Import
Dropbox Google Drive Import from Google Drive Gist Clipboard
Download
Markdown HTML Raw HTML
Back
Sharing
Sharing Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Comment & Invitee
Publishing
Please check the box to agree to the Community Guidelines.
Everyone on the web can find and read all notes of this public team.
After the note is published, everyone on the web can find and read this note.
See all published notes on profile page.
More (Comment, Invitee)
Commenting Enable
Disabled Forbidden Owners Signed-in users Everyone
Permission
Owners
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Invitee
No invitee
   owned this note    owned this note      
Published Linked with GitHub
Like BookmarkBookmarked
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
# Ethereum 222.0 Workshop Notes _All workshop attendees are encouraged to contribute their own notes to this document. This is a shared space for us to help further the spec. This document format is admittedly abysmal, so feel free to restructure. It's the best option at the moment for real time notetaking._ ## Ameen Soleimani (CEO SpankChain)'s Talk Notes (State of Eth2 Implementation) - There is more that goes in to building a client than just implementing the spec. Architecture, design, optimization, and other low-level implementation decisions must be made, so the spec does not truly represent the body of work necessary to have clients taking to each other on an Eth2 test net. - Before we move towards a testnet, we need consistent cross client tests. - Spec updates should follow a versioning paradigm, so there is a consistent reference for implementers to know what is expected of clients at a given time. - While the spec has always been open and available, EF did not explicitly consult potential Eth2 implementers when formulating the mainnet rollout plan. EF Researchers followed best practices and in general believed the Eth2's phased approach to mainnet rollout captured the opinions of development teams. - Implementation may have started too early, and the full complexity of the spec, even the Phase 0 Beacon Chain spec, was not fully understood. - What are the pros and cons of having a lead or other "centralized" coordination role, if it is being done with the consent of the implementers? - Cons: There is a non-zero possibility of a central planner overstepping their authority and taking the spec in an unpopular direction. - Pros: If everyone works on their own pet projects or favorite portion of the spec, it's difficult to form a cohesive development community. - Some central planning was necessary in order to kick off the research process. As more people became familiar with and contribute in the direction, it is easier to open up to more decentralized planning. - Why did client developers start so soon? Did they feel as though they had to implement Eth2 immediately? Perhaps there were some miscues and signaling problems to begin with. - There is now an apetite in the community for people to contribute and help Eth2 more faster and better. - The sheer number of teams working on Eth2 at the moment introduces significant coordination overhead. - Eth2 is underestimating competitive threats. There are many other blockchains teams whose success depends on convincing the next generation to build their ideas on a platform not Ethereum. - Eth2 roadmap is technically ambituous but still moving too slowly. - It shouldn't be expected/necessary that all teams launch at the same time. ## Mikerah (ChainSafe)'s Talk Notes (Why should we care about validator privacy?) - GitHub Stuff - [ethresearch/p2p](https://github.com/ethresearch/p2p/issues) - [ethresearch/sharding-p2p-poc](https://github.com/ethresearch/sharding-p2p-poc) Proof of Concept of Ethereum Serenity Peer-to-Peer Layer on libp2p PubSub System - [libp2p/specs](https://github.com/libp2p/specs) Technical specifications for the libp2p networking stack - Is there a rational for using Kademlia? Answer: It's already implemented in libp2p. - In structured networks long lived identities are necessary feature for implementation. Can we consider unstructured networks? - Ideal is to not tie node identity to validator identity in the protocol. Not tightly coupling this allows the validator more freedom in implementation. - Wire protocol needs to be well specified so the clients actually know how to communicate. - Gossip can be inefficient because the same transaction data is sent even to clients that have already received it. - What are the drawbacks to using the protocols that are already around today? i.e. devp2p Answer: It's poorly specified. - After significant research and benchmarking and the libp2p team offering closeness with the EF, libp2p was chosen. - What are alternatives to Kademlia? Answer: Bitcoin uses a unstructured network which is mostly hueristic based. - Minimal propagation time of new messages should be preferred in blockchain networks over bounded lookup times. - Is using an unstructured network even possible if your goal is to index nodes? - Validators are reassigned at each epoch, so a structured network will have to recalcuated at a per-epoch basis, correct? There is per-epoch shuffling, but also the notion of persistent committees in Eth2. - Will contracts on different shards be able to speak to eachother? Answer: Research is underway on a async crossshard communication protocol built in to base layer as well as a number of synchronous layer 2 protocols being investigated. - Papers that were mentioned - [Low-resource eclipse attacks in Ethereum](https://eprint.iacr.org/2018/236.pdf) - [Graphene](https://people.cs.umass.edu/~gbiss/graphene.pdf) ## Vanessa Bridge (PegaSys R&D | ConsenSys)'s Talk Notes - [Wittgenstein Repo on GitHub](https://github.com/ConsenSys/wittgenstein) - A simulation framework for testing some PoS and consensus algorithms. It is still in development, but hopefully others find this useful for tuning Eth2 network parameters and making sensible design decisions. - Used to simulate Casper IMD. - As of current protocols must be written in Java to make use of Wittgenstein simulation. - There are no plans for JNI bindings to faciliate testing protocols build in other languages which expose shared objects as of yet, but the implementation team is open to the idea given demand. ## TestNet & Wire Protocol Discussion Notes Session Takeaways What does it take to achieve interop? 1) We need to define these interop tasks: - Discovery (see py-libp2p team's summary below) - Felix from the EF is working on the Discovery Protocol - Connection Handshaking - Encryption? - Authenitication? - Compression? - Peer reputation? - Application Protocol - How will we propogate blocks and attestations? 2) Now that there is an initial spec release, the major priority is creating: - test vector formats - test vector generators well designed tests will help us achieve interop sooner. Danny's TODO: - to take a stab at designing the wire protocol in the next couple of days. - is going to add some notes to the spec on Network Topology ## py-libp2p Peer Discovery Discussion Notes **[Slide Deck](https://github.com/alexh/peer-discovery-pres/blob/master/peer_discovery_pres.pdf)** Session takeaways - Discovery protocol should return ENRs ([Ethereum Node Records](https://eips.ethereum.org/EIPS/eip-778)) or other forms of node metadata, instead of just networking information. - Easier to discover node capabilities, e.g. shards associated with a node - Endpoint verification needs more thought - Making the "bonding" process described in presentation more resilient to network faults - Non-Kademlia options should be explored. Additional info: - https://github.com/ethereum/devp2p/blob/master/discv4.md - https://github.com/ethereum/devp2p/wiki/Discovery-Overview

Import from clipboard

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lost their connection.

Create a note from template

Create a note from template

Oops...
This template is not available.


Upgrade

All
  • All
  • Team
No template found.

Create custom template


Upgrade

Delete template

Do you really want to delete this template?

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Forgot password

or

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Tutorials

Book Mode Tutorial

Slide Mode Tutorial

YAML Metadata

Contacts

Facebook

Twitter

Discord

Feedback

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions and GitHub Sync

Sign in to link this note to GitHub Learn more
This note is not linked with GitHub Learn more
 
Add badge Pull Push GitHub Link Settings
Upgrade now

Version named by    

More Less
  • Edit
  • Delete

Note content is identical to the latest version.
Compare with
    Choose a version
    No search result
    Version not found

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub

      Please sign in to GitHub and install the HackMD app on your GitHub repo. Learn more

       Sign in to GitHub

      HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Available push count

      Upgrade

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Upgrade

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully