>> (p.1)
    Author Topic: Catastrophe Scenario on Bitcoin Network  (Read 1200 times)
    cakir (OP)
    Legendary
    *
    Offline Offline

    Activity: 1274
    Merit: 1001


    ★ BitClave ICO: 15/09/17 ★


    View Profile WWW
    June 11, 2015, 10:45:00 PM
    Last edit: June 11, 2015, 11:11:53 PM by cakir
     #1

    All we know Chinese Miners have total 56% mining power[1] publicly. (There's 26% that we don't know who have it).
    What if Chinese government decides to cut their internet connection from outside of the world? (You know such thing can be done, eg: north korea [2]) Or maybe an earthquake can cut their internet from backbone (maybe not all of it but most of it).
    And as result of these scenarios ~50% of miners in China will still mine bitcoins in a local internet like a huge LAN. And rest of the world will mine in another bigger LAN but there'll be no connection between them.  Of course there'll be 2 different major forks.

    After 1 month everything went normal. So there're 2 major forks of bitcoin network. How will we decide? Which one is legit chain? Both of them looks legit.

    Possible solutions:
    - Major mining farms should use secondary internet connection such as satellite connection. Which can be blocked by governments. But it's not affected (or minimally affected) by natural catastrophes.
    That's why I support jgarzik's "bitcoin satellite project" [3]. Even if governments ban satellite connections which is provided by gov controlled ISP's; Personal satellite internet dishes can connect bitcoin satellites. There's a catch here, jgarzik's satellites will provide only blockchain (to distribute accepted blocks) they're not gonna be used for broadcasting block candidates.

    [1] https://blockchain.info/pools (antpool: 20, f2pool: 19, bw.com: 11, btcchina pool:6; total: 56%)
    [2] http://en.wikipedia.org/wiki/Internet_in_North_Korea
    [3] https://bt.irlbtc.com/view/334701.0


                      ,'#██+:                 
                  ,█████████████'             
                +██████████████████           
              ;██████████████████████         
             ███████:         .███████`       
            ██████               ;█████'      
          `█████                   #████#     
          ████+                     `████+    
         ████:                        ████,   
        ████:    .#              █     ████   
       ;███+     ██             ███     ████  
       ████     ███'            ███.    '███, 
      +███     #████           ,████     ████ 
      ████     █████ .+██████: █████+    `███.
     ,███     ███████████████████████     ████
     ████     ███████████████████████'    :███
     ███:    +████████████████████████     ███`
     ███     █████████████████████████`    ███+
    ,███     ██████████████████████████    #███
    '███    '██████████████████████████    ;███
    #███    ███████████████████████████    ,███
    ████    ███████████████████████████.   .███
    ████    ███████████████████████████'   .███
    +███    ███████████████████████████+   :███
    :███    ███████████████████████████'   +███
     ███    ███████████████████████████.   ███#
     ███.   #██████████████████████████    ███,
     ████    █████████████████████████+   `███
     '███    '████████████████████████    ████
      ███;    ███████████████████████     ███;
      ████     #████████████████████     ████ 
       ███#     .██████████████████     `███+ 
       ████`      ;██████████████       ████  
        ████         '███████#.        ████.  
        .████                         █████   
         '████                       █████    
          #████'                    █████     
           +█████`                ██████      
            ,██████:           `███████       
              ████████#;,..:+████████.        
               ,███████████████████+          
                 .███████████████;            
                    `+███████#,               
Page 1
Viewing Page: 1