Tomislav Mamić
    • Create new note
    • Create a note from template
      • Sharing URL 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
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee
    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL 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
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee
  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # Signaling session outline ### A. General information | | | | -------- | -------- | | Session title | Signaling ring | | Facilitator | James Hancock | | Scribe | *Text* | | Time and date | 13:30 - 15:00, 29.10.2018. | | Material requirements | *Text* | | Space requirements | *Text* | | Number of participants | *Text* | ### B. Expected outcomes 1. Action plan of needed tools based on review of the following events. 2. Block Reward Reduction 3. Ropsten Bork 4. Delaying Constantinople ### C. Expected outputs 1. ### D. Timeline | Duration | Segment | Description | | -------- | -------- | -------- | | 20 mins | Product status + Feedback | | | 15 mins | Context in which the magicians may want to know stances? | When, how often and for which cases Discussion of latest issues: mining reward, ropsten and pushback of the hardfork | | 15 mins | Backlog and feature priorities | Are there additional signals we can use? | | 40 mins | Fishbowl discussion | | | 10 mins | Wrap up | | James: We came up with having some kind of website. V1.0 includes coin and gas signalling + stances on twitter. Thanks, Giveth and Aragon for the support. Since the last meeting we had 3 community events: * reducing the miners' fee * ropsten fork * Constantinople push back We need to discuss tools that could help with managing that better. Other agenda items: * Multisigs and DAOs endorsement. How do you Signal / DAOs best practices? * List of the key sources of the information we need. Like hash power or specific influencers like 0x or maker. Criteria definition * How do we create incentives for people to signal? * Translate data from signalling / ethereum community to the investors (family offices), hedge funds, miners and educate them on what is good info and data. There's a lot of info – telegram, magicians, calls – too much for a usual investor. Also convenient distribution channels * Do we care about the standardized format for those signals? (there was a fork choice coordination proposal, e.g. specific block to transit by Dan, Strange loop, Metamask) # Events and signal sources On fee reduction: The idea to reduce the reward was thrown out. There was some debate, but how do people signal for support. Core devs took some miners representatives on the dev call. And some compromise happened regarding the fee and ASICS. The guy with big powers said – if I can't make money I can use my powers elsewhere. No idea who runs carbon vote. The biggest challenge with coinvotes – legitimacy is not very high. Devs won't take in consideration at all. So I'm not putting my funds out of ledger if they won't be checking anyway. If you win – you'll point to that, but not otherwise. How do you legitimize them? Griff: coinvotes are not that valuable without other signals. Miners will, of course, be against. Most impact comes from influencers. If we can grab them from sources and track their decisions in something like a wiki format. There's no common belief on who should influence the decisions. People don't necessarily want miners or devs to decide. The challenge we're gonna face is to have a better-formed ideology on who should decide. Afri: some issues are not contagious, but people can make them such. Maybe we can assign someone, do delegative voting for tactical issues. As long as you have a grouping – it's ok. Pure coninvote can be one-sided (e.g. let have the minimum miner fee). ## Timing of voting/signalling EIP has a maintainer and he makes the last call. So last call timing makes the most sense. Also, it's important – who asks the questions. What kinds and how they're asked? Another thing is EIP can be wrongly represented. ## Types of signals Do we have any other data points besides coins? We have gas and miners voting. You can even allocate power to different types of users (e.g. miners and app devs). Maybe we need to start with identifying the stakeholders and ways to reach them. Spoke word is one, written work, in-person meeting and etc. You can also check for non-verbal communications. One way to signal emotions – is signaled by emojis. There could be a lot of "confused" reaction. Better then yes or no. Signals are non-binding. But somehow it can come expensive to go against the majority decisions. That's how it works now – you can fork but that's impractical. Devs push the client release and they can choose. If they disagree also by selling the coins. The signals important for the core team would be more about the tech questions rather than economic. And investors do vice versa. You can find a lot of legitimacy from the influencers stances (Vitalik, Vlad etc.). In non-profit world, consensus is a qualitative thing, not quantitative. Not ideal to quantify that. You can signal with some percentage of uncertainty. But we can use some metrics and criteria. The uncertainty can be solved with the liquid democracy/delegation. You can end up with no decision (bitcoin situation), but the ability to fork is valuable. It's a very difficult problem, but moving to better things seems like a better solution. If we can make exits frictionless, then deciding would be way easier. With blockchain has an opportunity to choose. And in the end, the dominant strategy is to get there. If the signal is clear we can avoid contagious issues and splits (e.g. 60% are for this). On ropsten fork, would there be a signal that helped you – no. Why isn't it easier to help stakeholders to reach core devs. Even for core developer, it's hard to understand some questions (like the roadmap). So can be for many others. That's where research teams come in and can structure that. There's no concept & constitution to guide that. It's not that we don't have enough data, it's just is not disclosed. There's a couple of datapoints restricted by the tech e.g. full node voting. Nodes stuff is possible – Infura knows IP and software running. It's not sybil resistance, but incentivizes node operators. What if Catalonia becomes independent and decides to use Ethereum for governance and block all other IPs. This is out there in Bitcoin (ethereum as well at ethernodes.com). You can put a flag in the client. Coin.dance could show how many nodes use the right software. On ethereum, 27k nodes are available with OS, version, IP etc. Something like this should be available and open sourced. # Prediction markets Markets are the best way to aggregate the information. You can leverage the prediction market in the situation of high asymmetry. With 2-dimensional prediction market, if you can combine those results it's more informative. The best signals are giving you the info you don't know. In prediction markets, stances are known. It's more suitable for avoiding things like hard forks. In EIP0 we had an extensive list of influencers. Weighting the signals can feel wrong. The best course is to provide the data without the interpretation. Influencers list is the most controversial topic. But it's the potential way for delegative representation (e.g. delegate all my votes for Vitalik). The action item can be to raise that issue (tasks) further in magicians. Like Quora, HiveOne. Discussing it here is better than on Reddit. It's a delicate balance. Last time discussing 999 we've found several people using multiple accounts to signal. Action item: * List of stakeholders * 2 new EIPs (standardized format of signals, miners ) * Ethernode for tennagrahp * Join Quora and Riot/Telegram chat, or Tweet to James and Griff

    Import from clipboard

    Paste your markdown or webpage here...

    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 lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    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 Sign in with Wallet
    Wallet ( )
    Connect another wallet

    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

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    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
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    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.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        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
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

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

        Syncing

        Push failed

        Push successfully