Skip to content
  • Home Home Home, current page.
  • Moments Moments Moments, current page.

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
hugohanoi's profile
Hugo Nguyen
Hugo Nguyen
Hugo Nguyen
@hugohanoi

Tweets

Hugo Nguyen

@hugohanoi

I chain, therefore I am ⛓️

Joined April 2012

Tweets

  • © 2018 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Shinobi, CEO of Bitcoin‏ @brian_trollz 26 Dec 2017
      Replying to @brian_trollz @LukeDashjr and

      (i.e. both can cause splits, but for different reasons)

      1 reply 0 retweets 1 like
    2. Luke Dashjr‏ @LukeDashjr 26 Dec 2017
      Replying to @brian_trollz @ktorn and

      Softforks can't cause splits.

      3 replies 1 retweet 3 likes
    3. Jorge Timón‏ @timoncc 26 Dec 2017
      Replying to @LukeDashjr @brian_trollz and

      Of course they can. If miners create segwit invalid blocks now, most nodes will reject them but pre-segwit nodes will accept them. I know you're going to say that's miners doing a hf but what if it's a miner that never upgraded?

      1 reply 0 retweets 3 likes
    4. Luke Dashjr‏ @LukeDashjr 26 Dec 2017
      Replying to @timoncc @brian_trollz and

      It's still a HF attempt.

      1 reply 0 retweets 2 likes
    5. Jorge Timón‏ @timoncc 27 Dec 2017
      Replying to @LukeDashjr @brian_trollz and

      Whatever. Bip148 could have caused a split. Softforks can cause split.

      2 replies 1 retweet 3 likes
    6. Luke Dashjr‏ @LukeDashjr 27 Dec 2017
      Replying to @timoncc @brian_trollz and

      No, BIP148 could not have caused a split. Any split would have come from malicious miners intentionally doing itt, and they can do it with or without any softfork.

      1 reply 0 retweets 8 likes
    7. Jorge Timón‏ @timoncc 28 Dec 2017
      Replying to @LukeDashjr @brian_trollz and

      "Malicipus miners" or not, a split is a split. People like me would have followed the non-bip148 chain voluntarily.

      1 reply 0 retweets 0 likes
    8. Luke Dashjr‏ @LukeDashjr 28 Dec 2017
      Replying to @timoncc @brian_trollz and

      But the split wouldn't have been caused by BIP148.

      4 replies 0 retweets 1 like
    9. Jorge Timón‏ @timoncc 28 Dec 2017
      Replying to @LukeDashjr @brian_trollz and

      How not? Your node would have followed the bip148 chain while mine would have followed the original chain. All voluntary on our part.

      1 reply 0 retweets 0 likes
    10. Luke Dashjr‏ @LukeDashjr 28 Dec 2017
      Replying to @timoncc @brian_trollz and

      Just because you decide to follow an invalid chain doesn't make it any less invalid. It's no different than if you decided to run 2X.

      1 reply 0 retweets 0 likes
      Hugo Nguyen‏ @hugohanoi 28 Dec 2017
      Replying to @LukeDashjr @timoncc and

      You have a very loose definition of “invalid.” Inaction is NOT invalid. Many users/nodes around the world would have faced wipeout risk, just because they were unaware of the UASF chain.

      12:04 PM - 28 Dec 2017
      • 1 Like
      • Jorge Timón
      1 reply 0 retweets 1 like
        1. New conversation
        2. Luke Dashjr‏ @LukeDashjr 28 Dec 2017
          Replying to @hugohanoi @timoncc and

          Inaction is indeed often invalid. Otherwise Bitcoin has no rules at all, since light wallets are in a perpetual state of accepting invalid blocks. Otherwise softforks never succeed, since very rarely do 100% of nodes upgrade before activation.

          1 reply 0 retweets 0 likes
        3. Hugo Nguyen‏ @hugohanoi 28 Dec 2017
          Replying to @LukeDashjr @timoncc and

          Disagreed. The entire point of soft forks is to have a safe way to upgrade by being *backward compatible*. Backward compatibility implies inaction is a valid state. If you don’t care about backward compatibility, why bother with soft forks?

          1 reply 0 retweets 1 like
        4. Luke Dashjr‏ @LukeDashjr 28 Dec 2017
          Replying to @hugohanoi @timoncc and

          Softforks are backward compatible so long as miners are not performing attacks. It's a good attribute to have, but not relevant to the question at hand, where the miners are in fact attacking. During such circumstances, ex-full nodes are simply insecure.

          1 reply 0 retweets 0 likes
        5. Jorge Timón‏ @timoncc 28 Dec 2017
          Replying to @LukeDashjr @hugohanoi and

          The majority of users were not enforcing bip148. Had some miners dare to defy bip148's proposal, there would have been 2 used chains. You can't dictate that I'm an "ex-full node" for not enforcing bip148 against my will.

          2 replies 0 retweets 0 likes
        6. Luke Dashjr‏ @LukeDashjr 28 Dec 2017
          Replying to @timoncc @hugohanoi and

          That's where you're wrong. A majority of the users supported BIP148, and even if it turned out not all of them were enforcing, a split would have pushed the supporters who didn't enforce to begin doing so.

          1 reply 0 retweets 3 likes
        7. Hugo Nguyen‏ @hugohanoi 28 Dec 2017
          Replying to @LukeDashjr @timoncc and

          There are 3 types of users: 1) users who actively supported BIP148 2) users who were aware but not supportive-including many pro-Segwit users. some prefered BIP149. 3) users who were completely unaware BIP148 were coercive & hurt groups 2 & 3. There's nothing "soft" about it.

          2 replies 0 retweets 0 likes
        8. Hugo Nguyen‏ @hugohanoi 28 Dec 2017
          Replying to @hugohanoi @LukeDashjr and

          You keep saying "a majority of users supported BIP148", but the truth is that there was no reliable way to measure this, beyond the r/bitcoin tiny community and unreliable Twitter polls- which have biased samples given the inherent nature of Twitter.

          3 replies 0 retweets 1 like
        9. Luke Dashjr‏ @LukeDashjr 28 Dec 2017
          Replying to @hugohanoi @timoncc and

          Also, of the users polled, not only did a majority support BIP148, but those who did not also either opposed Segwit in general, or said they would support BIP148 if Core released it in an official release. So BIP148 effectively had almost same community support as Segwit itself.

          1 reply 0 retweets 2 likes
        10. 8 more replies

      Loading seems to be taking a while.

      Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

        Promoted Tweet

        false

        • © 2018 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Cookies
        • Ads info