Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XjX0E-0001JJ-Ga for bitcoin-development@lists.sourceforge.net; Wed, 29 Oct 2014 17:25:46 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.213.177 as permitted sender) client-ip=209.85.213.177; envelope-from=jgarzik@bitpay.com; helo=mail-ig0-f177.google.com; Received: from mail-ig0-f177.google.com ([209.85.213.177]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XjX0D-0004Fk-Cu for bitcoin-development@lists.sourceforge.net; Wed, 29 Oct 2014 17:25:46 +0000 Received: by mail-ig0-f177.google.com with SMTP id hl2so2603859igb.16 for ; Wed, 29 Oct 2014 10:25:39 -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=82UgkFmRwlYHQqzosduzhLEwxVCPUoaAEmvdmt+WL+8=; b=Xsm4CEbhX6Y9yvTDzPrJZEtPyfPAR+83JVxi9SkFjsRQzWM2StqW+oBR5XYqPHTEmt tSixtESAkBtjuylP6ycpDpTnmNGD8jLrw2BLAY4vwjoYFThI4U6MEtcWRMxWSP92VrdK 2YRvfcfoBZPLDcBvE4X4zO562Ji88XWXAAz+VDixjLM9t/c94rnK6n0HISR52wEJ+TQI BhCqaEqSyxy/IpKN1R6awYeDM2BkjI7JUz81Z2YfyPR7671k8lvvPAX1Tc4rMXRG+Baj uuX/7UrJiuRVMCG8MMa0gwnc2VXJuk0tYEJrpyCOyHro0VkTa2zsOmhvkHXadBsDkf3S n8/g== X-Gm-Message-State: ALoCoQkr/eXt3+JHW3QoL/iSkJ2ebL7T/o/t8BDBYMdN+k4UVdYr2j8beyntZGUB5dffknsCOmsQ X-Received: by 10.50.73.67 with SMTP id j3mr14093151igv.1.1414603539857; Wed, 29 Oct 2014 10:25:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.156.193 with HTTP; Wed, 29 Oct 2014 10:25:19 -0700 (PDT) In-Reply-To: <5450FAE1.5040508@certimix.com> References: <5450FAE1.5040508@certimix.com> From: Jeff Garzik Date: Wed, 29 Oct 2014 13:25:19 -0400 Message-ID: To: Sergio Lerner 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: 1XjX0D-0004Fk-Cu Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Death by halving (pro-active proposals) X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Oct 2014 17:25:46 -0000 Seconded - IMO a key future use of the chain will be securing other chains. I'm interested in pursuing the merged-mining angle. Getting chain hashes to a miner, and getting that miner payment from the chain, is key to this. Consider a future where there are 10,000 chains secured by one block... On Wed, Oct 29, 2014 at 10:34 AM, Sergio Lerner wrote: > Instead of discussing what will happen when the subsidy is halved (which > nobody really knows) maybe we can think about of what we can do to > mitigate any damage in case something unwanted happens. Let's be proactive. > > For instance, any form of merged-mining (like higher frequency > side-chains) will end-up increasing miners profit, even by a small > margin. Then that margin can compensate miners not to turn off their > equipment. Then we can encourage merge-mining on SHA-256, instead of > discouraging SHA-256 alt-coins. > > Also we can encourage mining during the "trouble" period by creating a > donation pool: suppose we manage to convince miners to donate 1% of > their revenue in order to pay back to the miners for the first month > after the reward halving. If every block pays 1% for 10 months, then > every block during the first month of halving will earn 20% more. Of > course, convincing miners of this may be difficult, but not impossible. > It could be done automatically with nLockTime freeze of transactions > with high fees, so no TTP is necessary. > > So here are two proposals, any other idea? > > Best regards, > Sergio. > > > > ------------------------------------------------------------------------------ > _______________________________________________ > 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/