From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) id 1Uc0nK-0000AW-Ll for bitcoin-development@lists.sourceforge.net; Mon, 13 May 2013 22:00:34 +0000 X-ACL-Warn: Received: from mail-pb0-f41.google.com ([209.85.160.41]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Uc0nJ-0006u5-Kq for bitcoin-development@lists.sourceforge.net; Mon, 13 May 2013 22:00:34 +0000 Received: by mail-pb0-f41.google.com with SMTP id xb12so816539pbc.28 for ; Mon, 13 May 2013 15:00:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=+GTWpOYrKXaqfC+CNUkxGefKPBjEKzTsubX+NnMszJM=; b=piEHP8VXdAwpH2HevLlEaDeVwM2s6mxVrOyaYPupBB+mYUR4IDgeFYSRRPNOKuBRDF 8wy25ekoJFXSNdMQH6T091+P0VTA+fYI7M7aM4ulE0KzrE6aDqA+iruFrzgvttfGYPHz /yXP03omHQ1ZqzdZqEIdJ8Z0L8ezpwjnHrZGwxrhUgDYlP83tyXwzg6XTRD4Rw6bG3tY vd4o6cdBVyhqGpftGUmc92mD3wH1aGjncV86JhnHrLW2Zqeb8nyM7haIOuWOzsxB4TcM mkIPWJ0cCsAkpVjmuW3R2wV5p1w0AkoqzR+ShopF/0HEzVEUZpFHBbMRrW6XbJCI+2sq T7IQ== MIME-Version: 1.0 X-Received: by 10.68.231.65 with SMTP id te1mr30848297pbc.98.1368482427728; Mon, 13 May 2013 15:00:27 -0700 (PDT) Received: by 10.68.240.106 with HTTP; Mon, 13 May 2013 15:00:27 -0700 (PDT) X-Originating-IP: [99.43.178.25] In-Reply-To: <20130513211244.GA9550@netbook.cypherspace.org> References: <20130511045342.GA28588@petertodd.org> <20130511102209.GA27823@netbook.cypherspace.org> <20130513105408.GB3393@netbook.cypherspace.org> <20130513211244.GA9550@netbook.cypherspace.org> Date: Mon, 13 May 2013 18:00:27 -0400 Message-ID: From: Jeff Garzik To: Adam Back Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmbnn6/g5QpjFrjBPQvq5QUfMRMErge9PHN3b95UI24+c9vaRgROlHrKnUk4IkV3WGzTPJc X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1Uc0nJ-0006u5-Kq Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] merged mining hashcash & bitcoin (Re: Coinbase TxOut Hashcash) 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: Mon, 13 May 2013 22:00:34 -0000 On Mon, May 13, 2013 at 5:12 PM, Adam Back wrote: > When you said destroy-via-miner-fee: > > >> Don't forget: 4. destroy-via-miner-fee, which is useful because it >> provides funding for a public service (bitcoin transaction >> verification). > > > Is that directly possible? Because the reward transaction has no source, > and no fee? Or can you put a 25BTC fee in the reward transaction in the > coinbase? When a transaction's input value exceeds its output value, the remainder is the transaction fee. The miner's reward for processing transactions is the 25 BTC initial currency distribution + the sum of all per-transaction fees. A destroy-by-miner fee transaction is a normal bitcoin transaction sent by any user, that might look like Input 1: 1.0 BTC Output 1: 0.5 BTC (the miner fee is implicitly 0.5 BTC, paid to whomever mines the transaction into a block) Sadly the bitcoin protocol prevents zero-output, give-it-all-to-the-miner transactions. -- Jeff Garzik exMULTI, Inc. jgarzik@exmulti.com