Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <jgarzik@bitpay.com>) id 1WmpYD-0005CA-N6 for bitcoin-development@lists.sourceforge.net; Tue, 20 May 2014 19:18:13 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.212.177 as permitted sender) client-ip=209.85.212.177; envelope-from=jgarzik@bitpay.com; helo=mail-wi0-f177.google.com; Received: from mail-wi0-f177.google.com ([209.85.212.177]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WmpYC-0002Vm-GD for bitcoin-development@lists.sourceforge.net; Tue, 20 May 2014 19:18:13 +0000 Received: by mail-wi0-f177.google.com with SMTP id f8so1524994wiw.10 for <bitcoin-development@lists.sourceforge.net>; Tue, 20 May 2014 12:18:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=CbjHAjLmhkqDAi5xeznuZTeYTXQOOXzYw/mH/bUrGfQ=; b=AWrG9Ubp/X3xlrU8uo83uyRk+VQUV+Rnzx+SUCKuCsQ2mC3LEVAmeLGCYUO0EPOQw5 JIFXbCp+7APKiWdr1dYgr5jK9PaWqpagVXobAG/RQDiVOC3mm+nr6jfFHqhA/DSc/Vyx s5Y2Pvfe5cBPB+hhQCxaGRmy4PyZC/1B8WE3e3GJB1IEMl4nDoEELNckO3Q4D80uRb1A a/7U90DbbwgWRxOqoZ8f7qvJkCqNnBvJgUdsa45dw+d5l/c5zfJlh8/4yqeF1I2aPL51 H35dFU0+84UD4bsoQcH9xg75Wqcgz6bps1DoQdU/a+GhLdWxGQWa4/cB2kdrAxxEhZfl 7TfA== X-Gm-Message-State: ALoCoQn+kHE8nAAAsf4J6JIYPsTKO5w5ETpNndQVktXjnV9ma/lp+biczVirG+mqAL1CfHcGtT2P X-Received: by 10.194.246.234 with SMTP id xz10mr4243698wjc.77.1400613486125; Tue, 20 May 2014 12:18:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.240.166 with HTTP; Tue, 20 May 2014 12:17:46 -0700 (PDT) In-Reply-To: <CALKy-wodNVZK+3q79YUJLmTRjihP85va4Mcp=mnUQTuUfLh+zg@mail.gmail.com> References: <CANEZrP2rgiQHpekEpFviJ22QsiV+s-F2pqosaZOA5WrRtJx5pg@mail.gmail.com> <CANAnSg0ABVyRcSaO2aEcqO8qaj+JdxRN4z-hLE-EbESv2TMf2g@mail.gmail.com> <trinity-1957ed0e-a607-47d7-803b-71c59af8eb89-1400573744536@3capp-mailcom-bs08> <20140520143710.GT26986@leitl.org> <4078A034-6626-495D-B42F-BDA94ACE1DA3@gmail.com> <CALKy-wodNVZK+3q79YUJLmTRjihP85va4Mcp=mnUQTuUfLh+zg@mail.gmail.com> From: Jeff Garzik <jgarzik@bitpay.com> Date: Tue, 20 May 2014 15:17:46 -0400 Message-ID: <CAJHLa0PjUqJd_Hfjiwfj5c1yb6LJZeZMS0LFHd3Ncb+Ly88F8w@mail.gmail.com> To: Andy Alness <andy@coinbase.com> Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WmpYC-0002Vm-GD Cc: "bitcoin-development@lists.sourceforge.net" <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] Why are we bleeding nodes? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Tue, 20 May 2014 19:18:13 -0000 Yes, i spec'd out the UDP traversal of the P2P protocol. It seems reasonable especially for "inv" messages. On Tue, May 20, 2014 at 2:46 PM, Andy Alness <andy@coinbase.com> wrote: > Has there ever been serious discussion on extending the protocol to > support UDP transport? That would allow for NAT traversal and for many > more people to run effective nodes. I'm also curious if it could be > made improve block propagation time. > > On Tue, May 20, 2014 at 7:52 AM, Gmail <will.yager@gmail.com> wrote: >> Unlikely. I doubt any significant portion of miners in china will continue to mine on a china-specific chain, since it will certainly be outmined by non-Chinese miners, and will be orphaned eventually. >> >> More likely is that mining interests in china will make special arrangements to circumvent the GFwOC. >> >> Users who can't access the worldwide blockchain will notice horrendously slow confirmation times and other side effects. >> >>> On May 20, 2014, at 10:37, Eugen Leitl <eugen@leitl.org> >>> >>> Could a blockchain fork due to network split happen? >>> >> >> ------------------------------------------------------------------------------ >> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE >> Instantly run your Selenium tests across 300+ browser/OS combos. >> Get unparalleled scalability from the best Selenium testing platform available >> Simple to use. Nothing to install. Get started now for free." >> http://p.sf.net/sfu/SauceLabs >> _______________________________________________ >> Bitcoin-development mailing list >> Bitcoin-development@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bitcoin-development >> > > > > -- > Andy Alness > Software Engineer > Coinbase > San Francisco, CA > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/